[JBoss JIRA] Created: (JBPM-2794) Constraint vailoation when moving from wait state using timer that result in looping back to the same wait state
4:21 a.m.
Constraint vailoation when moving from wait state using timer that result in looping back
to the same wait state
----------------------------------------------------------------------------------------------------------------
Key: JBPM-2794
URL: https://jira.jboss.org/jira/browse/JBPM-2794
Project: jBPM
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Runtime Engine
Affects Versions: jBPM 4.3, jBPM 4.4
Environment: Windows XP, Java 1.6, Test case, JBoss 5.1.0
Reporter: Maciej Swiderski
Attachments: jbpm-testcase.zip
It is impossible to go from one state where transition is made by timer that goes thru
java activity and decision point and gets back to the same state for retry.
Problem only exists if timer is assigned to a wait state and all nodes are executed
synchnously.
Error that is thrown is:
10:57:13,382 WRN | [JDBCExceptionReporter] SQL Error: -104, SQLState: 23000
10:57:13,382 SEV | [JDBCExceptionReporter] Violation of unique constraint $$: duplicate
value(s) for column(s) $$: SYS_CT_50 in statement [update JBPM4_EXECUTION set
DBVERSION_=?, ACTIVITYNAME_=?, PROCDEFID_=?, HASVARS_=?, NAME_=?, KEY_=?, ID_=?, STATE_=?,
SUSPHISTSTATE_=?, PRIORITY_=?, HISACTINST_=?, PARENT_=?, INSTANCE_=?, SUPEREXEC_=?,
SUBPROCINST_=? where DBID_=? and DBVERSION_=?]
### EXCEPTION ###########################################
10:57:13,382 SEV | [AbstractFlushingEventListener] Could not synchronize database state
with session
org.hibernate.exception.ConstraintViolationException: could not update:
[org.jbpm.pvm.internal.model.ExecutionImpl#15]
Attached is a eclipse project with minimal test case for it that illustrates the problem.
The same test project is attached to discussion on forum.
Workaround is to make one on the nodes between states to be async.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:21 a.m.
New subject: [JBoss JIRA] Updated: (JBPM-2794) Constraint vailoation when moving from wait state using timer that result in looping back to the same wait state
[
https://jira.jboss.org/jira/browse/JBPM-2794?page=com.atlassian.jira.plug...
]
Maciej Swiderski updated JBPM-2794:
-----------------------------------
Attachment: jbpm-testcase.zip
Test case to illustrate the issue
Constraint vailoation when moving from wait state using timer that
result in looping back to the same wait state
----------------------------------------------------------------------------------------------------------------
Key: JBPM-2794
URL: https://jira.jboss.org/jira/browse/JBPM-2794
Project: jBPM
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Runtime Engine
Affects Versions: jBPM 4.4, jBPM 4.3
Environment: Windows XP, Java 1.6, Test case, JBoss 5.1.0
Reporter: Maciej Swiderski
Attachments: jbpm-testcase.zip
It is impossible to go from one state where transition is made by timer that goes thru
java activity and decision point and gets back to the same state for retry.
Problem only exists if timer is assigned to a wait state and all nodes are executed
synchnously.
Error that is thrown is:
10:57:13,382 WRN | [JDBCExceptionReporter] SQL Error: -104, SQLState: 23000
10:57:13,382 SEV | [JDBCExceptionReporter] Violation of unique constraint $$: duplicate
value(s) for column(s) $$: SYS_CT_50 in statement [update JBPM4_EXECUTION set
DBVERSION_=?, ACTIVITYNAME_=?, PROCDEFID_=?, HASVARS_=?, NAME_=?, KEY_=?, ID_=?, STATE_=?,
SUSPHISTSTATE_=?, PRIORITY_=?, HISACTINST_=?, PARENT_=?, INSTANCE_=?, SUPEREXEC_=?,
SUBPROCINST_=? where DBID_=? and DBVERSION_=?]
### EXCEPTION ###########################################
10:57:13,382 SEV | [AbstractFlushingEventListener] Could not synchronize database state
with session
org.hibernate.exception.ConstraintViolationException: could not update:
[org.jbpm.pvm.internal.model.ExecutionImpl#15]
Attached is a eclipse project with minimal test case for it that illustrates the problem.
The same test project is attached to discussion on forum.
Workaround is to make one on the nodes between states to be async.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:41 a.m.
New subject: [JBoss JIRA] Commented: (JBPM-2794) Constraint vailoation when moving from wait state using timer that result in looping back to the same wait state
[
https://jira.jboss.org/jira/browse/JBPM-2794?page=com.atlassian.jira.plug...
]
Maciej Swiderski commented on JBPM-2794:
----------------------------------------
Seems like the issue is in org.jbpm.pvm.internal.id.DatabaseIdComposer.createId method.
It assignes the same id for two timers which causes contraint exception.
Question is how it should be fixed?
Simple solution is to keep the state using variables but I am not sure if that is the
right thing to do - is more like jBPM user solution than developer.
Any suggestions?
Constraint vailoation when moving from wait state using timer that
result in looping back to the same wait state
----------------------------------------------------------------------------------------------------------------
Key: JBPM-2794
URL: https://jira.jboss.org/jira/browse/JBPM-2794
Project: jBPM
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Runtime Engine
Affects Versions: jBPM 4.4, jBPM 4.3
Environment: Windows XP, Java 1.6, Test case, JBoss 5.1.0
Reporter: Maciej Swiderski
Attachments: jbpm-testcase.zip
It is impossible to go from one state where transition is made by timer that goes thru
java activity and decision point and gets back to the same state for retry.
Problem only exists if timer is assigned to a wait state and all nodes are executed
synchnously.
Error that is thrown is:
10:57:13,382 WRN | [JDBCExceptionReporter] SQL Error: -104, SQLState: 23000
10:57:13,382 SEV | [JDBCExceptionReporter] Violation of unique constraint $$: duplicate
value(s) for column(s) $$: SYS_CT_50 in statement [update JBPM4_EXECUTION set
DBVERSION_=?, ACTIVITYNAME_=?, PROCDEFID_=?, HASVARS_=?, NAME_=?, KEY_=?, ID_=?, STATE_=?,
SUSPHISTSTATE_=?, PRIORITY_=?, HISACTINST_=?, PARENT_=?, INSTANCE_=?, SUPEREXEC_=?,
SUBPROCINST_=? where DBID_=? and DBVERSION_=?]
### EXCEPTION ###########################################
10:57:13,382 SEV | [AbstractFlushingEventListener] Could not synchronize database state
with session
org.hibernate.exception.ConstraintViolationException: could not update:
[org.jbpm.pvm.internal.model.ExecutionImpl#15]
Attached is a eclipse project with minimal test case for it that illustrates the problem.
The same test project is attached to discussion on forum.
Workaround is to make one on the nodes between states to be async.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:30 p.m.
New subject: [JBoss JIRA] Commented: (JBPM-2794) Constraint vailoation when moving from wait state using timer that result in looping back to the same wait state
[
https://jira.jboss.org/jira/browse/JBPM-2794?page=com.atlassian.jira.plug...
]
Alejandro Guizar commented on JBPM-2794:
----------------------------------------
I have my doubts about DatabaseIdComposer. IMO more time should have been spent
researching other options such as Hibernate's enhanced identifier generators:
http://docs.jboss.org/hibernate/stable/core/reference/en/html/mapping.htm...
Apart from saving the work of implementing a custom identifier generator, the above
generators were (hopefully) implemented by folks who know the various issues that may
affect the generation process. Plus they are exposed to the entire Hibernate community,
thus increasing the chances that lurking bugs are found and eliminated.
Constraint vailoation when moving from wait state using timer that
result in looping back to the same wait state
----------------------------------------------------------------------------------------------------------------
Key: JBPM-2794
URL: https://jira.jboss.org/jira/browse/JBPM-2794
Project: jBPM
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Runtime Engine
Affects Versions: jBPM 4.4, jBPM 4.3
Environment: Windows XP, Java 1.6, Test case, JBoss 5.1.0
Reporter: Maciej Swiderski
Attachments: jbpm-testcase.zip
It is impossible to go from one state where transition is made by timer that goes thru
java activity and decision point and gets back to the same state for retry.
Problem only exists if timer is assigned to a wait state and all nodes are executed
synchnously.
Error that is thrown is:
10:57:13,382 WRN | [JDBCExceptionReporter] SQL Error: -104, SQLState: 23000
10:57:13,382 SEV | [JDBCExceptionReporter] Violation of unique constraint $$: duplicate
value(s) for column(s) $$: SYS_CT_50 in statement [update JBPM4_EXECUTION set
DBVERSION_=?, ACTIVITYNAME_=?, PROCDEFID_=?, HASVARS_=?, NAME_=?, KEY_=?, ID_=?, STATE_=?,
SUSPHISTSTATE_=?, PRIORITY_=?, HISACTINST_=?, PARENT_=?, INSTANCE_=?, SUPEREXEC_=?,
SUBPROCINST_=? where DBID_=? and DBVERSION_=?]
### EXCEPTION ###########################################
10:57:13,382 SEV | [AbstractFlushingEventListener] Could not synchronize database state
with session
org.hibernate.exception.ConstraintViolationException: could not update:
[org.jbpm.pvm.internal.model.ExecutionImpl#15]
Attached is a eclipse project with minimal test case for it that illustrates the problem.
The same test project is attached to discussion on forum.
Workaround is to make one on the nodes between states to be async.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:05 a.m.
New subject: [JBoss JIRA] Commented: (JBPM-2794) Constraint vailoation when moving from wait state using timer that result in looping back to the same wait state
[
https://jira.jboss.org/jira/browse/JBPM-2794?page=com.atlassian.jira.plug...
]
Huisheng Xu commented on JBPM-2794:
-----------------------------------
The simplest way to fix this issue is append execution.getDbid() to the compositeId.
String executionId = base + "." + executionPart + "."
+ execution.getDbid();
the execution.getDbid() always created before invoke execution.composeIds(), so it could
make execution.getId() unique.
Constraint vailoation when moving from wait state using timer that
result in looping back to the same wait state
----------------------------------------------------------------------------------------------------------------
Key: JBPM-2794
URL: https://jira.jboss.org/jira/browse/JBPM-2794
Project: jBPM
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Runtime Engine
Affects Versions: jBPM 4.4, jBPM 4.3
Environment: Windows XP, Java 1.6, Test case, JBoss 5.1.0
Reporter: Maciej Swiderski
Attachments: jbpm-testcase.zip
It is impossible to go from one state where transition is made by timer that goes thru
java activity and decision point and gets back to the same state for retry.
Problem only exists if timer is assigned to a wait state and all nodes are executed
synchnously.
Error that is thrown is:
10:57:13,382 WRN | [JDBCExceptionReporter] SQL Error: -104, SQLState: 23000
10:57:13,382 SEV | [JDBCExceptionReporter] Violation of unique constraint $$: duplicate
value(s) for column(s) $$: SYS_CT_50 in statement [update JBPM4_EXECUTION set
DBVERSION_=?, ACTIVITYNAME_=?, PROCDEFID_=?, HASVARS_=?, NAME_=?, KEY_=?, ID_=?, STATE_=?,
SUSPHISTSTATE_=?, PRIORITY_=?, HISACTINST_=?, PARENT_=?, INSTANCE_=?, SUPEREXEC_=?,
SUBPROCINST_=? where DBID_=? and DBVERSION_=?]
### EXCEPTION ###########################################
10:57:13,382 SEV | [AbstractFlushingEventListener] Could not synchronize database state
with session
org.hibernate.exception.ConstraintViolationException: could not update:
[org.jbpm.pvm.internal.model.ExecutionImpl#15]
Attached is a eclipse project with minimal test case for it that illustrates the problem.
The same test project is attached to discussion on forum.
Workaround is to make one on the nodes between states to be async.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:51 p.m.
New subject: [JBoss JIRA] Updated: (JBPM-2794) Constraint vailoation when moving from wait state using timer that result in looping back to the same wait state
[
https://jira.jboss.org/jira/browse/JBPM-2794?page=com.atlassian.jira.plug...
]
Alejandro Guizar updated JBPM-2794:
-----------------------------------
Comment: was deleted
Constraint vailoation when moving from wait state using timer that
result in looping back to the same wait state
----------------------------------------------------------------------------------------------------------------
Key: JBPM-2794
URL: https://jira.jboss.org/jira/browse/JBPM-2794
Project: jBPM
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Runtime Engine
Affects Versions: jBPM 4.3, jBPM 4.4
Environment: Windows XP, Java 1.6, Test case, JBoss 5.1.0
Reporter: Maciej Swiderski
Attachments: jbpm-testcase.zip
It is impossible to go from one state where transition is made by timer that goes thru
java activity and decision point and gets back to the same state for retry.
Problem only exists if timer is assigned to a wait state and all nodes are executed
synchnously.
Error that is thrown is:
10:57:13,382 WRN | [JDBCExceptionReporter] SQL Error: -104, SQLState: 23000
10:57:13,382 SEV | [JDBCExceptionReporter] Violation of unique constraint $$: duplicate
value(s) for column(s) $$: SYS_CT_50 in statement [update JBPM4_EXECUTION set
DBVERSION_=?, ACTIVITYNAME_=?, PROCDEFID_=?, HASVARS_=?, NAME_=?, KEY_=?, ID_=?, STATE_=?,
SUSPHISTSTATE_=?, PRIORITY_=?, HISACTINST_=?, PARENT_=?, INSTANCE_=?, SUPEREXEC_=?,
SUBPROCINST_=? where DBID_=? and DBVERSION_=?]
### EXCEPTION ###########################################
10:57:13,382 SEV | [AbstractFlushingEventListener] Could not synchronize database state
with session
org.hibernate.exception.ConstraintViolationException: could not update:
[org.jbpm.pvm.internal.model.ExecutionImpl#15]
Attached is a eclipse project with minimal test case for it that illustrates the problem.
The same test project is attached to discussion on forum.
Workaround is to make one on the nodes between states to be async.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:53 p.m.
New subject: [JBoss JIRA] Updated: (JBPM-2794) Constraint vailoation when moving from wait state using timer that result in looping back to the same wait state
[
https://jira.jboss.org/jira/browse/JBPM-2794?page=com.atlassian.jira.plug...
]
Alejandro Guizar updated JBPM-2794:
-----------------------------------
Fix Version/s: jBPM 4.4
Assignee: Alejandro Guizar
Constraint vailoation when moving from wait state using timer that
result in looping back to the same wait state
----------------------------------------------------------------------------------------------------------------
Key: JBPM-2794
URL: https://jira.jboss.org/jira/browse/JBPM-2794
Project: jBPM
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Runtime Engine
Affects Versions: jBPM 4.3, jBPM 4.4
Environment: Windows XP, Java 1.6, Test case, JBoss 5.1.0
Reporter: Maciej Swiderski
Assignee: Alejandro Guizar
Fix For: jBPM 4.4
Attachments: jbpm-testcase.zip
It is impossible to go from one state where transition is made by timer that goes thru
java activity and decision point and gets back to the same state for retry.
Problem only exists if timer is assigned to a wait state and all nodes are executed
synchnously.
Error that is thrown is:
10:57:13,382 WRN | [JDBCExceptionReporter] SQL Error: -104, SQLState: 23000
10:57:13,382 SEV | [JDBCExceptionReporter] Violation of unique constraint $$: duplicate
value(s) for column(s) $$: SYS_CT_50 in statement [update JBPM4_EXECUTION set
DBVERSION_=?, ACTIVITYNAME_=?, PROCDEFID_=?, HASVARS_=?, NAME_=?, KEY_=?, ID_=?, STATE_=?,
SUSPHISTSTATE_=?, PRIORITY_=?, HISACTINST_=?, PARENT_=?, INSTANCE_=?, SUPEREXEC_=?,
SUBPROCINST_=? where DBID_=? and DBVERSION_=?]
### EXCEPTION ###########################################
10:57:13,382 SEV | [AbstractFlushingEventListener] Could not synchronize database state
with session
org.hibernate.exception.ConstraintViolationException: could not update:
[org.jbpm.pvm.internal.model.ExecutionImpl#15]
Attached is a eclipse project with minimal test case for it that illustrates the problem.
The same test project is attached to discussion on forum.
Workaround is to make one on the nodes between states to be async.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:55 p.m.
New subject: [JBoss JIRA] Updated: (JBPM-2794) Constraint vailoation when moving from wait state using timer that result in looping back to the same wait state
[
https://jira.jboss.org/jira/browse/JBPM-2794?page=com.atlassian.jira.plug...
]
Alejandro Guizar updated JBPM-2794:
-----------------------------------
Affects Version/s: (was: jBPM 4.4)
Constraint vailoation when moving from wait state using timer that
result in looping back to the same wait state
----------------------------------------------------------------------------------------------------------------
Key: JBPM-2794
URL: https://jira.jboss.org/jira/browse/JBPM-2794
Project: jBPM
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Runtime Engine
Affects Versions: jBPM 4.3
Environment: Windows XP, Java 1.6, Test case, JBoss 5.1.0
Reporter: Maciej Swiderski
Assignee: Alejandro Guizar
Fix For: jBPM 4.4
Attachments: jbpm-testcase.zip
It is impossible to go from one state where transition is made by timer that goes thru
java activity and decision point and gets back to the same state for retry.
Problem only exists if timer is assigned to a wait state and all nodes are executed
synchnously.
Error that is thrown is:
10:57:13,382 WRN | [JDBCExceptionReporter] SQL Error: -104, SQLState: 23000
10:57:13,382 SEV | [JDBCExceptionReporter] Violation of unique constraint $$: duplicate
value(s) for column(s) $$: SYS_CT_50 in statement [update JBPM4_EXECUTION set
DBVERSION_=?, ACTIVITYNAME_=?, PROCDEFID_=?, HASVARS_=?, NAME_=?, KEY_=?, ID_=?, STATE_=?,
SUSPHISTSTATE_=?, PRIORITY_=?, HISACTINST_=?, PARENT_=?, INSTANCE_=?, SUPEREXEC_=?,
SUBPROCINST_=? where DBID_=? and DBVERSION_=?]
### EXCEPTION ###########################################
10:57:13,382 SEV | [AbstractFlushingEventListener] Could not synchronize database state
with session
org.hibernate.exception.ConstraintViolationException: could not update:
[org.jbpm.pvm.internal.model.ExecutionImpl#15]
Attached is a eclipse project with minimal test case for it that illustrates the problem.
The same test project is attached to discussion on forum.
Workaround is to make one on the nodes between states to be async.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:02 a.m.
New subject: [JBoss JIRA] Commented: (JBPM-2794) Constraint vailoation when moving from wait state using timer that result in looping back to the same wait state
[
https://jira.jboss.org/jira/browse/JBPM-2794?page=com.atlassian.jira.plug...
]
O S commented on JBPM-2794:
---------------------------
please refer to the following thread as an additional test case to verify that the issue
described is the same and that it's fixed:
http://community.jboss.org/thread/150965?tstart=0
Constraint vailoation when moving from wait state using timer that
result in looping back to the same wait state
----------------------------------------------------------------------------------------------------------------
Key: JBPM-2794
URL: https://jira.jboss.org/jira/browse/JBPM-2794
Project: jBPM
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Runtime Engine
Affects Versions: jBPM 4.3
Environment: Windows XP, Java 1.6, Test case, JBoss 5.1.0
Reporter: Maciej Swiderski
Assignee: Alejandro Guizar
Fix For: jBPM 4.4
Attachments: jbpm-testcase.zip
It is impossible to go from one state where transition is made by timer that goes thru
java activity and decision point and gets back to the same state for retry.
Problem only exists if timer is assigned to a wait state and all nodes are executed
synchnously.
Error that is thrown is:
10:57:13,382 WRN | [JDBCExceptionReporter] SQL Error: -104, SQLState: 23000
10:57:13,382 SEV | [JDBCExceptionReporter] Violation of unique constraint $$: duplicate
value(s) for column(s) $$: SYS_CT_50 in statement [update JBPM4_EXECUTION set
DBVERSION_=?, ACTIVITYNAME_=?, PROCDEFID_=?, HASVARS_=?, NAME_=?, KEY_=?, ID_=?, STATE_=?,
SUSPHISTSTATE_=?, PRIORITY_=?, HISACTINST_=?, PARENT_=?, INSTANCE_=?, SUPEREXEC_=?,
SUBPROCINST_=? where DBID_=? and DBVERSION_=?]
### EXCEPTION ###########################################
10:57:13,382 SEV | [AbstractFlushingEventListener] Could not synchronize database state
with session
org.hibernate.exception.ConstraintViolationException: could not update:
[org.jbpm.pvm.internal.model.ExecutionImpl#15]
Attached is a eclipse project with minimal test case for it that illustrates the problem.
The same test project is attached to discussion on forum.
Workaround is to make one on the nodes between states to be async.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:30 a.m.
New subject: [JBoss JIRA] Updated: (JBPM-2794) Constraint vailoation when moving from wait state using timer that result in looping back to the same wait state
[
https://jira.jboss.org/jira/browse/JBPM-2794?page=com.atlassian.jira.plug...
]
Huisheng Xu updated JBPM-2794:
------------------------------
Attachment: JBPM-2794.patch
I upload a patch with letting DatabaseIdComposer appending execution.getDbid() after the
execution.getName(). There is also a testcase to verify the patch.
And I have to update HistoryActivityInstanceQueryTest for modification of
DatabaseIdComposer, because the executionId no longer be the processInstance +
'.' + activityName.
Constraint vailoation when moving from wait state using timer that
result in looping back to the same wait state
----------------------------------------------------------------------------------------------------------------
Key: JBPM-2794
URL: https://jira.jboss.org/jira/browse/JBPM-2794
Project: jBPM
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Runtime Engine
Affects Versions: jBPM 4.3
Environment: Windows XP, Java 1.6, Test case, JBoss 5.1.0
Reporter: Maciej Swiderski
Assignee: Alejandro Guizar
Fix For: jBPM 4.4
Attachments: JBPM-2794.patch, jbpm-testcase.zip
It is impossible to go from one state where transition is made by timer that goes thru
java activity and decision point and gets back to the same state for retry.
Problem only exists if timer is assigned to a wait state and all nodes are executed
synchnously.
Error that is thrown is:
10:57:13,382 WRN | [JDBCExceptionReporter] SQL Error: -104, SQLState: 23000
10:57:13,382 SEV | [JDBCExceptionReporter] Violation of unique constraint $$: duplicate
value(s) for column(s) $$: SYS_CT_50 in statement [update JBPM4_EXECUTION set
DBVERSION_=?, ACTIVITYNAME_=?, PROCDEFID_=?, HASVARS_=?, NAME_=?, KEY_=?, ID_=?, STATE_=?,
SUSPHISTSTATE_=?, PRIORITY_=?, HISACTINST_=?, PARENT_=?, INSTANCE_=?, SUPEREXEC_=?,
SUBPROCINST_=? where DBID_=? and DBVERSION_=?]
### EXCEPTION ###########################################
10:57:13,382 SEV | [AbstractFlushingEventListener] Could not synchronize database state
with session
org.hibernate.exception.ConstraintViolationException: could not update:
[org.jbpm.pvm.internal.model.ExecutionImpl#15]
Attached is a eclipse project with minimal test case for it that illustrates the problem.
The same test project is attached to discussion on forum.
Workaround is to make one on the nodes between states to be async.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:02 p.m.
New subject: [JBoss JIRA] Updated: (JBPM-2794) Constraint vailoation when moving from wait state using timer that result in looping back to the same wait state
[
https://jira.jboss.org/jira/browse/JBPM-2794?page=com.atlassian.jira.plug...
]
Huisheng Xu updated JBPM-2794:
------------------------------
Attachment: JBPM-2794-2010-05-11.patch
add testcase for O.S's scenairo. JBPM-2794-2010-05-11.patch.
Constraint vailoation when moving from wait state using timer that
result in looping back to the same wait state
----------------------------------------------------------------------------------------------------------------
Key: JBPM-2794
URL: https://jira.jboss.org/jira/browse/JBPM-2794
Project: jBPM
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Runtime Engine
Affects Versions: jBPM 4.3
Environment: Windows XP, Java 1.6, Test case, JBoss 5.1.0
Reporter: Maciej Swiderski
Assignee: Alejandro Guizar
Fix For: jBPM 4.4
Attachments: JBPM-2794-2010-05-11.patch, JBPM-2794.patch, jbpm-testcase.zip
It is impossible to go from one state where transition is made by timer that goes thru
java activity and decision point and gets back to the same state for retry.
Problem only exists if timer is assigned to a wait state and all nodes are executed
synchnously.
Error that is thrown is:
10:57:13,382 WRN | [JDBCExceptionReporter] SQL Error: -104, SQLState: 23000
10:57:13,382 SEV | [JDBCExceptionReporter] Violation of unique constraint $$: duplicate
value(s) for column(s) $$: SYS_CT_50 in statement [update JBPM4_EXECUTION set
DBVERSION_=?, ACTIVITYNAME_=?, PROCDEFID_=?, HASVARS_=?, NAME_=?, KEY_=?, ID_=?, STATE_=?,
SUSPHISTSTATE_=?, PRIORITY_=?, HISACTINST_=?, PARENT_=?, INSTANCE_=?, SUPEREXEC_=?,
SUBPROCINST_=? where DBID_=? and DBVERSION_=?]
### EXCEPTION ###########################################
10:57:13,382 SEV | [AbstractFlushingEventListener] Could not synchronize database state
with session
org.hibernate.exception.ConstraintViolationException: could not update:
[org.jbpm.pvm.internal.model.ExecutionImpl#15]
Attached is a eclipse project with minimal test case for it that illustrates the problem.
The same test project is attached to discussion on forum.
Workaround is to make one on the nodes between states to be async.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:19 p.m.
New subject: [JBoss JIRA] Assigned: (JBPM-2794) Constraint vailoation when moving from wait state using timer that result in looping back to the same wait state
[
https://jira.jboss.org/jira/browse/JBPM-2794?page=com.atlassian.jira.plug...
]
Huisheng Xu reassigned JBPM-2794:
---------------------------------
Assignee: Huisheng Xu (was: Alejandro Guizar)
Constraint vailoation when moving from wait state using timer that
result in looping back to the same wait state
----------------------------------------------------------------------------------------------------------------
Key: JBPM-2794
URL: https://jira.jboss.org/jira/browse/JBPM-2794
Project: jBPM
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Runtime Engine
Affects Versions: jBPM 4.3
Environment: Windows XP, Java 1.6, Test case, JBoss 5.1.0
Reporter: Maciej Swiderski
Assignee: Huisheng Xu
Fix For: jBPM 4.4
Attachments: JBPM-2794-2010-05-11.patch, JBPM-2794.patch, jbpm-testcase.zip
It is impossible to go from one state where transition is made by timer that goes thru
java activity and decision point and gets back to the same state for retry.
Problem only exists if timer is assigned to a wait state and all nodes are executed
synchnously.
Error that is thrown is:
10:57:13,382 WRN | [JDBCExceptionReporter] SQL Error: -104, SQLState: 23000
10:57:13,382 SEV | [JDBCExceptionReporter] Violation of unique constraint $$: duplicate
value(s) for column(s) $$: SYS_CT_50 in statement [update JBPM4_EXECUTION set
DBVERSION_=?, ACTIVITYNAME_=?, PROCDEFID_=?, HASVARS_=?, NAME_=?, KEY_=?, ID_=?, STATE_=?,
SUSPHISTSTATE_=?, PRIORITY_=?, HISACTINST_=?, PARENT_=?, INSTANCE_=?, SUPEREXEC_=?,
SUBPROCINST_=? where DBID_=? and DBVERSION_=?]
### EXCEPTION ###########################################
10:57:13,382 SEV | [AbstractFlushingEventListener] Could not synchronize database state
with session
org.hibernate.exception.ConstraintViolationException: could not update:
[org.jbpm.pvm.internal.model.ExecutionImpl#15]
Attached is a eclipse project with minimal test case for it that illustrates the problem.
The same test project is attached to discussion on forum.
Workaround is to make one on the nodes between states to be async.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:25 p.m.
New subject: [JBoss JIRA] Resolved: (JBPM-2794) Constraint vailoation when moving from wait state using timer that result in looping back to the same wait state
[
https://jira.jboss.org/jira/browse/JBPM-2794?page=com.atlassian.jira.plug...
]
Huisheng Xu resolved JBPM-2794.
-------------------------------
Resolution: Done
Constraint vailoation when moving from wait state using timer that
result in looping back to the same wait state
----------------------------------------------------------------------------------------------------------------
Key: JBPM-2794
URL: https://jira.jboss.org/jira/browse/JBPM-2794
Project: jBPM
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Runtime Engine
Affects Versions: jBPM 4.3
Environment: Windows XP, Java 1.6, Test case, JBoss 5.1.0
Reporter: Maciej Swiderski
Assignee: Huisheng Xu
Fix For: jBPM 4.4
Attachments: JBPM-2794-2010-05-11.patch, JBPM-2794.patch, jbpm-testcase.zip
It is impossible to go from one state where transition is made by timer that goes thru
java activity and decision point and gets back to the same state for retry.
Problem only exists if timer is assigned to a wait state and all nodes are executed
synchnously.
Error that is thrown is:
10:57:13,382 WRN | [JDBCExceptionReporter] SQL Error: -104, SQLState: 23000
10:57:13,382 SEV | [JDBCExceptionReporter] Violation of unique constraint $$: duplicate
value(s) for column(s) $$: SYS_CT_50 in statement [update JBPM4_EXECUTION set
DBVERSION_=?, ACTIVITYNAME_=?, PROCDEFID_=?, HASVARS_=?, NAME_=?, KEY_=?, ID_=?, STATE_=?,
SUSPHISTSTATE_=?, PRIORITY_=?, HISACTINST_=?, PARENT_=?, INSTANCE_=?, SUPEREXEC_=?,
SUBPROCINST_=? where DBID_=? and DBVERSION_=?]
### EXCEPTION ###########################################
10:57:13,382 SEV | [AbstractFlushingEventListener] Could not synchronize database state
with session
org.hibernate.exception.ConstraintViolationException: could not update:
[org.jbpm.pvm.internal.model.ExecutionImpl#15]
Attached is a eclipse project with minimal test case for it that illustrates the problem.
The same test project is attached to discussion on forum.
Workaround is to make one on the nodes between states to be async.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5258
days inactive
5344
days old
12 comments
4 participants
participants (4)
-
Alejandro Guizar (JIRA) -
Huisheng Xu (JIRA)
-
Maciej Swiderski (JIRA)
-
O S (JIRA)