Bug 781023 (SOA-3505) - 'AcquireInstanceLock' exception when BPEL process faces too many requests per second.
Summary: 'AcquireInstanceLock' exception when BPEL process faces too many requests per...
Keywords:
Status: CLOSED NEXTRELEASE
Alias: SOA-3505
Product: JBoss Enterprise SOA Platform 5
Classification: JBoss
Component: Documentation, riftsaw
Version: 5.2.0.ER5
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 5.2.0 GA
Assignee: David Le Sage
QA Contact:
URL: http://jira.jboss.org/jira/browse/SOA...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-10-20 14:28 UTC by Marek Baluch
Modified: 2011-11-09 08:46 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-11-09 08:46:55 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-3505 0 None None None Never

Description Marek Baluch 2011-10-20 14:28:12 UTC 
Affects: Release Notes
project_key: SOA

The 'AcquireInstanceLock' exception may start popping up in the server log under heavy load.

Note from Jeff Yu: "So when you are doing the load tests again, you would see some 'AcquireInstanceLock' exceptions, thats fine because those jobs that didn't get the 'Instance Lock' successfully will be inserted into ODE_JOB table and got retried until they are succeed."
Comment 1 Marek Baluch 2011-10-20 14:30:05 UTC 
Link: Added: This issue depends RIFTSAW-456
Comment 2 Marek Baluch 2011-10-20 14:32:14 UTC 
This will be fixed in Riftsaw 3 which I think will not make it into SOA 5.2. IMO we should document this as known issue.
Comment 3 David Le Sage 2011-10-21 04:22:57 UTC 
Release Notes Docs Status: Added: Documented as Known Issue
Writer: Added: dlesage
Release Notes Text: Added: https://issues.jboss.org/browse/SOA-3505

If your server is working at high capacity, you may encounter 'AcquireInstanceLock' exceptions.  These have no impact as those jobs which did not obtain the 'Instance Lock' are sent to the ODE_JOB table from where they will be retried until they process successfully.
Comment 4 David Le Sage 2011-10-21 04:23:13 UTC 
Added to the release notes.
Comment 5 Marek Baluch 2011-11-09 08:46:55 UTC 
Verified in ER6 and http://documentation-stage.bne.redhat.com/docs/en-US/JBoss_Enterprise_SOA_Platform/5/html-single/5.2.0_Release_Notes/index.html
Note You need to log in before you can comment on or make changes to this bug.