Bug 998659

Summary: Use one stateful knowledge session per BPM process instance
Product: [JBoss] JBoss Fuse Service Works 6 Reporter: David Ward <dward>
Component: SwitchYardAssignee: David Virgil <dvirgiln>
Status: CLOSED WORKSFORME QA Contact: Jiri Sedlacek <jsedlace>
Severity: high Docs Contact:
Priority: unspecified    
Version: 6.0.0 GACC: aileenc, atangrin, dlesage, kconner, ldimaggi, oskutka, rcernich, soa-p-jira, tcunning
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
There is a performance impact if you use the same stateful knowledge session across multiple process instances. This is because the one-session-for-all-processInstances model is inherently single threaded. When the transaction is started, it will pessimistically lock the SessionInfo table, blocking other threads. To avoid this, create mapping so that a session is only ever used for one process instance and use a unique JPA entity manager.
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-07-14 17:08:30 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description David Ward 2013-08-19 17:46:49 UTC
See JBoss JIRA: SWITCHYARD-1584

Comment 2 tcunning 2015-07-14 17:08:30 UTC
We're moving to using JIRA to track issues for Fuse 6.2.1.    I've logged https://issues.jboss.org/browse/ENTESB-3628 to track the product version of this issue.    Closing and work will continue in the associated JIRA.

Comment 3 JBoss JIRA Server 2015-12-21 09:48:00 UTC
David virgil naranjo <david.virgil.naranjo> updated the status of jira SWITCHYARD-1584 to Closed