ObjectDB ObjectDB

Internal Website Search

71-80 of 200 resultsRefresh
80

Suspected memleak caused by bad state of EntityManager

Our application manages the Entities itself, so we close the EntityManager after every creating ... and finalize, we found the problem is caused by bad state of EntityManager. After first throwing the InternalException, the EntityManager throws every time when doing merge operation, but it can be closed
80

EntityManager to closed

Hi I understand we should close the entitymanager after each use, and close the factory ... . I am just running some test cases and opened up 100 entitymanager via factory.createEntityManager ... closing EntityManager and EntityManagerFactory instances is mainly wasted resources on the client side. support Support
80

Issue with orphanRemoval and multiple EntityManagers

with orphanRemoval set to true. I use a new EntityManager for each transaction (which normally happens in ... , the database contains 3 child entities. If I use the same EntityManager for both transactions ... @contextspace.com"));         EntityManager em = emf.createEntityManager();         em
79

JPA - ExceptionInInitializerError when creating EntityManager

.EntityManagerFactoryImpl@ffa7e1 EntityManager emTemp = emf.createEntityManager(); TypedQuery<EmailSettings ... .createEntityManagerFactory("myDBPU"); javax.persistence.EntityManager em = emf.createEntityManager(); try { Object
79

EntityManager getMetamodel() causes crash

I am trying to track down some obscure errors with multi-threading. This involved looking at the EntityManager Metamodel but this caused an ObjectDB exception. So I reverted to your example code in ... " EntityManager em = emf.createEntityManager(); em.getTransaction().begin
79

EntityManager.refresh takes a long time

EntityManager.refresh takes a long time for entity object Person in this code:     logger.log(Level.INFO, "begin select for person " + new Date().toString());                TypedQuery<Person ... understand this term correctly, if try to refresh Entitymanager updates only objects in his context
79

Eclipse4 RCP - No Persistence provider for EntityManager

.PersistenceException: No Persistence provider for EntityManager I'm using the latest ObjectDB 2.6.2.b03 ... an EntityManagerFactory to building an EntityManager) it may be because resources that are needed by
78

Executing JUnit "all tests" throws "Object ... belongs to another EntityManager" Exception

#7' belongs to another EntityManager [Symbol:7] When I change the order in which the test runs (by
16

An entityManager.flush() with many entities is not possible

The following exception occures if we call entityManager.flush() where the corresponding JPA PersistenceContext has many entities and relations. What is the reason for the exception? entityManager.getTransaction().commit() instead of a entityManager.flush() works correctly. Unfortunately I have not
15

DB persist operation results are not available for another Thread/EntityManager immdiately

Hello, we have following situation: The EntityManagerFactory is always opened and won't be closed. Thread A with its own EntityManager persists entities and commits the entities successfully. Thread B runs afterwards also with its own EntityManager and tries to load the persisted entities by

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