org.apache.openjpa.persistence.PersistenceException

Cannot call commit when using distributed transactions

Samebug tips0

We couldn't find tips for this exception.

Don't give up yet. Paste your full stack trace to get a solution.

Solutions on the web3

  • via Unknown by 666705,
  • via Unknown by Rick Curtis,
  • Stack trace

    • org.apache.openjpa.persistence.PersistenceException: Cannot call commit when using distributed transactions at org.apache.openjpa.jdbc.sql.SQLExceptions.getStore(SQLExceptions.java:92) at org.apache.openjpa.jdbc.sql.SQLExceptions.getStore(SQLExceptions.java:64) at org.apache.openjpa.jdbc.sql.SQLExceptions.getStore(SQLExceptions.java:41) at org.apache.openjpa.jdbc.kernel.AbstractJDBCSeq.closeConnection(AbstractJDBCSeq.java:163) at org.apache.openjpa.jdbc.kernel.NativeJDBCSeq.nextInternal(NativeJDBCSeq.java:206) at org.apache.openjpa.jdbc.kernel.AbstractJDBCSeq.next(AbstractJDBCSeq.java:54) at org.apache.openjpa.util.ImplHelper.generateValue(ImplHelper.java:159) at org.apache.openjpa.util.ImplHelper.generateFieldValue(ImplHelper.java:143) at org.apache.openjpa.jdbc.kernel.JDBCStoreManager.assignField(JDBCStoreManager.java:554) at org.apache.openjpa.util.ApplicationIds.assign(ApplicationIds.java:435) at org.apache.openjpa.util.ApplicationIds.assign(ApplicationIds.java:420) at org.apache.openjpa.jdbc.kernel.JDBCStoreManager.assignObjectId(JDBCStoreManager.java:538) at org.apache.openjpa.kernel.DelegatingStoreManager.assignObjectId(DelegatingStoreManager.java:131) at org.apache.openjpa.kernel.DelegatingStoreManager.assignObjectId(DelegatingStoreManager.java:131) at org.apache.openjpa.kernel.StateManagerImpl.assignObjectId(StateManagerImpl.java:471) at org.apache.openjpa.kernel.StateManagerImpl.assignField(StateManagerImpl.java:555) at org.apache.openjpa.kernel.StateManagerImpl.beforeAccessField(StateManagerImpl.java:1354) at org.apache.openjpa.kernel.StateManagerImpl.accessingField(StateManagerImpl.java:1337)

    Write tip

    You have a different solution? A short tip here would help you and many other users who saw this issue last week.

    Users with the same issue

    We couldn't find other users who have seen this exception.