About trace

61-70 of 200Refresh
Result
2

Throwable(cause)

). The fillInStackTrace() method is called to initialize the stack trace data in the newly created
Result
2

Throwable(message)

Constructor java.lang.Throwable Throwable(   String message ) Constructs a new throwable with the specified detail message. The cause is not initialized, and may subsequently be initialized by a call to initCause. The fillInStackTrace() method is called to initialize the stack trace data in
Result
2

Throwable(message, cause)

() method is called to initialize the stack trace data in the newly created throwable. Parameters
Forum
2

PersistenceManager.getObjectsById(Collection,boolean) throwing JDOException

a complete error message and stack trace. A test case the demonstrates the issue may help.   Ok, I think ... traces as this is running on a classified lab system, but I wrote down the following notes from ... ) The topmost entry of the stack trace references PMImpl.getObjectsById() on line 511
Issue
2

Blocked by find

blocked: 109 Total waited: 80 Stack trace: com.objectdb.o.PGC.C(PGC.java:484) - locked java ... Stack trace: rbccm.felix.objectdb.workflow.ObjectDbInstanceContainer.putIfAbsent ... further information. The stack trace is related to dilution of pages from the page cache
Forum
2

disabling JDO in objectdb embedded mode

trace does not mention ObjectDB at all. Please check if you have conflicting jars, maybe of another JDO ... . Could you please post the relevant exception stack trace. The stack trace on #1 above doesn't seem to be related. Hi thank you for your reply. The stack trace is very huge, as the content
Forum
2

Occasionally slow requests in load testing

trace examples. Given that the code is obfuscated we have no idea what it is actually doing ... very healthy as well, no issues that I can see. Thanks, Natalia.   The first stack trace (com.objectdb ... may also be much longer than 10-15 seconds. The other stack trace (com.objectdb.o.PGC:w: line number 232
Issue
2

each 1-2 days objects on some objectdb level lock/block each other

:         - None please have a look at that, the situation is getting pretty much uncomfortable This stack trace ... queries require too much cpu. The stack traces show queries that scan data pages intensively ... .     > The stack traces show queries that scan data pages intensively can you write us the thread # that you mean
Forum
2

Database is erased after deploying a new web application version

error message and stack trace. > The name of the process that uses the .odb file is "java" - not ... instances). > Please post the full exception error message and stack trace. Failed to open file '/root ... the file from the new web-app version, but is there a more elegant way to do it? The stack trace
Forum
2

Eclipse plugin problem (using ObjectDB as a separate bundle)

in the stack trace at com.objectdb.jpa.EMImpl.commit(EMImpl.java:277)  refers to JPA. Is this suppose to be there?   How do I set this cascade in JDO? The stack trace is ok - since some ObjectDB ... , do the following: 1. Run the application. 2. If the window does not appear and there is a lot of stack trace