Internal Website Search
91-100 of 100 resultsRefreshSuspected memleak caused by bad state of EntityManager.class:na] at com.objectdb.jpa.EMImpl.rollback(EMImpl.java:295) ~[EMImpl.class:na | |
One transaction or two?()) { pm.currentTransaction().rollback(); } if(!pm.isClosed()) { pm.close | |
EM close causes an exception is closed and that transaction is not rollbacked or committed before the close | |
Working with a cleared cache()) { m_persistenceManager.currentTransaction().rollback | |
ClassCastException: cannot be cast to com.objectdb.spi.TrackableUserType() ) transaction.rollback() if( !pm.isClosed() ) pm.close | |
How to use ObjectDB properly in spring boot application?.getTransaction().isActive()) em.getTransaction().rollback(); } | |
Empty temporary dat files in the temp folder, remove …) and then commit or in the case of errors rollback the transaction and closing | |
Is it possible to commit only specific elements? of them and rollback others. Since JPA supports one transaction per thread, you will have to split | |
Unexpected exception during query, if entity is not enhanced whose transaction was rollback. Only the entity model structure of TCVector remains in | |
NullPointer running multiple client against server.getTransaction().rollback(); throw new ApplicationException("Error putting message on objectdb |