Home » Search

About fatal

1-9 of 9Refresh
Manual
84

General Settings and Logging

logging levels are: "fatal" "error" "warning" "info" "trace" "debug"
JDO Doc
8

javax.jdo.JDOFatalException

that are fatal; that is, the condition that caused it cannot be bypassed even if the operation is retried
Forum
2

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)   Some fatal exceptions mark an active transaction
Forum
2

OutofMemory error with Object DB 2.0

/odb/log/archive/" retain="90" />
Forum
2

PersistenceException UserException: Failed to validate persistence.xml

fatal user error> org.apache.openjpa.persistence.ArgumentException: A JDBC Driver or DataSource class
Forum
2

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

. Please see http://www.objectdb.com/database/issue/282?u#item-5. The initial error (with inevitable fatal
Issue
2

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

:*:fatal] java.lang.ClassCastException: com.objectdb.o.STV at com.objectdb.o.PBI.p(PBI.java:91) at com
Issue
2

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

(Worker.java:54)   Now it's really interesting: If we change the loggingLevel   from "fatal
Issue
2

Use temporary files to enable very large transactions

="fatal" />