ObjectDB ObjectDB

Internal Website Search

11-20 of 98 resultsRefresh

ObjectDB is opening too many sockets

nothing: [2021-04-16 18:26:25 #1 server] Server on port 10054 has started by 26621@testing TCP Dump ... port 10054 We had also strace running to print all network related kernel calls from process: Based ... _INET6, sin6_port=htons(37970), inet_pton(AF_INET6, "::ffff:", &sin6_addr), sin6_flowinfo

How to change properties in urls2.xml?

url and their port / user / password properties. I have no control on the port and password used. :( Does it exist a way to change urls2.xml properties ? Adding ?port=XXXX at the end of the persistence ... > <property name="javax.persistence.jdbc.url" value="/var/lib/tomcat7/db/myDb.odb?port=3333

Server vs embedded mode in multi-instance scenario

> <connection port="6136" max="100" /> <data path="$objectdb/db" /> <embedded ... to the database from other machines - the first process should use a url such as: test.odb;port=3333 (specifying a port). All the other processes should be able to connect to the database remotely using

Glassfish and ObjectDB 2.4.3

[http-listener-1] on host/port [] INFO: WEB0169: Created HTTP listener [http-listener-2] on host/port [] INFO: WEB0169: Created HTTP listener [admin-listener] on host/port [0 ... -listener-1] on host/port [] INFO: Grizzly Framework 1.9.46 started in: 2ms - bound to [0

multiple connection using share folder

a configuration file explicitly -port <port> : override configuration's server port -silent ... file <server > <connection port="6136" max="3" /> <data path="$objectdb/db ... ) and port. It is possible in embedded-server mode but it would be easier with client-server mode

connection pooling

port="6136" max="100" /> The <connection> element specifies how clients can connect to the server: The port attribute specifies a TPC port on which the server is listening for new connections. Usually the default port 6136 should be specified. If another port is specified it also has to be specified

EntityManagerFactory Fails To Swtich Over To Slave When Master Is Unavailable

>         </schema>         <server>                 <connection port="9999" max="100 ... >                 <connection port="9998" max="100" />                 <data path="$objectdb/db ... master on port 10,000. 2.) On same server, start ObjectDB server as slave on port 10,001. 3.) Run test

Database Connection using JPA

) and listening on the specified port (the default is 6136 when not specified). The path indicates

Database Explorer

select File > Open C/S Connection... and provide host, port, username and password for a client-server

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

. 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 on port 6138. ObjectDB Server started on port 6138. <--This is where I restarted the service. Note

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