Internal Website Search

that has already been fixed. The stack trace is produced by ObjectDB 2.3.7, which is 2 years old now ... ALIREZA ZARRABI Could you please provide a stack trace with the last ObjectDB version (2.5.4_03

Hello, Some on my threads stay in BLOCKED state in my thread pool. When i watch the stack trace , i see only just obfuscated object db code. com.objectdb.o.PGC.w ( PGC.java:212 ) com.objectdb.o.SNP.D ... statement at the end of that stack trace . Please provide more details, and if possible also a test case

. 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

7 and succeed?  If so any advice i l helpful Here is the stack trace 13:49:11,894 INFO [org ... problem (JBoss fails on NullPointerException according to your stack trace ). It affects using JBoss

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

the stack trace ? support Support com.objectdb.o.UserException: Attempt to obtain a transaction using ... exception to a JDO exception before throwing it externally. Note that the stack trace was essential

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

to post a stack trace on an exception report. Thanks!  support Support Fix confirmed.  Thank you. CBE CBE

Hi, We have a problem where our database size grows over time more than expected. We've traced it down to the following issue: I have some entities that are using OneToMany relationship with orphanRemoval set to true. I use a new EntityManager for each transaction (which normally happens in

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

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

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

and TransportationEvent. Thanks in advance! lakshmi Lakshmi Please post the exception full stack trace . support Support

.MessageDB.main(MessageDB.java:68)   zepinto Jose Pinto The stack trace indicates an attempt ... next bug reports, since in most cases the stack trace alone is insufficient to solve an issue. support Support

This is the second stack trace that I get, almost always and continuously if I increase the load: May 20 ... . It seems that all entity managers become corrupted / broken. (see stack trace below) Should it be something in

part of the trace that reveals what inside com.greensoft.greenstar.ejb.ext.ExtGreenStarRequestBean ... ); // } return ok; }   webel Dr Darren Kelly The stack trace indicates an unexpected state

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

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