ObjectDB ObjectDB

Internal Website Search

151-160 of 200 resultsRefresh

Query debugging configuration from class

for. I would like to log (in the console or in a separate log file) what it's actually executing

Database corrupted after schema change

is also missing in the list. Neither ObjectDB log, nor the application log wrote any errors, so it looks

Class loading problem with private packages in OSGi environment

a stack trace of the error (from the log file) or provide a sample database file that can be used to reproduce the exception? support Support Hello, following the stack trace in the log

ObjectDB 2.x is working without any activation code

put activation code for a machine in conf file the logs were not opening but recentely we have faced a strange ... to open the logs without any issue , what could be the reason for this ? Also how to find

Object Relations Error after Schema Change

of your application. support Support Hi, we only use one entity class version. Attached second log file. Problem occurs when we create a new entry in the class we have changed the relation. Quote from the log “08

Glassfish and ObjectDB 2.4.3

, Browser, etc.). In addition, check if there are exceptions in the console or in the server log. support ... get no execptions in server log and sometimes yes like here: Launching GlassFish on Felix platform

Enhancer problem

Schreiber Could you check the log file for detailed stack traces? Please provide more details about how you integrate the Enhancer into the build process. support Support Thanks, The logs

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

, field "map" -> 12 broken references More information can be found in the log Relevant part from the log file: [2014-05-06 10:58:29 #53 type.registry] New type eu.extech.quant.data.user_attribute

Service terminated silently (crashed?)...is there any way to cause a crash dump?

After running without issue, uninterrupted for seven months, our instance stopped silently. The contents of the log are as follows: Object DB log: ObjectDB Server started on port 6138. ObjectDB Server stopped. ObjectDB Server started on port 6138. ObjectDB Server stopped. ObjectDB Server started

Close() Method of EMF throwing "PersistenceException: Connection is closed" on first attempt to close.

, please check the ObjectDB log files on the server and the client for more information. To avoid future outage you may want to consider catching this exception and just writing the condition to a log file

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