Fast Object Database for Java - with JPA/JDO support

Internal Website Search

1-10 of 26 resultsRefresh

ObjectDB is opening too many sockets

, and we are now facing following issue. Object DB server is creating too many sockets. Currently the ObjectDB Server process has 3895 opened files, and from that number 3823 are opened sockets. I ... /proc//fd lrwx------ 1 odb odb 64 Mar 19 11:34 995 -> 'socket:[507755621]' lrwx------ 1

General Settings and Logging

sockets become obsolete as a result of inactivity. The value is the timeout in seconds, where 0 ... its own inactivity timeout on sockets a more restrictive inactivity timeout has to be specified for ObjectDB to avoid using sockets that are expired by the firewall. The element

Server Configuration

Explains how to set a JPA/JDO database server using ObjectDB, the fast Java object database for JPA/JDO.

Database Connection using JPA

. a pool of sockets), provides an efficient way to construct multiple EntityManager instances ... EntityManagerFactory instance. Calling the close method is essential to release resources (such as a socket in

[ODB1] Chapter 8 - ObjectDB Server

for the user. 8.4 Using Secure Socket Layer (SSL) ObjectDB supports encryption of client server communications using the Secure Sockets Layer (SSL) protocol. Encryption is especially important

SSL Configuration

The configuration element specifies Secure Sockets Layer (SSL) settings for secure communication in client-server mode, for both the client side and the server side. The default configuration file contains the following element:

Obtaining a JPA Database Connection

or a socket to a remote server) in a connection pool and use them to speed up future EntityManager

Running ObjectDB on a node that does not have internet connectivity

.SocksSocketImpl.connect(Unknown Source) at Source) at ... (Unknown Source) at Source) at Source

Mismatch client-server protocol prefix

and sockets are used for more than one request, failure to read a full request by the server can cause ... . It could be because of concurrent use of the same connection and sockets (i.e. same EntityManager) by two concurrent ... a socket from a closed EntityManager is still used after the EntityManager is closed after its resources

How to disable use of graphic windows by objectDB

of getLocalHost: Socket socket = new Socket(InetAddress.getLocalHost(), port); It seems to be a known issue in

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