Bug 780008 (SOA-2368) - JBPM2094Test and JBPM2787Test are failing on MySql 5
Summary: JBPM2094Test and JBPM2787Test are failing on MySql 5
Keywords:
Status: CLOSED NEXTRELEASE
Alias: SOA-2368
Product: JBoss Enterprise SOA Platform 5
Classification: JBoss
Component: JBPM - standalone
Version: 5.1.0.ER2
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: ---
: 5.1.0 GA
Assignee: Alejandro Guizar
QA Contact:
URL: http://jira.jboss.org/jira/browse/SOA...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-10-01 12:55 UTC by Jiri Pechanec
Modified: 2011-02-11 00:51 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-02-11 00:51:19 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 Issue Tracker SOA-2368 0 None None None Never

Description Jiri Pechanec 2010-10-01 12:55:50 UTC 
project_key: SOA

See
http://hudson.qa.jboss.com/hudson/view/SOA-Release/job/soa-jbpm-db-jdk16-maven/104/DATABASE=mysql50,jdk=java16_default,label=RHEL_any/
Comment 1 Alejandro Guizar 2010-10-01 20:03:08 UTC 
I recently lowered the job processing timeout to check the effect in the jbpm3-db job. While the latest run withstood the lower timeout [1] I figure it makes the tests more sensitive to a loaded environment. I will increase the timeout again.
Comment 2 Alejandro Guizar 2010-10-01 22:51:36 UTC 
I have increased the job processing timeout back to one minute. If the problem persists, please reopen this issue.
Comment 4 Dana Mison 2011-01-05 00:14:37 UTC 
Writer: Added: dlesage
Comment 5 Jiri Pechanec 2011-01-06 08:42:16 UTC 
Verified in ER6 - the issue is now present only sometimes so it seems that it is really related to timeout value
Comment 6 David Le Sage 2011-02-11 00:50:55 UTC 
Temporarily reopening to update release notes.
Comment 7 David Le Sage 2011-02-11 00:51:09 UTC 
Release Notes Docs Status: Added: Not Required
Note You need to log in before you can comment on or make changes to this bug.