Bug 777849 (SOA-377)

Summary: Document JBM Cursors issue and the effect.
Product: [JBoss] JBoss Enterprise SOA Platform 4 Reporter: Mark Little <mark.little>
Component: Documentation, JBoss MessagingAssignee: Joshua Wulf <jwulf>
Status: CLOSED NEXTRELEASE QA Contact:
Severity: urgent Docs Contact:
Priority: urgent    
Version: 4.2 CR1CC: lcarlon, rcampbell
Target Milestone: ---   
Target Release: 4.2 CR3   
Hardware: Unspecified   
OS: Unspecified   
URL: http://jira.jboss.org/jira/browse/SOA-377
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2008-02-07 04:10:51 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, 777825    
Bug Blocks:    

Description Mark Little 2008-01-31 08:17:00 UTC
Affects: Documentation (Ref Guide, User Guide, etc.), Release Notes
Date of First Response: 2008-01-31 05:30:08
project_key: SOA

Comment 1 Mark Little 2008-01-31 08:17:16 UTC
Link: Added: This issue depends SOA-288


Comment 2 Mark Little 2008-01-31 08:21:45 UTC
Link: Added: This issue depends SOA-351


Comment 3 Kevin Conner 2008-01-31 10:30:08 UTC
Josh, we may be creating a workaround for this issue.  Can you hold off on this until I get back to you?

Comment 4 Joshua Wulf 2008-01-31 11:22:47 UTC
standing by...

Comment 5 Kevin Conner 2008-02-04 18:58:15 UTC
Hiya Josh.

We have a workaround for this issue but it will still need to be accompanied by some documentation.

If someone chooses to reconfigure the datasource used by JBM then we must make sure that it is a separate datasource, used solely by JBM, and that they include the following elements in their ds file

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

The first element enables the caching of the prepared statements and a reasonable value would appear to be 50.  The second element forces the cache to reuse prepared statements whether they have been closed or not.

Including both of these elements in the ds is an appropriate workaround for JBMESSAGING-1218.

Kev

Comment 6 Joshua Wulf 2008-02-07 01:37:02 UTC
Settings for JBoss Messaging Datasource

   As a workaround for an issue in JBoss Messaging, which will be resolved in a future update, specific settings are required when configuring a datasource for use with JBoss Messaging.

   If you reconfigure the datasource used by JBoss Messenging, you should ensure that this datasource is used exclusively by JBoss Messaging, and that the ds file contains the following elements:

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

   Further Information: This is a workaround for the issue described in http://jira.jboss.com/jira/browse/SOA-288