"matterbury" wrote : | So, my questions are: is there any other reason the update could fail? how might I track down what's going wrong (I have turned on arjuna's DEBUG but it doesn't give enough detail for this)? | | FWIW, the actual exception is: | | | 2009-05-19 09:50:42,557 DEBUG [org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreEntityCommand.AddressEB] Executing SQL: UPDATE ADDRESS SET CITY=?, STATE=?, SUBURB_CODE=?, COUNTRY=?, TELEPHONE=?, EMAIL=?, cname=? WHERE LINE1=? | | 2009-05-19 09:50:42,561 DEBUG [com.arjuna.ats.jta.logging.logger] BaseTransaction.getStatus | | 2009-05-19 09:50:52,014 DEBUG [com.arjuna.ats.jta.logging.logger] TransactionImple.setRollbackOnly | | 2009-05-19 09:50:52,014 WARN [com.arjuna.ats.arjuna.logging.arjLoggerI18N] [com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator_2] TwoPhaseCoordinator.beforeCompletion - failed for com.arjuna.ats.internal.jta.resources.arjunacore.synchronizationim...@1971f66 | | javax.ejb.EJBException: Update failed. Expected one affected row: rowsAffected=0, id=875 Main St | | at org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreEntityCommand.execute(JDBCStoreEntityCommand.java:169) | | at org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreManager.storeEntity(JDBCStoreManager.java:666) | | at org.jboss.ejb.plugins.CMPPersistenceManager.storeEntity(CMPPersistenceManager.java:428) | | : | | : | | : | | |
Ask the question in the EJB forum. If your quess is correct then the correct transaction is not associated with the thread when you do the prepare() and so the JDBCStoreManager() is trying to execute the storeEntity() during a transaction synchronization callback in the wrong transaction (or more probably no transaction)? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4236025#4236025 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4236025 _______________________________________________ jboss-user mailing list [email protected] https://lists.jboss.org/mailman/listinfo/jboss-user
