ObjectDB ObjectDB

Internal Website Search

1-10 of 41 resultsRefresh

General Settings and Logging

: <general> <temp path="$temp/ObjectDB" threshold="64mb" /> <network inactivity-timeout="0 ... represent megabytes and kilobytes (respectively). The <network> element <network inactivity-timeout="0" /> The <network> element has one attribute, inactivity-timeout, which specifies when network

Server connection management

to have a configuration setting that would tell the server to close connections after a period of inactivity ... server in a few seconds after it becomes accessible again. Inactivity Timeout You can set the inactivity timeout in seconds and it affects both the client and the server side:   <general

Log is almost empty (log level 'trace')

. due to inactivity) by the operating system, firewall, etc. In that case setting a non zero inactivity timeout ... , so I doubt it's a problem of VPS config. Regarding 'Inactivity period', I indeed saw ... dont see any relation. I'll try to play with inactivity timeout and let you know results. Yuri

Query becomes slower on moving from ObjectDB 1.x to ObjectDB 2.x

logEntryId, which is inactive. An inactive index is usually the result of adding a new index ... ) but currently inactive indexes are not detected. Anyway, this procedure is a one time operation

ObjectDB shuts down

. It always happens in the morning ie. after several hours of inactivity although we are not sure ... , or some similar inactivity. When inspecting the log it doesn’t show anything why the database ... the process? Since you mentioned idle action, you may want to check the inactivity setting

500Mb ObjectDb database opening issue

500Mb ObjectDb database opening issue

Replication error on slave restart

> <temp path="$temp" threshold="128mb" /> <network inactivity-timeout="0" /> <url-history size ... inactivity-timeout="0" />   <url-history size="50" user="true" password="true" />   <log path

EntityManagerFactory Fails To Swtich Over To Slave When Master Is Unavailable

" threshold="64mb" />                 <network inactivity-timeout="5" />                 <url-history ... inactivity-timeout="5" />                 <url-history size="50" user="true" password="true

Replication issue, Replayer failing due to NullPointerException.

> <general> <temp path="$temp/ObjectDB" threshold="64mb" /> <network inactivity-timeout="0 ... <objectdb> <general> <temp path="$temp/ObjectDB" threshold="64mb" /> <network inactivity

[ODB1] Chapter 8 - ObjectDB Server

inactivity time (in seconds). If a connection is inactive for more than the specified time the server

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