ObjectDB ObjectDB

Internal Website Search

191-200 of 200 resultsRefresh

Java fails to run when using JMX Remote + ODB agent

=false -Dcom.sun.management.jmxremote.authenticate=fals -versionjava version "1.6.0_18" OpenJDK Runtime ... .management.jmxremote.port=16969 -Dcom.sun.management.jmxremote.ssl=false -Dcom.sun.management.jmxremote ... =false -Dcom.sun.management.jmxremote.authenticate=fals -version java version "1.6.0_26" Java(TM


if locking version-check is set false? are the changes from process B lost if process A subsequently commits ... : <locking version-check="false" /> correct? Is that all that is needed to switch from optimistic ... works for me: 1) standard config file with these changes: <locking version-check="false

ObjectDb.conf Defaults

-history size="0" user="false" password="false" /> --> <!-- error if missing <log path="" max="8mb" stdout="false" stderr="false" /> --> <!-- error if missing <log-archive path="$objectdb/log

Pessimistic lock

: javax.jdo.option.Optimistic=false javax.jdo.option.NontransactionalRead=true javax.jdo.option.NontransactionalWrite=false javax.jdo.option.RetainValues=true javax.jdo.option.RestoreValues=false ... =true javax.jdo.option.RestoreValues=false The DB2 returns the message "Optimistic lock failed

Activation license not picked up in Jenkins

.7437 18.99/1.18 (a.deleted=false)> <extractPlan 3.7225 18.96/1.18 a(Site ... .Site a WHERE a.deleted=false" => 0 results in 71 milliseconds. [2020-09-03 22:03:34 #18 type ... ] <finalPlans> <filterPlan 3.7649 19.01/1.18 (a.deleted=false)> <filterPlan 3.7437

mapping file is not being loaded

.xml file makes any difference. Another thing to check - setting exclude-unlisted-classes to false ... - manually listing classes along with setting exclude-unlisted-classes to false. The Metamodel API ... configuration element back to false, and ran the original project. The metadata was now accessible

Objectdb recovery

Hello, I have question regarding objectdb recovery when objectdb is not finished correctly (power outage). We are using following configuration: <recovery enabled="true" sync="false" path="." max="128mb"/> <recording enabled="false" sync="false" path="." mode="write"/> Is there any possibility

Optimistic locking: prevent version increment on entity collection attribute

out to be false!     assertTrue(readings != null);     assertTrue(readings.size() == 2); } oudjanef Farid ... ); // This turn out to be false! assertTrue(readings != null); em.close ... ()); // This is false! assertTrue(finalDoc.getReadings().size() == 2); em.close(); emf.close

Activation Issue

="true" sync="false" path="." max="128mb" /> <recording enabled="false" sync="false" path="." mode

ObjectDB can't be activated

activation", boolean.class).getSingleResult()); Result is "false". Also when trying to create ... : false com.objectdb.o.UserException: Too many persistable types (>10) - exceeds evaluation limit at com ... = venet0:0         name = venet0:0         subInterfaces = false         hardwareAddress = null

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