About configuration

release

2.3.2

... Fixed evaluation of $temp in the configuration file. Version 2.2.9 Added new configuration to enable / disable auto serialization of non persistable types ...

 
api-jpa

javax.persistence.Persistence

Bootstrap class that is used to obtain an EntityManagerFactory in Java SE environments.(Class of JPA)

 
forum_thread

Login Error (bad username 'admin' or password)

I am getting following error when i am trying to connect to server: [com.objectdb.o._PersistenceException: Login Error (bad username 'admin' or password)] with root cause com.objectdb.o.UserException: Login Error (bad username 'admin' or password) at com.objectdb.o.MSG.d(MSG.java:61) at com.objectdb.o.HND.K(HND.java:210) at com.objectdb.o.SHN.K(SHN.java:208) at com.objectdb.o.HND.run(HND.java:132) at java.lang.Thread.run(Thread.java:662) Here is my connection string: ... admin is defined in the objectdb.conf but maybe this configuration file is not in use. The configuration file has to be located relatively to the path of the ...

 
api-jdo

getPersistenceManagerFactory()

Get the anonymous PersistenceManagerFactory configured via the standard configuration file resource "META-INF/jdoconfig.xml", using the current thread's context class loader to locate the configuration file resource(s).(Static Method of javax.jdo.JDOHelper)

 
forum_thread

lockfiles in client/server mode

i have an objectdb server running on localhost as user "objectdb", spawned like so: java -server -cp /usr/local/share/objectdb/objectdb.jar: com.objectdb.Server -conf /etc/objectdb/objectdb.conf start it has naturally created and taken ownership of /tmp/ObjectDB. ... on the client side should solve the problem, so maybe the configuration file that you have edited is not the one that is in use. Try ... XML error to the file, if the client starts this configuration file is probably not used (see rules for the configuration path ...

 
release

2.7.1

... Improved performance of handling multi activations configuration. Fixed a synchronization bug in using temporary ... on exceeding maximum number of connections specified in configuration. Fixed optimistic lock exception on removing of a ...

 
manual

Database Replication and Clustering

Replication enables maintaining up to date version of an ObjectDB database on multiple nodes.... appropriate  <replication> elements in the configuration : <server > <connection port = ... Connecting to the Database Cluster The configuration above demonstrates a situation in which the master database is ...

 
release

2.2.2

... selected rows. Fixed a replication configuration error . Version 2.2.1 Added support ... space after index deletion. Changed default configuration (enabled recovery, disabled recording). Fixed a ...

 
release

2.3.7

... to TRACE  ( issue #88 ). Changed main configuration elements from required to optional. Fixed the ... Fixed evaluation of $temp in the configuration file. Version 2.2.9 Added new configuration to enable / disable auto serialization of non persistable types ...

 
release

2.7.0

... Improved performance of handling multi activations configuration. Fixed a synchronization bug in using temporary ... on exceeding maximum number of connections specified in configuration. Fixed optimistic lock exception on removing of a ...