9 | Mismatch client-server protocol prefix. It could be because of concurrent use of the same connection and sockets (i.e. same EntityManager) by two concurrent threads. ObjectDB synchronizes use of EntityManager by different threads, but maybe there is an uncovered ... a socket from a closed EntityManager is still used after the EntityManager is closed after its resources |
9 | Query results are not up to date for entities, not primitives objects and then updating them, but it should be used cautiously because bypassing the EntityManager may break its synchronization with the database. For example, the EntityManager may not be aware ... . Therefore, it is a good practice to use a separate EntityManager for UPDATE queries." support Support Ok |
9 | Conflicting modifiers .... (javax.persistence.Id, javax.persistence.ManyToOne) javax.persistence.Basic; import javax.persistence.Entity; import javax.persistence.EntityManager ... ") }) public class Container { public static Container getInstance(EntityManager em) { Container c ... , EntityManager em) throws TestException { if (lastInstanceInMap == null) { lastInstanceInMap |
9 | Visibility of changes in Transaction is not visible to a JPA QL Query getInstance(EntityManager em) { Singleton c = em.find(Singleton.class, "1"); if (c == null) { c ... .lang.Integer lastInstance; public void generateItems(EntityManager em, int howMany ... (EntityManager em) { TypedQuery<Long> q = em.createQuery("SELECT COUNT(x) FROM Item x", Long.class |
9 | Problem on JPA Merge Entity.Hello, I have a problem with the EntityManager.merge() function. I set a property value ... ErgoDaoJpa implements IErgoDao { @PersistenceContext private EntityManager entityManager ... , DaoException { entityManager.persist(ergoClass); } public void updateErgoClass |
9 | Entity listener - event instead of object database. I can't find the nice way to use EntityManager in EntityListener. Because of that, I can't ... . Please be more specific regarding the technical question. Do you need to obtain an EntityManager from ... to an EntityManager. support Support I know about this feature request and I'm already subscribed. The main |
9 | openejb jpa jaas module javax.persistence.EntityManager; import javax.persistence.EntityManagerFactory; import javax ... EntityManager entityManager; protected Map<String, ?> sharedState = new HashMap ... ) options.get("url")); entityManager = entityManagerFactory.createEntityManager |
1 | [ObjectDB 2.2.6_02] Unexpected exception (Error 990) at com.objectdb.o.OBC.aJ(OBC.java:961); import javax.persistence.EntityManager; import javax.persistence.EntityManagerFactory; import ... .createEntityManagerFactory("ReproducePU"); } public EntityManager getEntityManager() { return emf ... ); edit(chart); } public MomentEntity findMomentEntity(Long id) { EntityManager em |
1 | InternalException seems to work around the problem. In the error version I'm keeping the entityManager at the thread level ... version a new entityManager is opened & closed for each action (load, remove, etc). When an update has occurred the actions are now: Open a new EntityManager Open a new transaction Merge the updated object |
1 | Once served to JSF page via @EJB query bean, many list fields are null (but same query ok after fresh persist in @PostConstruct) TestQuery { @PersistenceContext private EntityManager em; public List<Element> findElements ... . Your TestQuery class uses a transaction scope EntityManager (the default as explained ... findElements, etc. 2. Switch to extended scope EntityManager By doing that you prevent detachment on exit |
