Searched on Google with the first line of a JAVA stack trace?

We can recommend more relevant solutions and speed up debugging when you paste your entire stack trace with the exception message. Try a sample exception.

Recommended solutions based on your search

Solutions on the web

via Stack Overflow by Sean Coetzee
, 1 year ago
The transaction has been rolled back. See the nested exceptions for details on the errors that occurred. FailedObject: entities.Fund@1097fef5
via Stack Overflow by akshay
, 2 years ago
The transaction has been rolled back. See the nested exceptions for details on the errors that occurred.
via grokbase.com by Unknown author, 2 years ago
The transaction has been rolled back. See the nested exceptions for details on the errors that occurred.
via Stack Overflow by Milan
, 1 year ago
The transaction has been rolled back. See the nested exceptions for details on the errors that occurred.
via sourceforge.net by Unknown author, 2 years ago
The transaction has been rolled backSee the nested exceptions for details on the errors that occurred.
via openjpa-users by Datin Benoit, 1 year ago
The transaction has been rolled back. See the nested exceptions for details on the errors that occurred. FailedObject: xms.common.beans.bus.planning.schedule.B_ScheduleElement-224
org.apache.openjpa.persistence.PersistenceException: 
The transaction has been rolled back.  See the nested exceptions for details on the errors that occurred.
FailedObject: entities.Fund@1097fef5	at org.apache.openjpa.kernel.BrokerImpl.newFlushException(BrokerImpl.java:2370)	at org.apache.openjpa.kernel.BrokerImpl.flush(BrokerImpl.java:2207)	at org.apache.openjpa.kernel.BrokerImpl.flushSafe(BrokerImpl.java:2105)	at org.apache.openjpa.kernel.BrokerImpl.flush(BrokerImpl.java:1876)	at org.apache.openjpa.kernel.DelegatingBroker.flush(DelegatingBroker.java:1045)	at org.apache.openjpa.persistence.EntityManagerImpl.flush(EntityManagerImpl.java:663)	at org.jboss.as.jpa.container.AbstractEntityManager.flush(AbstractEntityManager.java:457)