[jbpm-issues] [JBoss JIRA] Commented: (JBPM-1987) create optimistic locking test
[
https://jira.jboss.org/jira/browse/JBPM-1987?page=com.atlassian.jira.plug...
]
Joram Barrez commented on JBPM-1987:
------------------------------------
Added module 'test-concurrent'.
Added basic test scenarios: normal usage/ async fork/timer vs signal.
Added convenience classes and methods for testing concurrent scenario's with
synchronization points.
Writing new concurrent scenario's should be easy with this infrastructure.
Deferred to a future release as a pointer, to check if new scenario's have popped up
create optimistic locking test
------------------------------
Key: JBPM-1987
URL: https://jira.jboss.org/jira/browse/JBPM-1987
Project: JBoss jBPM
Issue Type: Task
Security Level: Public(Everyone can see)
Reporter: Tom Baeyens
Assignee: Joram Barrez
Priority: Minor
Fix For: jBPM 4.x
create a test that produces an optimistic locking failure.
this will
1) verify that the db isolation works correctly
2) allow us to see how this gets logged. (in jbpm 3, a lot of people complained because
there were still SOSEs in the logs)
--
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