ObjectDB Database Search

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

(EMImpl.java:290) We see in this stack trace that is a commit operation, all right ... So why does it try ... could give you more informations about this issue. Xirt xirt Sylvain As a start, please post a full stack trace of the exception. support Support

this issue further could you please provide full stack traces of the exceptions. You may be able to find the full stack traces (including exception causes) in the log files. When the server starts

Stack Trace , because when tagged as Java Code the background-color doesn't get shown as marking but as ... and couldn't get the exception. Please provide a full stack trace (from the log), and check

Eugen Please post the complete stack trace including nested exceptions (check the ObjectDB log file ... to de.tud.stg.emergent.policy.persistence.ClientEntity ----- complete stack trace including nested

I have the following stack trace .  Is this a null ptr in our code or in the object db code? Failed to commit transaction:  (error 613) at com.objectdb.jpa.EMImpl.commit(EMImpl.java:279 ... .commit(EMImpl.java:276) CalculationServices Calculation Services The stack trace indicates an attempt

. prolancer Emil Andonov Please post the stack trace that you get with version 2.5.4_03. support Support Here is the stack trace when using your DB explorer tool to run the query:   [ObjectDB 2.5.4_03

; the method on the bottom of the stack trace looks like this: private PersistenceManager persistenceManager ... there is something I can do to prevent it next time.   jakab Gergely Jakab The stack trace

These stack traces show normal waiting for short time locks. Maybe several full thread dumps can show a repeating pattern of a specific activity that holds such locks more than expected (the stack traces

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

(EMImpl.java:292) jakab Gergely Jakab The new stack trace indicates a collision between automatic schema

you the stack trace when it happens, but it's ultimately all related to the fact

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

, the locking thread's stack trace indictes a slower operation of creating a new connection

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

? Debugging? Runtime? If it is an exception - provide a full stack trace . If it is a compilation error or

Stack trace below:   [ObjectDB 2.7.1_02] Failed to process class file of type 'app.model.ClientSession' (error 422) com.objectdb.o.UserException: Failed to process class file of type 'app.model.ClientSession'         at com.objectdb.o.MSG.d(MSG.java:75

] ............ codefad FrankChu According to the stack trace you may have a map whose one of its values

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

should include a more detailed stack trace . Could you please send it? In addition, if this is a new error

J visual vm is complaining of deadlock since upgrading to the 2.4.4_16 from _06 and using setting -Dobjectdb.temp.no-resize-clear=true The only other change is that we no longer create recovery or replay files as we were not using these. i have attached our full server strack trace

with version 2.8.8 please post the up to date stack trace . support Support The Client side is 2.8.8 (a maven

Here is the stack trace of blocked threads : com.objectdb.o.OMF.at ( OMF.java:881 ) com.objectdb.o.OBM

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

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

above (write a 10-15 Mbytes) need to check remaining memory in any available profiler. Stack trace

:719) btc_es BTC EmbeddedSystems The stack trace indicates an unexpected state of the query result

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

a stack trace and some code snippets if they would aid understanding. I'm merely trying to determine

just the one type.  The log file shows the same stack trace and nothing else of note. Crispy

. The stack trace indicates an unexpected state of one of your persistable types, and if the same code ... to provide a workaround to the specific exception in your stack trace . Please try it. With this new build

.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

? ##### Additionals infos, here is the stack trace : [ObjectDB 2.4.0] Unexpected exception (Error 990) Generated ... ();         emf.close();     } } The stack trace

See stack trace below. Unfortunately I just uncovered this in a log check so I dont have any further information surrounding the circumstances. java.lang.NullPointerException at com.objectdb.o.SHN ... Richard Szurgot The stack trace indicates an attempt to run a query in client-server mode

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

; bmcalist.odb Brian The database seems to be healthy. These stack traces are normal when using DEBUG level ... ) ---------------------------------------------------------------- bmcalist.odb Brian The stack trace indicates an index problem

exception at the minimum the stack trace of that internal exception and the full error message

the context of your second reported stack trace . If it does't solve the issue, we may need a test case that demonstrates the exception. support Support

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

you for this report. The stack trace indicates an unexpected condition at the end of a flush

van woerkom Unfortunately the information in this stack trace is not sufficient to identify

Zwicker You can see all the query plans in the log if you enable logging for queries in trace level

, the stack trace indicates an issue in communication between the client and the server

Jakab The stack trace indicates out of memory situation in Java 8 Metaspace (not the JVM heap

(RemoteTestRunner.java:210)   velo Marvin Froeder The stack trace seems to be related to the value

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

trace of the exception it could help in investigating this further. support Support

Steve Zara Thank you for this report. The stack trace is incomplete. Further lines

.java:1438)     btc_es BTC EmbeddedSystems This stack trace indicates an unexpected

client-server mode then the stack trace clearly indicates a client side OutOfMemoryError (maybe