ObjectDB Database Search

keeps growing, but the actual odb file never changes unless I restart the server.  The  .odr ... ?  It only changes when  restart the server? Trianglehead Json Error It is normal

it causes following error and the ObjectDB is restarted automatically: java[3545]: Too many open files ... bellow are steps done on 1 running ObjectDBServer without restarts , also explorer was single instance

well. Today we restarted the app and it threw the following exception during startup while trying to read ... . However this one service thrown this error even without the restarting of JVM. Is this wanted behaviour? We'll

fine with the default JVM heap size on a PC with 16GB RAM. Did a server restart solve the issue ... thrown back to your application? support Support some report about the state: - server restart solved

deleting the database files and restarting the server. Now the Unique constraint works

, but for some reason it persists across database restarts , which is scary to me. here in part of the conf file

I am getting this exception on a regular basis, after a period of time of repeating the same code execution.  I don't understand why.  I restart the DB server and my code works again for another period of time until same exception is encountered again.  I cannot pin down a pattern e

.java:662) Exception in thread "main"     Then I have to restart the server, but when I

another instance, it tells me that there is another connection to the database.   If I restart

, allow to close individual or all. c. Buttons to restart database, hot backup (remote server to local

dont have the database anymore as it was deleted when the application was restarted . I'll try

integrity.   Secondly, after the slave went down we tried to restart it, but got an error similar

. Because the "odbxxxxxx.log" file is in use by an java process. If I restart Glassfish, I can delete the folder

restarts .  I'd just like to know how to configure it to be in my home directory

Glassfish3.1.1 Netbeans7.1 ObjectDB 2.3.7_19 If I deploy a web application to Glassfish using ObjectDB as JPA provider, then undeploy, I can't access the database file in the ObjectDB explorer, the explorer claims the database file is being accessed by another process. If I restart Glassfish

until i restart tomcat. Other JPA providers are able to fetch the Metamodel without connecting to the DB

the objects. At some point, may be when restarting Glassfish or re-publishing the application, the database

delete it and restart the database server. Version 2.3.1 is nearly one year old - you should upgrade

the problem), or changing schema without restarting the server - but more details are required. support

an ObjectDB version at the client side and keeping the server running. Try restarting the server

and the server use the same ObjectDB version. Do you still get the exception after restarting

When launching the Guestbook tutorial for the second time (after a server restart ) I get a ClassCastException: java.lang.ClassCastException: guest.Guest cannot be cast to guest.Guest The first time (when the db is created) persisting and retrieving works fine. Using the explorer on the db file

and restart the application with the same DB, I see the original behavior (working but slow).  

;deliberately to the objectdb.conf file and restart the server, to verify that the  file is in use by

that demonstrates the problem. If you are working in client-server mode, you should try to restart the server

without restarting the application, but no luck. For example, we get the same behavior

on slave server and restarting it. It converts my *.odb to *.odb_nonclosed mastervoland Vladimir

down and database lost connection with the JBOSS AS, several restarts got it up and running finally. 

I'm considering using ObjectDB in a system that is going to be running continuously without support instantly available for many years.  How stable is ObjectDB when it comes to power failures and unattended restarts ?  Is database integrity maintained during such events?  I have seen

neither. I restarted the machine as well, but nothing. I'm writing thanks to IE now. zmirc Mircea Chirac

and submitting again.   And a reload of the page or restart of the browser have the same result

has been properly restarted . All other classes which just had package renames are working well. Any idea

file we added about 30K records over 2 days. 4. Try a DELETE - exception thrown. Restarting

will be completed. Even if there is a failure, restarting the slave and the connection to the master

Running in embedded mode, configuration specifies " ".  Still, tablename.odb$ files get created, and if still present after an abrupt stop, the application will not restart properly.   What do we need to do to not utilize recovery files (not have orphan tablename.odb$ files)? CAPdev CAP

configuration. If ObjectDB recovery is enabled then ObjectDB should recover automatically when it is restarted

AND you restart Glassfish and Clean and Build and Deploy/Run, the web app runs and will display

I added a simple User entity during Tomcat startup: class User {  @Id @GeneratedValue private long id; @Basic(optional = false) private String firstName; private String middleName; @Basic(optional = false) private String lastName; } Everything works fine until I restart the server, which does

when Swing is unavailable. Currently start/stop/ restart messages are printed to the standard output

; longpat Brian O'Hare Maybe the server was still running. Schema changes  requires server restart . I

but when I restarted the objectdb servers and the application clients it seems to be working ok

:680) thanks, Alex quasado Alexander Adam Funny enough, after restarting my application it works

and restart .   support Support hi, Perfect, thank you very much! Now the only point left

had assumed that objectdb would reprocess these when the services restarted but instead we got the exception

classes in agent enhancement (by catching exceptions). Added automatic restart for failed connections

anymore after restart of the web application: com.objectdb.o._PersistenceException: Failed

I don't want to keep creating these issues but the Exception tells me to :), I started a thread to see if anyone else has encountered this at http://www.objectdb.com/database/forum/484 Essentially what has happened if i've added a bunch of new fields to an existing entity, I restarted the DB

restart tomcat. Other JPA providers are able to fetch the Metamodel without connecting to the DB. I

We've been having a problem where our ObjectDB server goes unresponsive every 2 days or so.  I've reviewed the server-side logs, and there are no events logged shortly before the crash.  Once the server gets in this state, it is unresponsive to bin/server.sh restart ; I have had to reboot

while, I have to restart Tomee, because none of the DB queries work after those errors