Bug 778034 (SOA-559)

Summary: Document SOAP Processing workaround and result
Product: [JBoss] JBoss Enterprise SOA Platform 4 Reporter: Mark Little <mark.little>
Component: DocumentationAssignee: Joshua Wulf <jwulf>
Status: CLOSED NEXTRELEASE QA Contact:
Severity: high Docs Contact:
Priority: high    
Version: 4.2 TP01CC: lcarlon
Target Milestone: ---   
Target Release: 4.2 CP02   
Hardware: Unspecified   
OS: Unspecified   
URL: http://jira.jboss.org/jira/browse/SOA-559
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2008-06-10 09:27:08 UTC Type: Task
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On: 777772    
Bug Blocks:    

Description Mark Little 2008-05-31 01:02:51 UTC 
Affects: Documentation (Ref Guide, User Guide, etc.), Release Notes
Date of First Response: 2008-06-02 02:09:25
project_key: SOA
Comment 1 Mark Little 2008-05-31 01:03:02 UTC 
Link: Added: This issue depends SOA-288
Comment 2 Joshua Wulf 2008-06-02 06:09:25 UTC 
7.1. SOAPProcessor cannot handle large message backlog

A database issue in the current release can cause resources to be exhausted in large transactions.

The workaround for this is to add the following lines to your datasource configuration:

<share-prepared-statements>true</share-prepared-statements>
<prepared-statement-cache-size>10<prepared-statement-cache-size>

You can tune the prepared-statement-cache-size to your situation. It is important that you enable share-prepared-statements.

Further information: http://jira.jboss.com/jira/browse/SOA-288
Comment 3 Jiri Pechanec 2008-06-10 09:27:08 UTC 
Verified in CR1