Bug 777551 (SOA-54) - jBPM has problems with concurrent executors using database table
Summary: jBPM has problems with concurrent executors using database table
Keywords:
Status: CLOSED NEXTRELEASE
Alias: SOA-54
Product: JBoss Enterprise SOA Platform 4
Classification: JBoss
Component: JBossESB, JBPM - within SOA
Version: 4.2 IR2
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: ---
: 4.2 CR3
Assignee: Jiri Pechanec
QA Contact:
URL: http://jira.jboss.org/jira/browse/SOA-54
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2007-10-17 08:26 UTC by Jiri Pechanec
Modified: 2008-01-08 02:20 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2007-12-05 03:11:00 UTC
Type: Bug

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 777683 0 urgent CLOSED Document in Release Notes that when jBPM is used then it is not safe to use MySQL on Linux 2021-02-22 00:41:40 UTC
Red Hat Issue Tracker JBPM-1444 0 None None None Never
Red Hat Issue Tracker SOA-54 0 None None None Never

Internal Links: 777683

Description Jiri Pechanec 2007-10-17 08:26:06 UTC 
Date of First Response: 2007-11-09 06:18:07
project_key: SOA

The jBPM has problems with concurrent job executors if they are polling the same table. This situation will happen in cluster configuration with multiple jBPM engines deployed. Is it possible to use JMS queue for storing jobs instaed of database table?
Comment 1 Jiri Pechanec 2007-10-17 08:26:25 UTC 
Link: Added: This issue is related to JBPM-1072
Comment 2 Jiri Pechanec 2007-10-17 08:27:27 UTC 
Link: Added: This issue is related to JBQA-1101
Comment 3 Len DiMaggio 2007-11-01 16:40:02 UTC 
Link: Added: This issue related SOA-84
Comment 4 Mark Little 2007-11-06 14:27:23 UTC 
Link: Added: This issue is a dependency of JBESB-1301
Comment 5 Tom Baeyens 2007-11-09 11:18:07 UTC 
multiple jbpm instances connecting to the same jbpm database tables is definitely something we support.  it would be great to know what problems you're seeing.   are these reproducable ?
Comment 6 Mark Little 2007-11-20 14:22:16 UTC 
Tom to follow up with Jiri.
Comment 7 Tom Baeyens 2007-11-20 14:51:24 UTC 
see JBPM-1071
Comment 8 Mark Little 2007-11-21 12:03:39 UTC 
From Jiri:

"1) Jirka has shown the problem in live demo to Tom
2) Tom has investigated log files but did not find anything suspicious
3) Jirka and Tom agreed that both uses the similar procedure to execute the test
4) Main difference in environment is OS and dual core config
5) Tom will try to re-run test on the Linux machine himself"
Comment 9 Len DiMaggio 2007-11-28 17:45:24 UTC 
Jirka - can you confirm that this problem is/is not reproducible on Windows? The QE lab has Windows systems we can use. Thanks.
Comment 10 Jiri Pechanec 2007-11-29 09:52:19 UTC 
I was not able to reproduce the issue but I still think there is something strange in the behaviour. Let's postpone the final result when JTA will be in place.
Comment 11 Jiri Pechanec 2007-12-03 14:09:42 UTC 
Link: Added: This issue related SOA-195
Comment 12 Jiri Pechanec 2007-12-03 14:19:22 UTC 
Link: Added: This issue related SOA-196
Comment 13 Jiri Pechanec 2007-12-03 14:21:05 UTC 
Temporary solution SOA-195
Final solution SOA-196
Comment 14 Len DiMaggio 2007-12-03 16:35:40 UTC 
Current disposition for this JIRA:

* SOA-54 and SOA-55 - Mark these as 'resolved', reopen if made necessary - unlikely - by jBPM rework
 * JBPM-1072, JBPM-1072 - leave these open as they are jBPM issues
* SOA-195 - New JIRA to require SOA-P to document in Release Notes that when jBPM is used then it is not safe to use MySQL on Linux
* SOA-196 - The jBPM does not work with MySQL/Linux combo - mark as fix in 4.3
* JBPM-1095- Project bug for SOA-196
Comment 16 Len DiMaggio 2008-01-08 02:20:34 UTC 
Link: Removed: This issue related SOA-84
Note You need to log in before you can comment on or make changes to this bug.