ObjectDB ObjectDB

Internal Website Search

1-10 of 12 resultsRefresh

General Settings and Logging

logging levels are: "fatal" "error" "warning" "info" "trace" "debug"

UTF Error

.objectdb.o.SHN.x(SHN.java:157) at com.objectdb.o.HND.run(HND.java:134) ... 1 more FATAL ... reading UTF string FATAL: /person/List.xhtml @25,35 value="#{personController.items}": javax.ejb

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

. Please see https://www.objectdb.com/issue/1924#item-5. The initial error (with inevitable fatal side-effects

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) dmoshal David Moshal Some fatal exceptions mark

Query fails with failed to read

logging info for this issue (logger "store.file", level fatal, so probably no need for any configuration change if fatal logging is enabled for all loggers, which is the default). support Support

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

interesting: If we change the loggingLevel from "fatal" to "warning", we get other exceptions

Use temporary files to enable very large transactions

/archive/" retain="90" />                 <logger name="*" level="fatal" />         </general

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

database corrupt

system is shared). Accessing ObjectDB in embedded mode directly from two processes is fatal. Regarding


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

Getting Started

ObjectDB is very easy to use. Follow the Getting Started Tutorial and the Quick Tour manual chapter and in minutes you may be able to write and run first Java programs against ObjectDB.

Prior knowledge or experience in database programming (SQL, JDBC, ORM, JPA, etc.) is not required, but some background in using the Java language is essential.

Need Help?

  1. Search ObjectDB website
  2. Read the FAQ
  3. Follow the Tutorials
  4. View or post in the forum
  5. Search or file an issue
  6. Contact support