About console

forum_thread

Exceeding max connections and crashing

Hi, we have severe problems with ObjectDB crashing frequently. We can’t find the exact cause but we suspect several things. We use 2.5.3_03 version and we use it in production. The same setup in test environment hasn’t have these kind of problems First crash occurred when network went down and database lost connection with the JBOSS AS, several restarts got it up and running finally.  It seems when the database loses network connection it shutdowns but we cant be sure. Usualy database stops once a day with no apperent reason. ... but you can try to connect to the database from any Java console program using ordinary JPA, and see if it is running and functional. ...

 
issue

Eager load Map

I'm having an issue eager loading a nested map. I've attached @ManyToMany(fetch=FetchType.EAGER) attributes to no avail. If the map is viewed in the debugger or force iterated in the code it loads ok. The attached code attempts to replicate the scenario. Its not an exact match but is the best I could come up with without replicating the whole system. The test creates an object, persists it to a db and re-loads it. The EntityManager is closed before accesing any fields. Finally the nested map is accessed and printed to screen. ... and the nested map is empty so nothing is printed to the console. If you uncomment the 2 lines after the "find" and re-run the test, the ...

 
release

2.0.5

... support for running a server with no tray icon (using a -console flag). Changed EntityManager.find to return null when no ...

 
release

2.0.3

... support for running a server with no tray icon (using a -console flag). Changed EntityManager.find to return null when no ...

 
release

2.0.2

... support for running a server with no tray icon (using a -console flag). Changed EntityManager.find to return null when no ...

 
release

2.0.4

... support for running a server with no tray icon (using a -console flag). Changed EntityManager.find to return null when no ...

 
issue

Post-compile enhancement sometimes causes error in generic loops: incompatible types found: java.lang.Object: required: Entity

I have moved from automatic run-time enhancement to explicit post-compile enhancement in an Ant build.xml in a NetBeans web app, and sometimes on editing a file that performs a generic loops over and @entity type I get a generics error. The loop is:  for (Steel s: this.steelMaterials.getL_Steel().getEls()) { eSteelTableItems.add(asXmlElement(s)); } Where getEls() here gives: List<Steel> This sometimes (only, I don't understand the circumstances) gives this error: ... Could you please provide a simple console test case that demonstrates this issue? ...

 
forum_thread

Filename.odb$ Persisting Issue

Hi, I seem to have a frequent issue with my Filename.odb$ remaining in my /db directory after my program terminates which prevents me from running my program again due to a persistence error thrown by Eclipse. I can't seem to manually terminate the file either. I usually have to fully close Eclipse and wait a bit for it to remove itself. Any ideas why this happens? Thanks, Dragon ... and executed (e.g. using a debugger or printing to log o console). It will not be reached and executed if the application is terminated ...

 
forum_thread

Lazy loading does not work - crud takes long

tomee7.0.0SNAPSHOT,objectdb 2.6.4 The OneToMany Entities are filled with 40.000 Records and they have between 20-40 Columns. It takes over 50s to load all Project Enities that contains the OneToMany Relationships. It should be load lazy but i didnt know why the query fetch all the Data. ... in your application will require posting a minimal Java console test case (see these instructions ) that reproduces this situation. ...

 
release

2.0.1

... support for running a server with no tray icon (using a -console flag). Changed EntityManager.find to return null when no ...