Hide Forgot
Affects: Documentation (Ref Guide, User Guide, etc.), Release Notes Date of First Response: 2008-01-31 05:30:08 project_key: SOA
Link: Added: This issue depends SOA-288
Link: Added: This issue depends SOA-351
Josh, we may be creating a workaround for this issue. Can you hold off on this until I get back to you?
standing by...
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
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