org.apache.openjpa.persistence.RollbackException: 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

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 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
via openjpa-users by Kevin Sutter, 5 months 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
via jpab.org by Unknown author, 1 year ago
The transaction has been rolled back. See the nested exceptions for details on the errors that occurred. FailedObject: org.jpab.node.Node@3a0ab1
via jpab.org by Unknown author, 1 year ago
The transaction has been rolled back. See the nested exceptions for details on the errors that occurred. FailedObject: org.jpab.node.Node@3a0ab1
via nabble.com by Unknown author, 1 year ago
Optimistic locking errors were detected when flushing to the data store.  The following objects may have been concurrently modified in another transaction: [org.cliftonfarm.feed.domain.Grouping-1069, org.cliftonfarm.feed.domain.Ingredient-1107, org.cliftonfarm.feed.domain.Step-1119]
via Coderanch by sachin y deshpande, 11 months ago
The transaction has been rolled back. See the nested exceptions for details on the errors that occurred.
org.apache.openjpa.persistence.RollbackException: 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
at xms.xserver.common.JPAPersistenceTool.commitTransaction(JPAPersistenceTool.java:193)
at xms.xserver.fe.bus.planning.PlanningManager.updateScheduleElement(PlanningManager.java:2126)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at xms.common.util.annotationshandler.RmwoAnnotationHandler.invoke(RmwoAnnotationHandler.java:95)
at com.sun.proxy.$Proxy50.updateScheduleElement(Unknown Source)
at xms.xserver.fe.bus.planning.actions.UpdateScheduleElementAction.execute(UpdateScheduleElementAction.java:63)
at xms.common.xcommand.XCommand.performAction(XCommand.java:219)
at xms.xserver.fe.inter.impl.sys.session.I_Server_impl_tie.sendCommand(I_Server_impl_tie.java:715)
at xms.xserver.fe.inter.gen.sys.session.I_ServerPOATie.sendCommand(I_ServerPOATie.java:204)
at xms.xserver.fe.inter.gen.sys.session.I_ServerPOA._invoke_sendCommand(I_ServerPOA.java:350)
at xms.xserver.fe.inter.gen.sys.session.I_ServerPOA.access$3500(I_ServerPOA.java:8)
at xms.xserver.fe.inter.gen.sys.session.I_ServerPOA$Operation_sendCommand.invoke(I_ServerPOA.java:571)
at xms.xserver.fe.inter.gen.sys.session.I_ServerPOA._invoke(I_ServerPOA.java:83)
at org.openorb.orb.adapter.poa.POA.dispatch(POA.java:1493)
at org.openorb.orb.net.AbstractServerRequest.dispatch(AbstractServerRequest.java:889)
at org.openorb.orb.net.ServerManagerImpl.serve_request(ServerManagerImpl.java:1601)
at org.openorb.orb.net.ServerManagerImpl.thread_pool_main(ServerManagerImpl.java:1526)
at org.openorb.orb.net.ServerManagerImpl.access$9(ServerManagerImpl.java:1382)
at org.openorb.orb.net.ServerManagerImpl$PoolThread.run(ServerManagerImpl.java:2886)

Users with the same issue

You are the first who have seen this exception.

Write tip

Know the solutions? Share your knowledge to help other developers to debug faster.