ObjectDB ObjectDB

Internal Website Search

71-80 of 200 resultsRefresh

Trouble viewing db in Explorer.

the log file. It should include a more detailed exception stack trace. support Support The log file ... related to the reported problem (it is written to the log file only when the logging level is DEBUG

NullPointerException while setting a new property value

Vitas Lada Please check your ObjectDB log file (mainly on the client side, but server side as ... error. Here is the log file in DEBUG mode, but there is nothing special or detailed error description. https://dl.dropbox.com/u/51625311/objectdb.log (attaching files seems to be broken too...) java

Setting temp directory location in ObjectDB

inactivity-timeout="0" /> <log path="$objectdb/log/" max="8mb" stdout="false" stderr="false" /> <log-archive path="$objectdb/log/archive/" retain="90" /> <logger name="*" level="info

Mismatch client-server protocol prefix

next requests to fail with this exception. Please check the log files for other exceptions, possibly ... after upgrading to the newest underscore release I suppose. I also checked the logs of our other apps ... to the entity manager. From what I see from the logs Spring reuses them and creates new ones

type.loader java.lang.ClassNotFoundException

) Glassfish3.0.1 With server logging turned on I get the following error message for many (or all) encountered ... With logging enabled in debug level - some 'normal' ClassNotFoundException are written to the log - so please check if you still see these exceptions in lower logging level (e.g. info). The empty

Query results are not up to date for entities, not primitives

="true" />   <log path="$objectdb/log/" max="8mb" stdout="false" stderr="false" />   <log-archive path="$objectdb/log/archive/" retain="90" />   <logger name="*" level="info" /> </general> <database

OutofMemory error with Object DB 2.0

" password="true" /> <log path="c:/temp/odb/log/" max="8mb" stdout="false" stderr="false" /> <log-archive path="c:/temp/odb/log/archive/" retain="90" /> <logger name="*" level="fatal

Log4j error

Please initialize the log4j system properly. [java] log4j:WARN See http://logging.apache.org/log4j/1.2 ... this error somehow changes our logging level to DEBUG. Is there possibility that ObjectDB's logging ... the logging level, but apparently there is a class loading conflict. Please try build 2.5.1_05, which includes an attempt to fix this issue. support Support

Enhancement of type is old and cannot be used

Hi, since I switched to 2.8.3_05 from 2.7.6, the ODB log of my app is full of such messages as ... listed in the log. All the listed classes in the ODB log are not existing anymore in my code ... Explorer, I can see those non-existing classes from the log listed as Entities, but they have 0

Internal error

of throwing the exception will write information to the log and proceed (ignoring that unexpected state ... can give you feedback soon. sjzlondon Steve Zara Please try build 2.7.2_07 and report new log messages ... . Will report back log entries soon. sjzlondon Steve Zara I believe I may have found a possible cause

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