ObjectDB Database Search

BTC EmbeddedSystems Could you please post the exception and its stack trace ? support Support It was Error 990. btc_es BTC EmbeddedSystems To examine this error we would need the stack trace

. sjzlondon Steve Zara Could you please post the thread dump at that point (i.e. the stack traces ... are you using? The stack traces do not match the last version (2.7.6_01) so the line numbers don't indicate

I will continue investigating this, probably by tracing the whole process as this is a blocker ... . I was tracing it using strace and there are messages like this: [pid 34741] 16:34:38.348869 accept

the below error and stack trace in the log.  Can you please help us determine the problem ... (HND.java:134) at java.lang.Thread.run(Thread.java:745) CAPdev CAP Dev Unfortunately the stack trace

you find this stack trace , in the log file? on the server, client or both? If you get the stack trace

well. Although the stack trace indicates an error while reading the hash map, if some objects in the database are corrupted then unfortunately, the exact stack trace is not very helpful. Finally

The stack trace  indicates that an attempt to access the JDO dtd file (in order to verify

please open new forum threads. You should provide more details including a full stack trace . In addition

- so the exception is unexpected. Maybe you have to restart the server (I see that the stack trace

Eclipse. Stack trace is attached. Any ideas? Is there any way to avoid the usage of those proxy

trace and check your code - you might find that your compareTo method changes a persistent field in

and post stack traces of all the running threads . support Support

- modified to actually deploy to repo!   Willks William You are right. Here is the full stack trace

EntityManagerFactory but they have their own EntityManager . The stack trace and the test are attached. edy

stack trace . I have tried to Google the problem but with no success. The value 7 is random. I

@Index, I traced it to the JDO lib. So if I want to make a index without SQL on database, then @Index

them to the pool?   longpat Brian O'Hare Following the server side stack trace (in #2

trace the exception might not be related to using NEW . There is an unexpected state during query

of the entity hierarchy?   My listing of assumptions above is based on the following call trace : 

values I get the following stack trace : ava.lang.ClassCastException: com.epimss.lab.data.toxicology

the following stack trace . [ObjectDB 2.2.8] javax.persistence.PersistenceException Failed to get reference

should never be thrown. Please post the complete stack trace of the exception that you get. support

ObjectDB log file should contain a full stack trace of the Enhancer exception, at least when you run

the meanwhile, here is the output for both the CDI and Organisation queries from objectdb trace :  

(and stack trace if available).  So, instead of DB write a standard serialization mechanizm

. The fix is based on the stack trace rather than on the test case since running the test project

a full stack trace and more information about your entity class and the problem. support Support

Schreiber Could you check the log file for detailed stack traces ? Please provide more details

ObjectDB enhanced classes fail when compiled to Java 1.7 [ObjectDB 2.2.9_08 Enhancer] 28 persistable types have been enhanced: ... com.vaisala.jx.db.gdm.model.SourceType stack trace from jUnit test com.vaisala.jx.db.gdm.facade.BaseFacadeTest  Time elapsed: 0 sec 

that crash the application. This is part of the stack trace : java.io.FileNotFoundException: file:\C:\Users

Please check the log file for additional errors / exception stack trace . support Support I've

anymore and it is highly recommended to upgrade to ObjectDB 2. But I can check the stack trace

Hi! Just got this: [com.objectdb.o.ENT.A(ENT.java:450), com.objectdb.o.OBM.bx(OBM.java:371), com.objectdb.o.OBM.bx(OBM.java:249), com.objectdb.jpa.EMImpl.persist(EMImpl.java:375), ...]   Any idea?? Using 2.3.3 ... thanks!! Alex quasado Alexander Adam The stack trace doesn't match version 2.3

(if you have an exception stack trace in the log it may help understanding why it has failed in

= result.get(0); logger.debug("[ trace _fetch] ["+g.getMembers().size()+"]"); return g; } } finally { em

BTC EmbeddedSystems The stack trace indicates an unexpected state of the query result cache ... to diagnose the cause.     support Support Further analysis of the stack trace revealed an issue

trace , you can still see that if you look at the file and class names that are shown in this stack trace . support Support

when the log file reached its size limit. Here's the stack trace of that issue: com.objectdb.o ... .objectdb.o.LFL.m(LFL.java:874) ... 21 more Arne Arne Stocker The first stack trace indicates

.jpa.EMImpl.find(EMImpl.java:524) btc_es BTC EmbeddedSystems This stack trace shows ... version (e.g. 2.9.0). An analysis of this stack trace indicates a situation in which the a find method

that I'm running along with a file containing the full stack trace that I'm getting. Let me know

According to the stack trace - it doesn't look as anything serious, just an incomplete check of a new

This is another unrelated NPE and this time I will need more than the stack trace . I am checking out the test

trace has not been produced by the last ObjectDB version. Which ObjectDB version are you using (probably

.objectdb.o.IVP.g(IVP.java:96) ... 27 more   FastModel Ben Schreiber According to the stack trace

at com.objectdb.o.REG.S(REG.java:822) freddieFishCake Jonathan Lister The stack trace indicates

.runner.RemoteTestRunner.main(RemoteTestRunner.java:197) If the stack trace is no use I can send a zip

I'm getting the following stack trace when running the enhancer on one of my jars: [ObjectDB 2.3.2_04] null java.lang.NullPointerException at com.objectdb.o.JEL.L(JEL.java:633) at com.objectdb.o.JEL.D(JEL.java:491) at com.objectdb.o.JEN.k(JEN.java:95) at com.objectdb.Enhancer.main(Enhancer.java:32

at the time so feel free to just close this issue if the stack traces are of no use to you - I thought

see that the exception is written to the log with a WARING level. It would be changed to TRACE in the next build (2.3.3_01).  support Support

felixobjectdb Richard Szurgot The stack trace indicates a problem in updating an index, maybe in a new type (or