Bug 778034 (SOA-559) - Document SOAP Processing workaround and result
Summary: Document SOAP Processing workaround and result
Keywords:
Status: CLOSED NEXTRELEASE
Alias: SOA-559
Product: JBoss Enterprise SOA Platform 4
Classification: JBoss
Component: Documentation
Version: 4.2 TP01
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 4.2 CP02
Assignee: Joshua Wulf
QA Contact:
URL: http://jira.jboss.org/jira/browse/SOA...
Whiteboard:
Depends On: SOA-288
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-05-31 01:02 UTC by Mark Little
Modified: 2014-10-19 23:00 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-06-10 09:27:08 UTC
Type: Task

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-559 0 None None None Never

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
Note You need to log in before you can comment on or make changes to this bug.