2:07 a.m.
Possible problem in concurrent signalling from multiple threads
---------------------------------------------------------------
Key: JBPM-1071
URL: http://jira.jboss.com/jira/browse/JBPM-1071
Project: JBoss jBPM
Issue Type: Bug
Components: Core Engine
Affects Versions: jBPM jPDL 3.2.2
Environment: Linux 2.6.21-1.3228.fc7 #1 SMP Tue Jun 12 14:56:37 EDT 2007 x86_64
x86_64 x86_64 GNU/Linux
MySQL 5.0.22
Reporter: Jiri Pechanec
Assigned To: Tom Baeyens
Priority: Critical
Attachments: expl.tar.gz
Attached is a simple test case that
1) Deploys process definition with two nodes
2) Starts the process instance that will go to the wait state on first node
3) Starts 20 threads that tries concurrently signal the same process instance
4) The second node writes a record to the database
The test case needs to be executed multiple times to see the incorrect behaviour.
This is an example of run output
Isol 8
Action 1
Action 2
Action 2
Action 2
Action 2
Action 2 1
Action 2 1
Action 2 1
Action 2 1
Signalist 5
Signalist 6
Signalist 8
Signalist 12
Signalist 7
Signalist 13
Signalist 14
Signalist 15
Signalist 9
Signalist 16
Signalist 17
Signalist 18
Signalist 4
Success 7
Failure 13
Explanation of the outcome
4 threads successfully executed the node action including database operation. All database
opeartion were comitted (4 new records were created)
3 threads successfully executed the signal operation but no real action was performed
13 threads attempted to execute the signal operation but ended with an exception
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:07 a.m.
New subject: [JBoss JIRA] Updated: (JBPM-1071) Possible problem in concurrent signalling from multiple threads
[ http://jira.jboss.com/jira/browse/JBPM-1071?page=all ]
Jiri Pechanec updated JBPM-1071:
--------------------------------
Attachment: expl.tar.gz
Possible problem in concurrent signalling from multiple threads
---------------------------------------------------------------
Key: JBPM-1071
URL: http://jira.jboss.com/jira/browse/JBPM-1071
Project: JBoss jBPM
Issue Type: Bug
Components: Core Engine
Affects Versions: jBPM jPDL 3.2.2
Environment: Linux 2.6.21-1.3228.fc7 #1 SMP Tue Jun 12 14:56:37 EDT 2007 x86_64
x86_64 x86_64 GNU/Linux
MySQL 5.0.22
Reporter: Jiri Pechanec
Assigned To: Tom Baeyens
Priority: Critical
Attachments: expl.tar.gz
Attached is a simple test case that
1) Deploys process definition with two nodes
2) Starts the process instance that will go to the wait state on first node
3) Starts 20 threads that tries concurrently signal the same process instance
4) The second node writes a record to the database
The test case needs to be executed multiple times to see the incorrect behaviour.
This is an example of run output
Isol 8
Action 1
Action 2
Action 2
Action 2
Action 2
Action 2 1
Action 2 1
Action 2 1
Action 2 1
Signalist 5
Signalist 6
Signalist 8
Signalist 12
Signalist 7
Signalist 13
Signalist 14
Signalist 15
Signalist 9
Signalist 16
Signalist 17
Signalist 18
Signalist 4
Success 7
Failure 13
Explanation of the outcome
4 threads successfully executed the node action including database operation. All
database opeartion were comitted (4 new records were created)
3 threads successfully executed the signal operation but no real action was performed
13 threads attempted to execute the signal operation but ended with an exception
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:25 p.m.
New subject: [JBoss JIRA] Commented: (JBPM-1071) Possible problem in concurrent signalling from multiple threads
[ http://jira.jboss.com/jira/browse/JBPM-1071?page=comments#action_12383149 ]
Ronald van Kuijk commented on JBPM-1071:
----------------------------------------
what exceptions were thrown? and what action was not performed? There has been lots of
discussion on simultaneous access to node, actions and database. Can you please check the
JBPM-993 and JBPM-995 (and related) if that contains some more info?
Possible problem in concurrent signalling from multiple threads
---------------------------------------------------------------
Key: JBPM-1071
URL: http://jira.jboss.com/jira/browse/JBPM-1071
Project: JBoss jBPM
Issue Type: Bug
Components: Core Engine
Affects Versions: jBPM jPDL 3.2.2
Environment: Linux 2.6.21-1.3228.fc7 #1 SMP Tue Jun 12 14:56:37 EDT 2007 x86_64
x86_64 x86_64 GNU/Linux
MySQL 5.0.22
Reporter: Jiri Pechanec
Assigned To: Tom Baeyens
Priority: Critical
Attachments: expl.tar.gz
Attached is a simple test case that
1) Deploys process definition with two nodes
2) Starts the process instance that will go to the wait state on first node
3) Starts 20 threads that tries concurrently signal the same process instance
4) The second node writes a record to the database
The test case needs to be executed multiple times to see the incorrect behaviour.
This is an example of run output
Isol 8
Action 1
Action 2
Action 2
Action 2
Action 2
Action 2 1
Action 2 1
Action 2 1
Action 2 1
Signalist 5
Signalist 6
Signalist 8
Signalist 12
Signalist 7
Signalist 13
Signalist 14
Signalist 15
Signalist 9
Signalist 16
Signalist 17
Signalist 18
Signalist 4
Success 7
Failure 13
Explanation of the outcome
4 threads successfully executed the node action including database operation. All
database opeartion were comitted (4 new records were created)
3 threads successfully executed the signal operation but no real action was performed
13 threads attempted to execute the signal operation but ended with an exception
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:21 a.m.
New subject: [JBoss JIRA] Commented: (JBPM-1071) Possible problem in concurrent signalling from multiple threads
[ http://jira.jboss.com/jira/browse/JBPM-1071?page=comments#action_12383167 ]
Jiri Pechanec commented on JBPM-1071:
-------------------------------------
Hi,
the exception throws is
org.jbpm.JbpmException: couldn't execute org.jbpm.command.SignalCommand@715c2843
at org.jbpm.command.impl.CommandServiceImpl.execute(CommandServiceImpl.java:73)
at org.jpbm.exploratory.Signalist.run(Signalist.java:30)
Caused by: org.jbpm.JbpmException: couldn't signal token 'Token(/)' : node
'EndState(end-state1)' doesn't have a default transition
at org.jbpm.graph.exe.Token.signal(Token.java:138)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
org.hibernate.proxy.pojo.cglib.CGLIBLazyInitializer.invoke(CGLIBLazyInitializer.java:157)
at org.jbpm.graph.exe.Token$$EnhancerByCGLIB$$9af9b4e6.signal(<generated>)
at org.jbpm.command.SignalCommand.execute(SignalCommand.java:91)
at org.jbpm.command.impl.CommandServiceImpl.execute(CommandServiceImpl.java:71)
... 1 more
Which means that other threads are isgnalling process when it is in the end state.
But this is not a problem I am trying to point out.
The problem is that the same node is executed 4 times from different threads and all
changes made are successfully comitted.
IMHO the correct semantics is that only one thread executes each action (each node). The
rest of threads will either throw something like concurrent access exception or will be
used to signal in the next wait states.
According to content of the exception I can pretty accurately suppose that
4 threads executed Action 2, commited
3 threads executed transition to end state, probably committed
13 threads failed as there is no next transition
What I suppose is to have
1 thread executed Action 2, commited
3 thread executed Action 2, fail and rollback
1 thread executed transition to end state, committed
2 threads executed transition to end state, fail and rollback
13 threads failed as there is no next transition
or
1 thread executed Action 2, commited
1 thread executed transition to end state, committed
18 threads failed as there is no next transition
Possible problem in concurrent signalling from multiple threads
---------------------------------------------------------------
Key: JBPM-1071
URL: http://jira.jboss.com/jira/browse/JBPM-1071
Project: JBoss jBPM
Issue Type: Bug
Components: Core Engine
Affects Versions: jBPM jPDL 3.2.2
Environment: Linux 2.6.21-1.3228.fc7 #1 SMP Tue Jun 12 14:56:37 EDT 2007 x86_64
x86_64 x86_64 GNU/Linux
MySQL 5.0.22
Reporter: Jiri Pechanec
Assigned To: Tom Baeyens
Priority: Critical
Attachments: expl.tar.gz
Attached is a simple test case that
1) Deploys process definition with two nodes
2) Starts the process instance that will go to the wait state on first node
3) Starts 20 threads that tries concurrently signal the same process instance
4) The second node writes a record to the database
The test case needs to be executed multiple times to see the incorrect behaviour.
This is an example of run output
Isol 8
Action 1
Action 2
Action 2
Action 2
Action 2
Action 2 1
Action 2 1
Action 2 1
Action 2 1
Signalist 5
Signalist 6
Signalist 8
Signalist 12
Signalist 7
Signalist 13
Signalist 14
Signalist 15
Signalist 9
Signalist 16
Signalist 17
Signalist 18
Signalist 4
Success 7
Failure 13
Explanation of the outcome
4 threads successfully executed the node action including database operation. All
database opeartion were comitted (4 new records were created)
3 threads successfully executed the signal operation but no real action was performed
13 threads attempted to execute the signal operation but ended with an exception
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:10 a.m.
New subject: [JBoss JIRA] Updated: (JBPM-1071) Possible problem in concurrent signalling from multiple threads
[ http://jira.jboss.com/jira/browse/JBPM-1071?page=all ]
Tom Baeyens updated JBPM-1071:
------------------------------
Attachment: LockingTest.java
I attached a test LockingTest. This test does basically the same as your test, but it
fits in our overall test suite.
This test runs fine. So I can't reproduce the problem.
The way that I check the optimistic locking is a bit different. First, I spawn of x
number of competing threads/transactions. In each transaction, a comment is added that
includes the name of the thread.
Later on, we check if exactly 1 thread managed to commit, while the other were rolled
back.
What I think that you do different is that you don't use transactional resource to
measure which transactions committed and which transactions rolled back. A limitation of
the current implementation is that you can't see if an optimistic failure rollback
occured or not.
Possible problem in concurrent signalling from multiple threads
---------------------------------------------------------------
Key: JBPM-1071
URL: http://jira.jboss.com/jira/browse/JBPM-1071
Project: JBoss jBPM
Issue Type: Bug
Components: Core Engine
Affects Versions: jBPM jPDL 3.2.2
Environment: Linux 2.6.21-1.3228.fc7 #1 SMP Tue Jun 12 14:56:37 EDT 2007 x86_64
x86_64 x86_64 GNU/Linux
MySQL 5.0.22
Reporter: Jiri Pechanec
Assigned To: Tom Baeyens
Priority: Critical
Attachments: expl.tar.gz, LockingTest.java
Attached is a simple test case that
1) Deploys process definition with two nodes
2) Starts the process instance that will go to the wait state on first node
3) Starts 20 threads that tries concurrently signal the same process instance
4) The second node writes a record to the database
The test case needs to be executed multiple times to see the incorrect behaviour.
This is an example of run output
Isol 8
Action 1
Action 2
Action 2
Action 2
Action 2
Action 2 1
Action 2 1
Action 2 1
Action 2 1
Signalist 5
Signalist 6
Signalist 8
Signalist 12
Signalist 7
Signalist 13
Signalist 14
Signalist 15
Signalist 9
Signalist 16
Signalist 17
Signalist 18
Signalist 4
Success 7
Failure 13
Explanation of the outcome
4 threads successfully executed the node action including database operation. All
database opeartion were comitted (4 new records were created)
3 threads successfully executed the signal operation but no real action was performed
13 threads attempted to execute the signal operation but ended with an exception
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:37 a.m.
New subject: [JBoss JIRA] Commented: (JBPM-1071) Possible problem in concurrent signalling from multiple threads
[ http://jira.jboss.com/jira/browse/JBPM-1071?page=comments#action_12383206 ]
Jiri Pechanec commented on JBPM-1071:
-------------------------------------
I will look at the code. But what pleas pay attantion to the fact that in my test I am
also accessing to the database and all changes done in successful threads are committed.
Possible problem in concurrent signalling from multiple threads
---------------------------------------------------------------
Key: JBPM-1071
URL: http://jira.jboss.com/jira/browse/JBPM-1071
Project: JBoss jBPM
Issue Type: Bug
Components: Core Engine
Affects Versions: jBPM jPDL 3.2.2
Environment: Linux 2.6.21-1.3228.fc7 #1 SMP Tue Jun 12 14:56:37 EDT 2007 x86_64
x86_64 x86_64 GNU/Linux
MySQL 5.0.22
Reporter: Jiri Pechanec
Assigned To: Tom Baeyens
Priority: Critical
Attachments: expl.tar.gz, LockingTest.java
Attached is a simple test case that
1) Deploys process definition with two nodes
2) Starts the process instance that will go to the wait state on first node
3) Starts 20 threads that tries concurrently signal the same process instance
4) The second node writes a record to the database
The test case needs to be executed multiple times to see the incorrect behaviour.
This is an example of run output
Isol 8
Action 1
Action 2
Action 2
Action 2
Action 2
Action 2 1
Action 2 1
Action 2 1
Action 2 1
Signalist 5
Signalist 6
Signalist 8
Signalist 12
Signalist 7
Signalist 13
Signalist 14
Signalist 15
Signalist 9
Signalist 16
Signalist 17
Signalist 18
Signalist 4
Success 7
Failure 13
Explanation of the outcome
4 threads successfully executed the node action including database operation. All
database opeartion were comitted (4 new records were created)
3 threads successfully executed the signal operation but no real action was performed
13 threads attempted to execute the signal operation but ended with an exception
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:46 a.m.
New subject: [JBoss JIRA] Commented: (JBPM-1071) Possible problem in concurrent signalling from multiple threads
[ http://jira.jboss.com/jira/browse/JBPM-1071?page=comments#action_12383207 ]
Jiri Pechanec commented on JBPM-1071:
-------------------------------------
I have run your test in my environment and this is the result (I have run it not as junit
test but as a standalone application)
More updates [org.jbpm.graph.exe.Comment@3be0e954, org.jbpm.graph.exe.Comment@2af6a882]
So in that assertEquals there are two results, not just one.
Sometimes there is only one, sometimes there are three
Possible problem in concurrent signalling from multiple threads
---------------------------------------------------------------
Key: JBPM-1071
URL: http://jira.jboss.com/jira/browse/JBPM-1071
Project: JBoss jBPM
Issue Type: Bug
Components: Core Engine
Affects Versions: jBPM jPDL 3.2.2
Environment: Linux 2.6.21-1.3228.fc7 #1 SMP Tue Jun 12 14:56:37 EDT 2007 x86_64
x86_64 x86_64 GNU/Linux
MySQL 5.0.22
Reporter: Jiri Pechanec
Assigned To: Tom Baeyens
Priority: Critical
Attachments: expl.tar.gz, LockingTest.java
Attached is a simple test case that
1) Deploys process definition with two nodes
2) Starts the process instance that will go to the wait state on first node
3) Starts 20 threads that tries concurrently signal the same process instance
4) The second node writes a record to the database
The test case needs to be executed multiple times to see the incorrect behaviour.
This is an example of run output
Isol 8
Action 1
Action 2
Action 2
Action 2
Action 2
Action 2 1
Action 2 1
Action 2 1
Action 2 1
Signalist 5
Signalist 6
Signalist 8
Signalist 12
Signalist 7
Signalist 13
Signalist 14
Signalist 15
Signalist 9
Signalist 16
Signalist 17
Signalist 18
Signalist 4
Success 7
Failure 13
Explanation of the outcome
4 threads successfully executed the node action including database operation. All
database opeartion were comitted (4 new records were created)
3 threads successfully executed the signal operation but no real action was performed
13 threads attempted to execute the signal operation but ended with an exception
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:10 a.m.
New subject: [JBoss JIRA] Commented: (JBPM-1071) Possible problem in concurrent signalling from multiple threads
[ http://jira.jboss.com/jira/browse/JBPM-1071?page=comments#action_12387001 ]
Jiri Pechanec commented on JBPM-1071:
-------------------------------------
The Locking test is failing with this message
junit.framework.AssertionFailedError: [comment(Thread-5 committed), comment(Thread-1
committed), comment(Thread-3 committed), comment(Thread-2 committed
), comment(Thread-4 committed)] expected:<1> but was:<5> at
org.jbpm.optimisticlocking.LockingTest.testLocking(LockingTest.java:81)
Possible problem in concurrent signalling from multiple threads
---------------------------------------------------------------
Key: JBPM-1071
URL: http://jira.jboss.com/jira/browse/JBPM-1071
Project: JBoss jBPM
Issue Type: Bug
Components: Core Engine
Affects Versions: jBPM jPDL 3.2.2
Environment: Linux 2.6.21-1.3228.fc7 #1 SMP Tue Jun 12 14:56:37 EDT 2007 x86_64
x86_64 x86_64 GNU/Linux
MySQL 5.0.22
Reporter: Jiri Pechanec
Assigned To: Tom Baeyens
Priority: Critical
Attachments: expl.tar.gz, LockingTest.java
Attached is a simple test case that
1) Deploys process definition with two nodes
2) Starts the process instance that will go to the wait state on first node
3) Starts 20 threads that tries concurrently signal the same process instance
4) The second node writes a record to the database
The test case needs to be executed multiple times to see the incorrect behaviour.
This is an example of run output
Isol 8
Action 1
Action 2
Action 2
Action 2
Action 2
Action 2 1
Action 2 1
Action 2 1
Action 2 1
Signalist 5
Signalist 6
Signalist 8
Signalist 12
Signalist 7
Signalist 13
Signalist 14
Signalist 15
Signalist 9
Signalist 16
Signalist 17
Signalist 18
Signalist 4
Success 7
Failure 13
Explanation of the outcome
4 threads successfully executed the node action including database operation. All
database opeartion were comitted (4 new records were created)
3 threads successfully executed the signal operation but no real action was performed
13 threads attempted to execute the signal operation but ended with an exception
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:28 a.m.
New subject: [JBoss JIRA] Commented: (JBPM-1071) Possible problem in concurrent signalling from multiple threads
[ http://jira.jboss.com/jira/browse/JBPM-1071?page=comments#action_12387069 ]
Len DiMaggio commented on JBPM-1071:
------------------------------------
This is hibernate setup
<property
name="hibernate.dialect">org.hibernate.dialect.MySQLDialect</property>
<property
name="hibernate.connection.driver_class">com.mysql.jdbc.Driver</property>
<property
name="hibernate.connection.url">jdbc:mysql://localhost:3306/soaesb1</property>
<property
name="hibernate.connection.username">soaesb1</property>
<property
name="hibernate.connection.password">soaesb1</property>
<property name="hibernate.hbm2ddl.auto">create</property>
<property
name="hibernate.connection.isolation">8</property>
<property name="connection.pool_size">10</property>
Possible problem in concurrent signalling from multiple threads
---------------------------------------------------------------
Key: JBPM-1071
URL: http://jira.jboss.com/jira/browse/JBPM-1071
Project: JBoss jBPM
Issue Type: Bug
Components: Core Engine
Affects Versions: jBPM jPDL 3.2.2
Environment: Linux 2.6.21-1.3228.fc7 #1 SMP Tue Jun 12 14:56:37 EDT 2007 x86_64
x86_64 x86_64 GNU/Linux
MySQL 5.0.22
Reporter: Jiri Pechanec
Assigned To: Tom Baeyens
Priority: Critical
Attachments: expl.tar.gz, LockingTest.java
Attached is a simple test case that
1) Deploys process definition with two nodes
2) Starts the process instance that will go to the wait state on first node
3) Starts 20 threads that tries concurrently signal the same process instance
4) The second node writes a record to the database
The test case needs to be executed multiple times to see the incorrect behaviour.
This is an example of run output
Isol 8
Action 1
Action 2
Action 2
Action 2
Action 2
Action 2 1
Action 2 1
Action 2 1
Action 2 1
Signalist 5
Signalist 6
Signalist 8
Signalist 12
Signalist 7
Signalist 13
Signalist 14
Signalist 15
Signalist 9
Signalist 16
Signalist 17
Signalist 18
Signalist 4
Success 7
Failure 13
Explanation of the outcome
4 threads successfully executed the node action including database operation. All
database opeartion were comitted (4 new records were created)
3 threads successfully executed the signal operation but no real action was performed
13 threads attempted to execute the signal operation but ended with an exception
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:07 a.m.
New subject: [JBoss JIRA] Commented: (JBPM-1071) Possible problem in concurrent signalling from multiple threads
[ http://jira.jboss.com/jira/browse/JBPM-1071?page=comments#action_12387103 ]
Tom Baeyens commented on JBPM-1071:
-----------------------------------
just installed MySQL on my windows box and configured the test suite to go to MySQL.
Verified it in the logs that the set up was ok.
The lost Locking test still succeeds. Tried with the defaults and with
<property name="hibernate.connection.isolation">8</property>
<property name="connection.pool_size">10</property>
Any suggestions ?
Possible problem in concurrent signalling from multiple threads
---------------------------------------------------------------
Key: JBPM-1071
URL: http://jira.jboss.com/jira/browse/JBPM-1071
Project: JBoss jBPM
Issue Type: Bug
Components: Core Engine
Affects Versions: jBPM jPDL 3.2.2
Environment: Linux 2.6.21-1.3228.fc7 #1 SMP Tue Jun 12 14:56:37 EDT 2007 x86_64
x86_64 x86_64 GNU/Linux
MySQL 5.0.22
Reporter: Jiri Pechanec
Assigned To: Tom Baeyens
Priority: Critical
Attachments: expl.tar.gz, LockingTest.java
Attached is a simple test case that
1) Deploys process definition with two nodes
2) Starts the process instance that will go to the wait state on first node
3) Starts 20 threads that tries concurrently signal the same process instance
4) The second node writes a record to the database
The test case needs to be executed multiple times to see the incorrect behaviour.
This is an example of run output
Isol 8
Action 1
Action 2
Action 2
Action 2
Action 2
Action 2 1
Action 2 1
Action 2 1
Action 2 1
Signalist 5
Signalist 6
Signalist 8
Signalist 12
Signalist 7
Signalist 13
Signalist 14
Signalist 15
Signalist 9
Signalist 16
Signalist 17
Signalist 18
Signalist 4
Success 7
Failure 13
Explanation of the outcome
4 threads successfully executed the node action including database operation. All
database opeartion were comitted (4 new records were created)
3 threads successfully executed the signal operation but no real action was performed
13 threads attempted to execute the signal operation but ended with an exception
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:11 p.m.
New subject: [JBoss JIRA] Commented: (JBPM-1071) Possible problem in concurrent signalling from multiple threads
[ http://jira.jboss.com/jira/browse/JBPM-1071?page=comments#action_12387152 ]
Jiri Pechanec commented on JBPM-1071:
-------------------------------------
How did you configure to use MySQL?
Possible problem in concurrent signalling from multiple threads
---------------------------------------------------------------
Key: JBPM-1071
URL: http://jira.jboss.com/jira/browse/JBPM-1071
Project: JBoss jBPM
Issue Type: Bug
Components: Core Engine
Affects Versions: jBPM jPDL 3.2.2
Environment: Linux 2.6.21-1.3228.fc7 #1 SMP Tue Jun 12 14:56:37 EDT 2007 x86_64
x86_64 x86_64 GNU/Linux
MySQL 5.0.22
Reporter: Jiri Pechanec
Assigned To: Tom Baeyens
Priority: Critical
Attachments: expl.tar.gz, LockingTest.java
Attached is a simple test case that
1) Deploys process definition with two nodes
2) Starts the process instance that will go to the wait state on first node
3) Starts 20 threads that tries concurrently signal the same process instance
4) The second node writes a record to the database
The test case needs to be executed multiple times to see the incorrect behaviour.
This is an example of run output
Isol 8
Action 1
Action 2
Action 2
Action 2
Action 2
Action 2 1
Action 2 1
Action 2 1
Action 2 1
Signalist 5
Signalist 6
Signalist 8
Signalist 12
Signalist 7
Signalist 13
Signalist 14
Signalist 15
Signalist 9
Signalist 16
Signalist 17
Signalist 18
Signalist 4
Success 7
Failure 13
Explanation of the outcome
4 threads successfully executed the node action including database operation. All
database opeartion were comitted (4 new records were created)
3 threads successfully executed the signal operation but no real action was performed
13 threads attempted to execute the signal operation but ended with an exception
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:38 a.m.
New subject: [JBoss JIRA] Commented: (JBPM-1071) Possible problem in concurrent signalling from multiple threads
[ http://jira.jboss.com/jira/browse/JBPM-1071?page=comments#action_12387330 ]
Ronald van Kuijk commented on JBPM-1071:
----------------------------------------
could it be that it is related to the speed of a system?
Possible problem in concurrent signalling from multiple threads
---------------------------------------------------------------
Key: JBPM-1071
URL: http://jira.jboss.com/jira/browse/JBPM-1071
Project: JBoss jBPM
Issue Type: Bug
Components: Core Engine
Affects Versions: jBPM jPDL 3.2.2
Environment: Linux 2.6.21-1.3228.fc7 #1 SMP Tue Jun 12 14:56:37 EDT 2007 x86_64
x86_64 x86_64 GNU/Linux
MySQL 5.0.22
Reporter: Jiri Pechanec
Assigned To: Tom Baeyens
Priority: Critical
Attachments: expl.tar.gz, LockingTest.java
Attached is a simple test case that
1) Deploys process definition with two nodes
2) Starts the process instance that will go to the wait state on first node
3) Starts 20 threads that tries concurrently signal the same process instance
4) The second node writes a record to the database
The test case needs to be executed multiple times to see the incorrect behaviour.
This is an example of run output
Isol 8
Action 1
Action 2
Action 2
Action 2
Action 2
Action 2 1
Action 2 1
Action 2 1
Action 2 1
Signalist 5
Signalist 6
Signalist 8
Signalist 12
Signalist 7
Signalist 13
Signalist 14
Signalist 15
Signalist 9
Signalist 16
Signalist 17
Signalist 18
Signalist 4
Success 7
Failure 13
Explanation of the outcome
4 threads successfully executed the node action including database operation. All
database opeartion were comitted (4 new records were created)
3 threads successfully executed the signal operation but no real action was performed
13 threads attempted to execute the signal operation but ended with an exception
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:06 a.m.
New subject: [JBoss JIRA] Commented: (JBPM-1071) Possible problem in concurrent signalling from multiple threads
[ http://jira.jboss.com/jira/browse/JBPM-1071?page=comments#action_12387441 ]
Tom Baeyens commented on JBPM-1071:
-----------------------------------
"
How did you configure to use MySQL?
"
default windows installation on a xeon 3.6 GHz single core workstation
Possible problem in concurrent signalling from multiple threads
---------------------------------------------------------------
Key: JBPM-1071
URL: http://jira.jboss.com/jira/browse/JBPM-1071
Project: JBoss jBPM
Issue Type: Bug
Components: Core Engine
Affects Versions: jBPM jPDL 3.2.2
Environment: Linux 2.6.21-1.3228.fc7 #1 SMP Tue Jun 12 14:56:37 EDT 2007 x86_64
x86_64 x86_64 GNU/Linux
MySQL 5.0.22
Reporter: Jiri Pechanec
Assigned To: Tom Baeyens
Priority: Critical
Attachments: expl.tar.gz, LockingTest.java
Attached is a simple test case that
1) Deploys process definition with two nodes
2) Starts the process instance that will go to the wait state on first node
3) Starts 20 threads that tries concurrently signal the same process instance
4) The second node writes a record to the database
The test case needs to be executed multiple times to see the incorrect behaviour.
This is an example of run output
Isol 8
Action 1
Action 2
Action 2
Action 2
Action 2
Action 2 1
Action 2 1
Action 2 1
Action 2 1
Signalist 5
Signalist 6
Signalist 8
Signalist 12
Signalist 7
Signalist 13
Signalist 14
Signalist 15
Signalist 9
Signalist 16
Signalist 17
Signalist 18
Signalist 4
Success 7
Failure 13
Explanation of the outcome
4 threads successfully executed the node action including database operation. All
database opeartion were comitted (4 new records were created)
3 threads successfully executed the signal operation but no real action was performed
13 threads attempted to execute the signal operation but ended with an exception
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:26 a.m.
New subject: [JBoss JIRA] Commented: (JBPM-1071) Possible problem in concurrent signalling from multiple threads
[ http://jira.jboss.com/jira/browse/JBPM-1071?page=comments#action_12387468 ]
Jiri Pechanec commented on JBPM-1071:
-------------------------------------
Sorry, that is misunderstanding. Can you describe the process how did you enable the
support for MySQL?
Possible problem in concurrent signalling from multiple threads
---------------------------------------------------------------
Key: JBPM-1071
URL: http://jira.jboss.com/jira/browse/JBPM-1071
Project: JBoss jBPM
Issue Type: Bug
Components: Core Engine
Affects Versions: jBPM jPDL 3.2.2
Environment: Linux 2.6.21-1.3228.fc7 #1 SMP Tue Jun 12 14:56:37 EDT 2007 x86_64
x86_64 x86_64 GNU/Linux
MySQL 5.0.22
Reporter: Jiri Pechanec
Assigned To: Tom Baeyens
Priority: Critical
Attachments: expl.tar.gz, LockingTest.java
Attached is a simple test case that
1) Deploys process definition with two nodes
2) Starts the process instance that will go to the wait state on first node
3) Starts 20 threads that tries concurrently signal the same process instance
4) The second node writes a record to the database
The test case needs to be executed multiple times to see the incorrect behaviour.
This is an example of run output
Isol 8
Action 1
Action 2
Action 2
Action 2
Action 2
Action 2 1
Action 2 1
Action 2 1
Action 2 1
Signalist 5
Signalist 6
Signalist 8
Signalist 12
Signalist 7
Signalist 13
Signalist 14
Signalist 15
Signalist 9
Signalist 16
Signalist 17
Signalist 18
Signalist 4
Success 7
Failure 13
Explanation of the outcome
4 threads successfully executed the node action including database operation. All
database opeartion were comitted (4 new records were created)
3 threads successfully executed the signal operation but no real action was performed
13 threads attempted to execute the signal operation but ended with an exception
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:55 a.m.
New subject: [JBoss JIRA] Commented: (JBPM-1071) Possible problem in concurrent signalling from multiple threads
[ http://jira.jboss.com/jira/browse/JBPM-1071?page=comments#action_12387669 ]
Tom Baeyens commented on JBPM-1071:
-----------------------------------
by using hibernate ?!
somehow i have a feeling that is not the answer you're looking for. in that case,
please rephrase.
Possible problem in concurrent signalling from multiple threads
---------------------------------------------------------------
Key: JBPM-1071
URL: http://jira.jboss.com/jira/browse/JBPM-1071
Project: JBoss jBPM
Issue Type: Bug
Components: Core Engine
Affects Versions: jBPM jPDL 3.2.2
Environment: Linux 2.6.21-1.3228.fc7 #1 SMP Tue Jun 12 14:56:37 EDT 2007 x86_64
x86_64 x86_64 GNU/Linux
MySQL 5.0.22
Reporter: Jiri Pechanec
Assigned To: Tom Baeyens
Priority: Critical
Attachments: expl.tar.gz, LockingTest.java
Attached is a simple test case that
1) Deploys process definition with two nodes
2) Starts the process instance that will go to the wait state on first node
3) Starts 20 threads that tries concurrently signal the same process instance
4) The second node writes a record to the database
The test case needs to be executed multiple times to see the incorrect behaviour.
This is an example of run output
Isol 8
Action 1
Action 2
Action 2
Action 2
Action 2
Action 2 1
Action 2 1
Action 2 1
Action 2 1
Signalist 5
Signalist 6
Signalist 8
Signalist 12
Signalist 7
Signalist 13
Signalist 14
Signalist 15
Signalist 9
Signalist 16
Signalist 17
Signalist 18
Signalist 4
Success 7
Failure 13
Explanation of the outcome
4 threads successfully executed the node action including database operation. All
database opeartion were comitted (4 new records were created)
3 threads successfully executed the signal operation but no real action was performed
13 threads attempted to execute the signal operation but ended with an exception
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:59 a.m.
New subject: [JBoss JIRA] Commented: (JBPM-1071) Possible problem in concurrent signalling from multiple threads
[ http://jira.jboss.com/jira/browse/JBPM-1071?page=comments#action_12387671 ]
Jiri Pechanec commented on JBPM-1071:
-------------------------------------
Did you use hibernate.properties or direct modification of hibernate.cfg.xml?
Possible problem in concurrent signalling from multiple threads
---------------------------------------------------------------
Key: JBPM-1071
URL: http://jira.jboss.com/jira/browse/JBPM-1071
Project: JBoss jBPM
Issue Type: Bug
Components: Core Engine
Affects Versions: jBPM jPDL 3.2.2
Environment: Linux 2.6.21-1.3228.fc7 #1 SMP Tue Jun 12 14:56:37 EDT 2007 x86_64
x86_64 x86_64 GNU/Linux
MySQL 5.0.22
Reporter: Jiri Pechanec
Assigned To: Tom Baeyens
Priority: Critical
Attachments: expl.tar.gz, LockingTest.java
Attached is a simple test case that
1) Deploys process definition with two nodes
2) Starts the process instance that will go to the wait state on first node
3) Starts 20 threads that tries concurrently signal the same process instance
4) The second node writes a record to the database
The test case needs to be executed multiple times to see the incorrect behaviour.
This is an example of run output
Isol 8
Action 1
Action 2
Action 2
Action 2
Action 2
Action 2 1
Action 2 1
Action 2 1
Action 2 1
Signalist 5
Signalist 6
Signalist 8
Signalist 12
Signalist 7
Signalist 13
Signalist 14
Signalist 15
Signalist 9
Signalist 16
Signalist 17
Signalist 18
Signalist 4
Success 7
Failure 13
Explanation of the outcome
4 threads successfully executed the node action including database operation. All
database opeartion were comitted (4 new records were created)
3 threads successfully executed the signal operation but no real action was performed
13 threads attempted to execute the signal operation but ended with an exception
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:23 a.m.
New subject: [JBoss JIRA] Commented: (JBPM-1071) Possible problem in concurrent signalling from multiple threads
[ http://jira.jboss.com/jira/browse/JBPM-1071?page=comments#action_12388415 ]
Tom Baeyens commented on JBPM-1071:
-----------------------------------
direct modification of hibernate.cfg.xml
which of the two you use doesn't matter. but verify that your configurations are
actually picked up by the test run in the logs (thats what i did)
Possible problem in concurrent signalling from multiple threads
---------------------------------------------------------------
Key: JBPM-1071
URL: http://jira.jboss.com/jira/browse/JBPM-1071
Project: JBoss jBPM
Issue Type: Bug
Components: Core Engine
Affects Versions: jBPM jPDL 3.2.2
Environment: Linux 2.6.21-1.3228.fc7 #1 SMP Tue Jun 12 14:56:37 EDT 2007 x86_64
x86_64 x86_64 GNU/Linux
MySQL 5.0.22
Reporter: Jiri Pechanec
Assigned To: Tom Baeyens
Priority: Critical
Attachments: expl.tar.gz, LockingTest.java
Attached is a simple test case that
1) Deploys process definition with two nodes
2) Starts the process instance that will go to the wait state on first node
3) Starts 20 threads that tries concurrently signal the same process instance
4) The second node writes a record to the database
The test case needs to be executed multiple times to see the incorrect behaviour.
This is an example of run output
Isol 8
Action 1
Action 2
Action 2
Action 2
Action 2
Action 2 1
Action 2 1
Action 2 1
Action 2 1
Signalist 5
Signalist 6
Signalist 8
Signalist 12
Signalist 7
Signalist 13
Signalist 14
Signalist 15
Signalist 9
Signalist 16
Signalist 17
Signalist 18
Signalist 4
Success 7
Failure 13
Explanation of the outcome
4 threads successfully executed the node action including database operation. All
database opeartion were comitted (4 new records were created)
3 threads successfully executed the signal operation but no real action was performed
13 threads attempted to execute the signal operation but ended with an exception
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:12 p.m.
New subject: [JBoss JIRA] Commented: (JBPM-1071) Possible problem in concurrent signalling from multiple threads
[ http://jira.jboss.com/jira/browse/JBPM-1071?page=comments#action_12388692 ]
Koen Aers commented on JBPM-1071:
---------------------------------
I have been able to reproduce the issue for MySQL (not for HSQLDB) on my T60 Dual Core. So
it looks like it only happens in the case of 'true' concurrency on a multi
processor system as Len pointed out. I'll investigate some more to track down the
possible causes and/or fixes
Possible problem in concurrent signalling from multiple threads
---------------------------------------------------------------
Key: JBPM-1071
URL: http://jira.jboss.com/jira/browse/JBPM-1071
Project: JBoss jBPM
Issue Type: Bug
Components: Core Engine
Affects Versions: jBPM jPDL 3.2.2
Environment: Linux 2.6.21-1.3228.fc7 #1 SMP Tue Jun 12 14:56:37 EDT 2007 x86_64
x86_64 x86_64 GNU/Linux
MySQL 5.0.22
Reporter: Jiri Pechanec
Assigned To: Tom Baeyens
Priority: Critical
Attachments: expl.tar.gz, LockingTest.java
Attached is a simple test case that
1) Deploys process definition with two nodes
2) Starts the process instance that will go to the wait state on first node
3) Starts 20 threads that tries concurrently signal the same process instance
4) The second node writes a record to the database
The test case needs to be executed multiple times to see the incorrect behaviour.
This is an example of run output
Isol 8
Action 1
Action 2
Action 2
Action 2
Action 2
Action 2 1
Action 2 1
Action 2 1
Action 2 1
Signalist 5
Signalist 6
Signalist 8
Signalist 12
Signalist 7
Signalist 13
Signalist 14
Signalist 15
Signalist 9
Signalist 16
Signalist 17
Signalist 18
Signalist 4
Success 7
Failure 13
Explanation of the outcome
4 threads successfully executed the node action including database operation. All
database opeartion were comitted (4 new records were created)
3 threads successfully executed the signal operation but no real action was performed
13 threads attempted to execute the signal operation but ended with an exception
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:13 p.m.
New subject: [JBoss JIRA] Commented: (JBPM-1071) Possible problem in concurrent signalling from multiple threads
[ http://jira.jboss.com/jira/browse/JBPM-1071?page=comments#action_12388703 ]
Ronald van Kuijk commented on JBPM-1071:
----------------------------------------
I cannot reproduce on my single core 1THz, 512TB (RAM), 1GB (HD), but I'll try to
reproduce on a less powerful Dual Core tomorrow.
Possible problem in concurrent signalling from multiple threads
---------------------------------------------------------------
Key: JBPM-1071
URL: http://jira.jboss.com/jira/browse/JBPM-1071
Project: JBoss jBPM
Issue Type: Bug
Components: Core Engine
Affects Versions: jBPM jPDL 3.2.2
Environment: Linux 2.6.21-1.3228.fc7 #1 SMP Tue Jun 12 14:56:37 EDT 2007 x86_64
x86_64 x86_64 GNU/Linux
MySQL 5.0.22
Reporter: Jiri Pechanec
Assigned To: Tom Baeyens
Priority: Critical
Attachments: expl.tar.gz, LockingTest.java
Attached is a simple test case that
1) Deploys process definition with two nodes
2) Starts the process instance that will go to the wait state on first node
3) Starts 20 threads that tries concurrently signal the same process instance
4) The second node writes a record to the database
The test case needs to be executed multiple times to see the incorrect behaviour.
This is an example of run output
Isol 8
Action 1
Action 2
Action 2
Action 2
Action 2
Action 2 1
Action 2 1
Action 2 1
Action 2 1
Signalist 5
Signalist 6
Signalist 8
Signalist 12
Signalist 7
Signalist 13
Signalist 14
Signalist 15
Signalist 9
Signalist 16
Signalist 17
Signalist 18
Signalist 4
Success 7
Failure 13
Explanation of the outcome
4 threads successfully executed the node action including database operation. All
database opeartion were comitted (4 new records were created)
3 threads successfully executed the signal operation but no real action was performed
13 threads attempted to execute the signal operation but ended with an exception
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:29 p.m.
New subject: [JBoss JIRA] Updated: (JBPM-1071) Possible problem in concurrent signalling from multiple threads
[ http://jira.jboss.com/jira/browse/JBPM-1071?page=all ]
Koen Aers updated JBPM-1071:
----------------------------
Attachment: log.txt
This is the logfile the test produces. It looks like the version clashes are properly
detected, but the database is updated nonetheless...
Possible problem in concurrent signalling from multiple threads
---------------------------------------------------------------
Key: JBPM-1071
URL: http://jira.jboss.com/jira/browse/JBPM-1071
Project: JBoss jBPM
Issue Type: Bug
Components: Core Engine
Affects Versions: jBPM jPDL 3.2.2
Environment: Linux 2.6.21-1.3228.fc7 #1 SMP Tue Jun 12 14:56:37 EDT 2007 x86_64
x86_64 x86_64 GNU/Linux
MySQL 5.0.22
Reporter: Jiri Pechanec
Assigned To: Tom Baeyens
Priority: Critical
Attachments: expl.tar.gz, LockingTest.java, log.txt
Attached is a simple test case that
1) Deploys process definition with two nodes
2) Starts the process instance that will go to the wait state on first node
3) Starts 20 threads that tries concurrently signal the same process instance
4) The second node writes a record to the database
The test case needs to be executed multiple times to see the incorrect behaviour.
This is an example of run output
Isol 8
Action 1
Action 2
Action 2
Action 2
Action 2
Action 2 1
Action 2 1
Action 2 1
Action 2 1
Signalist 5
Signalist 6
Signalist 8
Signalist 12
Signalist 7
Signalist 13
Signalist 14
Signalist 15
Signalist 9
Signalist 16
Signalist 17
Signalist 18
Signalist 4
Success 7
Failure 13
Explanation of the outcome
4 threads successfully executed the node action including database operation. All
database opeartion were comitted (4 new records were created)
3 threads successfully executed the signal operation but no real action was performed
13 threads attempted to execute the signal operation but ended with an exception
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:44 p.m.
New subject: [JBoss JIRA] Commented: (JBPM-1071) Possible problem in concurrent signalling from multiple threads
[ http://jira.jboss.com/jira/browse/JBPM-1071?page=comments#action_12388707 ]
Koen Aers commented on JBPM-1071:
---------------------------------
Putting a breakpoint on line 256 while debugging this test reveals weird behaviour. It
turns out that right before the first commit there are no rows in the table, just like one
would expect. But after the first commit, still no rows... And only after the fifth commit
there is a change: the five rows are added as if processed in a batch. Thoughts anyone? Do
we miss a particular configuration here?
Possible problem in concurrent signalling from multiple threads
---------------------------------------------------------------
Key: JBPM-1071
URL: http://jira.jboss.com/jira/browse/JBPM-1071
Project: JBoss jBPM
Issue Type: Bug
Components: Core Engine
Affects Versions: jBPM jPDL 3.2.2
Environment: Linux 2.6.21-1.3228.fc7 #1 SMP Tue Jun 12 14:56:37 EDT 2007 x86_64
x86_64 x86_64 GNU/Linux
MySQL 5.0.22
Reporter: Jiri Pechanec
Assigned To: Tom Baeyens
Priority: Critical
Attachments: expl.tar.gz, LockingTest.java, log.txt
Attached is a simple test case that
1) Deploys process definition with two nodes
2) Starts the process instance that will go to the wait state on first node
3) Starts 20 threads that tries concurrently signal the same process instance
4) The second node writes a record to the database
The test case needs to be executed multiple times to see the incorrect behaviour.
This is an example of run output
Isol 8
Action 1
Action 2
Action 2
Action 2
Action 2
Action 2 1
Action 2 1
Action 2 1
Action 2 1
Signalist 5
Signalist 6
Signalist 8
Signalist 12
Signalist 7
Signalist 13
Signalist 14
Signalist 15
Signalist 9
Signalist 16
Signalist 17
Signalist 18
Signalist 4
Success 7
Failure 13
Explanation of the outcome
4 threads successfully executed the node action including database operation. All
database opeartion were comitted (4 new records were created)
3 threads successfully executed the signal operation but no real action was performed
13 threads attempted to execute the signal operation but ended with an exception
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:48 p.m.
New subject: [JBoss JIRA] Commented: (JBPM-1071) Possible problem in concurrent signalling from multiple threads
[ http://jira.jboss.com/jira/browse/JBPM-1071?page=comments#action_12388708 ]
Koen Aers commented on JBPM-1071:
---------------------------------
Ronald, is your dual core a windows box? It would be interesting to have the same issue on
a windows machine as well so that we know for sure it is not the OS.
Possible problem in concurrent signalling from multiple threads
---------------------------------------------------------------
Key: JBPM-1071
URL: http://jira.jboss.com/jira/browse/JBPM-1071
Project: JBoss jBPM
Issue Type: Bug
Components: Core Engine
Affects Versions: jBPM jPDL 3.2.2
Environment: Linux 2.6.21-1.3228.fc7 #1 SMP Tue Jun 12 14:56:37 EDT 2007 x86_64
x86_64 x86_64 GNU/Linux
MySQL 5.0.22
Reporter: Jiri Pechanec
Assigned To: Tom Baeyens
Priority: Critical
Attachments: expl.tar.gz, LockingTest.java, log.txt
Attached is a simple test case that
1) Deploys process definition with two nodes
2) Starts the process instance that will go to the wait state on first node
3) Starts 20 threads that tries concurrently signal the same process instance
4) The second node writes a record to the database
The test case needs to be executed multiple times to see the incorrect behaviour.
This is an example of run output
Isol 8
Action 1
Action 2
Action 2
Action 2
Action 2
Action 2 1
Action 2 1
Action 2 1
Action 2 1
Signalist 5
Signalist 6
Signalist 8
Signalist 12
Signalist 7
Signalist 13
Signalist 14
Signalist 15
Signalist 9
Signalist 16
Signalist 17
Signalist 18
Signalist 4
Success 7
Failure 13
Explanation of the outcome
4 threads successfully executed the node action including database operation. All
database opeartion were comitted (4 new records were created)
3 threads successfully executed the signal operation but no real action was performed
13 threads attempted to execute the signal operation but ended with an exception
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:26 a.m.
New subject: [JBoss JIRA] Assigned: (JBPM-1071) Possible problem in concurrent signalling from multiple threads
[ http://jira.jboss.com/jira/browse/JBPM-1071?page=all ]
Mark Little reassigned JBPM-1071:
---------------------------------
Assignee: Koen Aers (was: Tom Baeyens)
Possible problem in concurrent signalling from multiple threads
---------------------------------------------------------------
Key: JBPM-1071
URL: http://jira.jboss.com/jira/browse/JBPM-1071
Project: JBoss jBPM
Issue Type: Bug
Components: Core Engine
Affects Versions: jBPM jPDL 3.2.2
Environment: Linux 2.6.21-1.3228.fc7 #1 SMP Tue Jun 12 14:56:37 EDT 2007 x86_64
x86_64 x86_64 GNU/Linux
MySQL 5.0.22
Reporter: Jiri Pechanec
Assigned To: Koen Aers
Priority: Critical
Attachments: expl.tar.gz, LockingTest.java, log.txt
Attached is a simple test case that
1) Deploys process definition with two nodes
2) Starts the process instance that will go to the wait state on first node
3) Starts 20 threads that tries concurrently signal the same process instance
4) The second node writes a record to the database
The test case needs to be executed multiple times to see the incorrect behaviour.
This is an example of run output
Isol 8
Action 1
Action 2
Action 2
Action 2
Action 2
Action 2 1
Action 2 1
Action 2 1
Action 2 1
Signalist 5
Signalist 6
Signalist 8
Signalist 12
Signalist 7
Signalist 13
Signalist 14
Signalist 15
Signalist 9
Signalist 16
Signalist 17
Signalist 18
Signalist 4
Success 7
Failure 13
Explanation of the outcome
4 threads successfully executed the node action including database operation. All
database opeartion were comitted (4 new records were created)
3 threads successfully executed the signal operation but no real action was performed
13 threads attempted to execute the signal operation but ended with an exception
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:51 a.m.
New subject: [JBoss JIRA] Commented: (JBPM-1071) Possible problem in concurrent signalling from multiple threads
[ http://jira.jboss.com/jira/browse/JBPM-1071?page=comments#action_12389058 ]
Tom Baeyens commented on JBPM-1071:
-----------------------------------
running this test with mysql on my windows dual core gives green light.
so that leaves us with only reproducable on mysql-linux. I'll give it a shot and
we'll try to debug it. But we both don't have a clue how or where we should start
looking to find this problem.
We might start to think our options in case we won't be able to find/fix the problem.
Possible problem in concurrent signalling from multiple threads
---------------------------------------------------------------
Key: JBPM-1071
URL: http://jira.jboss.com/jira/browse/JBPM-1071
Project: JBoss jBPM
Issue Type: Bug
Components: Core Engine
Affects Versions: jBPM jPDL 3.2.2
Environment: Linux 2.6.21-1.3228.fc7 #1 SMP Tue Jun 12 14:56:37 EDT 2007 x86_64
x86_64 x86_64 GNU/Linux
MySQL 5.0.22
Reporter: Jiri Pechanec
Assigned To: Koen Aers
Priority: Critical
Attachments: expl.tar.gz, LockingTest.java, log.txt
Attached is a simple test case that
1) Deploys process definition with two nodes
2) Starts the process instance that will go to the wait state on first node
3) Starts 20 threads that tries concurrently signal the same process instance
4) The second node writes a record to the database
The test case needs to be executed multiple times to see the incorrect behaviour.
This is an example of run output
Isol 8
Action 1
Action 2
Action 2
Action 2
Action 2
Action 2 1
Action 2 1
Action 2 1
Action 2 1
Signalist 5
Signalist 6
Signalist 8
Signalist 12
Signalist 7
Signalist 13
Signalist 14
Signalist 15
Signalist 9
Signalist 16
Signalist 17
Signalist 18
Signalist 4
Success 7
Failure 13
Explanation of the outcome
4 threads successfully executed the node action including database operation. All
database opeartion were comitted (4 new records were created)
3 threads successfully executed the signal operation but no real action was performed
13 threads attempted to execute the signal operation but ended with an exception
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:27 a.m.
New subject: [JBoss JIRA] Commented: (JBPM-1071) Possible problem in concurrent signalling from multiple threads
[ http://jira.jboss.com/jira/browse/JBPM-1071?page=comments#action_12389133 ]
Ronald van Kuijk commented on JBPM-1071:
----------------------------------------
It is dual boot, but all is installed in Linux,(kernel 2.6.20), which does not run the
test correctly (same mysq as above). I do not have the time to install everything on
windows the comming days... sorry, but Tom already tried
Possible problem in concurrent signalling from multiple threads
---------------------------------------------------------------
Key: JBPM-1071
URL: http://jira.jboss.com/jira/browse/JBPM-1071
Project: JBoss jBPM
Issue Type: Bug
Components: Core Engine
Affects Versions: jBPM jPDL 3.2.2
Environment: Linux 2.6.21-1.3228.fc7 #1 SMP Tue Jun 12 14:56:37 EDT 2007 x86_64
x86_64 x86_64 GNU/Linux
MySQL 5.0.22
Reporter: Jiri Pechanec
Assigned To: Koen Aers
Priority: Critical
Attachments: expl.tar.gz, LockingTest.java, log.txt
Attached is a simple test case that
1) Deploys process definition with two nodes
2) Starts the process instance that will go to the wait state on first node
3) Starts 20 threads that tries concurrently signal the same process instance
4) The second node writes a record to the database
The test case needs to be executed multiple times to see the incorrect behaviour.
This is an example of run output
Isol 8
Action 1
Action 2
Action 2
Action 2
Action 2
Action 2 1
Action 2 1
Action 2 1
Action 2 1
Signalist 5
Signalist 6
Signalist 8
Signalist 12
Signalist 7
Signalist 13
Signalist 14
Signalist 15
Signalist 9
Signalist 16
Signalist 17
Signalist 18
Signalist 4
Success 7
Failure 13
Explanation of the outcome
4 threads successfully executed the node action including database operation. All
database opeartion were comitted (4 new records were created)
3 threads successfully executed the signal operation but no real action was performed
13 threads attempted to execute the signal operation but ended with an exception
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6748
days inactive
6788
days old
24 comments
6 participants
participants (6)
-
Jiri Pechanec (JIRA) -
Koen Aers (JIRA)
-
Len DiMaggio (JIRA)
-
Mark Little (JIRA)
-
Ronald van Kuijk (JIRA)
-
Tom Baeyens (JIRA)