]
Alexis Seigneurin updated JBPM-2303:
------------------------------------
Attachment: fork-test6.jpdl.xml
Exception with a process containing a fork/join
-----------------------------------------------
Key: JBPM-2303
URL:
https://jira.jboss.org/jira/browse/JBPM-2303
Project: JBoss jBPM
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: jBPM 4.0.0.Beta2
Environment: Tested with 4.0.0.Beta2 and 4.0-SNAPSHOT from SVN.
Reporter: Alexis Seigneurin
Attachments: Bug.java, fork-test5.jpdl.xml, fork-test6.jpdl.xml
I have a process which contains a "fork" to 3 tasks. 2 of these tasks lead to a
"join". I follow the first transition to the join without problem. Then, when I
follow the second transition, i get an exception.
I will attach the source code and the process definition.
2009-06-02 13:37:40,634 DEBUG [org.hibernate.SQL] - <
delete
from
JBPM4_EXECUTION
where
DBID_=?
and DBVERSION_=?>
2009-06-02 13:37:40,649 WARN [org.hibernate.util.JDBCExceptionReporter] - <SQL Error:
0, SQLState: 23503>
2009-06-02 13:37:40,649 ERROR [org.hibernate.util.JDBCExceptionReporter] - <ERROR:
update or delete on "jbpm4_execution" violates foreign key constraint
"fk_exec_instance" on "jbpm4_execution"
Détail : Key (dbid_)=(105) is still referenced from table
"jbpm4_execution".>
2009-06-02 13:37:40,649 ERROR [org.hibernate.event.def.AbstractFlushingEventListener] -
<Could not synchronize database state with session>
org.hibernate.exception.ConstraintViolationException: could not delete:
[org.jbpm.jpdl.internal.model.JpdlExecution#105]
at org.hibernate.exception.SQLStateConverter.convert(SQLStateConverter.java:94)
at org.hibernate.exception.JDBCExceptionHelper.convert(JDBCExceptionHelper.java:66)
at
org.hibernate.persister.entity.AbstractEntityPersister.delete(AbstractEntityPersister.java:2569)
at
org.hibernate.persister.entity.AbstractEntityPersister.delete(AbstractEntityPersister.java:2725)
at org.hibernate.action.EntityDeleteAction.execute(EntityDeleteAction.java:97)
at org.hibernate.engine.ActionQueue.execute(ActionQueue.java:279)
at org.hibernate.engine.ActionQueue.executeActions(ActionQueue.java:263)
at org.hibernate.engine.ActionQueue.executeActions(ActionQueue.java:172)
at
org.hibernate.event.def.AbstractFlushingEventListener.performExecutions(AbstractFlushingEventListener.java:321)
at
org.hibernate.event.def.DefaultFlushEventListener.onFlush(DefaultFlushEventListener.java:50)
at org.hibernate.impl.SessionImpl.flush(SessionImpl.java:1027)
at
org.jbpm.pvm.internal.tx.HibernateSessionResource.prepare(HibernateSessionResource.java:54)
at org.jbpm.pvm.internal.tx.StandardTransaction.commit(StandardTransaction.java:106)
at org.jbpm.pvm.internal.tx.StandardTransaction.complete(StandardTransaction.java:65)
at
org.jbpm.pvm.internal.tx.StandardTransactionInterceptor.execute(StandardTransactionInterceptor.java:61)
at
org.jbpm.pvm.internal.svc.EnvironmentInterceptor.execute(EnvironmentInterceptor.java:54)
at org.jbpm.pvm.internal.svc.RetryInterceptor.execute(RetryInterceptor.java:55)
at org.jbpm.pvm.internal.svc.TaskServiceImpl.completeTask(TaskServiceImpl.java:68)
at fr.idm.Bug.main(Bug.java:41)
Caused by: org.postgresql.util.PSQLException: ERROR: update or delete on
"jbpm4_execution" violates foreign key constraint "fk_exec_instance"
on "jbpm4_execution"
Détail : Key (dbid_)=(105) is still referenced from table "jbpm4_execution".
at
org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:1608)
at org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:1343)
at org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:194)
at org.postgresql.jdbc2.AbstractJdbc2Statement.execute(AbstractJdbc2Statement.java:451)
at
org.postgresql.jdbc2.AbstractJdbc2Statement.executeWithFlags(AbstractJdbc2Statement.java:350)
at
org.postgresql.jdbc2.AbstractJdbc2Statement.executeUpdate(AbstractJdbc2Statement.java:304)
at
org.hibernate.persister.entity.AbstractEntityPersister.delete(AbstractEntityPersister.java:2551)
... 16 more
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: