ObjectDB ObjectDB

Internal Website Search

71-80 of 93 resultsRefresh

How to run JPA query on Terminal instead of explorer.jar??

the Explorer on your local computer and access databases remotely (assuming ports are not blocked by

BIRT plugin: Trouble with Client/Server connection

: 2.5.6.b04 (server)objectdb.conf: <server> <connection port="6136" max="100

Connection is closed Caused by: java.io.EOFException

="false" /> </entities> <schema> </schema> <server> <connection port="6136" max="100

significant performance decrease

-tracking arrays="false" /> </entities> <schema> </schema> <server> <connection port="6136" max

Crash due to memory problems

.OutOfMemoryError: GC overhead limit exceeded [2016-11-10 11:18:55 #16 server] Server on port 3333 has stopped

Unable to convert 1.x odb file to 2.x

, it would be better if you can complete the remaining 1% by your own simple console application that would port any

Update is ignored by ObjectDB

direct access to fields simplifies code porting and direct JSON parsing. User has 100+ fields

each 1-2 days objects on some objectdb level lock/block each other

> <!-- <server> <connection port="6136" max="100" /> <data path="$objectdb/db

merger missing in log

#4 server] Server on port 3333 has started by 476@wzbhb101 [2018-05-16 08:50:02 #5 store

Once served to JSF page via @EJB query bean, many list fields are null (but same query ok after fresh persist in @PostConstruct)

) I appreciate your help - in addition to finding some critical bugs your session of porting from

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