About fatal


General Settings and Logging

Describes general configuration and logging of the ObjectDB Java object database for JPA and JDO. the ObjectDB General configuration section.... The supported logging levels are: "fatal" "error" "warning" ...


Server connection management

The server does not appear to release broken connections. My typical development pattern is to keep reloading my war file in tomcat until the permgen space runs out, and then I kill and restart tomcat. After a few days of this, the server stops responding, and I see the following in the server logs: ... I see the following in the server logs: [odb:server:fatal] com.objectdb.o.UserException: Too many open connections (100) at ... be released? The exception is: [odb:server:fatal] com.objectdb.o.UserException: Too many open connections (100) at ...



This class represents exceptions that are fatal; that is, the condition that caused it cannot be bypassed even if the operation is retried.(Exception of JDO)


Querying error - java.lang.ClassCastException: com.objectdb.o.STV

I'm getting the ClassCastException below when querying objects. As yet I haven't been able to track down the exact circumstance in which it occurs - saving and querying objects works fine on attempts to recreate - but presumably at some point an object gets saved which objectdb doesn't like. Any pointers as to what is wrong or approaches to investigate further would be much appreciated. ... further would be much appreciated. [odb:*:fatal] java.lang.ClassCastException: com.objectdb.o.STV at ...


Failed to commit transaction: Attempt to commit a rollback only transaction

Anyone know what this means?? Suddenly cropped up.   Failed to commit transaction: Attempt to commit a rollback only transaction (error 613) at com.objectdb.jpa.EMImpl.commit(EMImpl.java:271) at javax.jdo.Transaction$commit.call(Unknown Source) ... 22:54 Some fatal exceptions mark an active transaction as rollback only. In that ...


Unexpected exception (Error 990) com.objectdb.o.InternalException

Hello, we get an exception if we use Enhanced Entities. With not enhanced Entities we get no error. ... If we change the loggingLevel   from "fatal" to "warning", we get other exceptions.  (We do excactly the same!) ...


OutofMemory error with Object DB 2.0

Hi, I am getting the below OutOfMemoryError after I have migrated from objectdb 1.0 to 2.0 The application works with 256MB heap size with objectdb 1.0  But on 2.0 even with max heap size of 1024MB, I get this error. The application reads xml file of around 1GB and creates a new odb file and inserts 200 records at a time. ... /> <logger name = "*" level = "fatal" /> </general >   <database > ...


PersistenceException UserException: Failed to validate persistence.xml

I'm really tired of looking at the same exception all day. I have DaoService which gets initialized when app starts. ... HTTP Status 500 - <openjpa-2.2.0-r422266:1244990 fatal user error> org.apache.openjpa.persistence.ArgumentException: A JDBC ...


Possible cause for "Enhancement of type ... is old and cannot be used"

We get the following log: ... . The initial error (with inevitable fatal side-effects) is similar (see more detailed error report at that link): ...


Use temporary files to enable very large transactions

We have transactions in which many objects are created. These objects are no longer needed in the current transaction after creation. Unfortunately, we will receive an OutOfMemory exception because the objects are kept in the first level cache of ObjectDB. In the forum thread http://www.objectdb.com/database/forum/921 on post #4 you wrote, that ObjectDB should support very large transactions in further version. Can you implement it that ObjectDB used temporary files? ... <logger name = "*" level = "fatal" /> </general > <database ...