And for completeness, though this is discussed ad infinitum elsewhere. Thread local patterns are stupid. You can cause database connections to leak across transaction boundaries with work getting done in random transactions.
Hibernate3 does not use this pattern, it uses the datasource pool as a .... pool. TransactionLocal or sticky transaction connection caching is done by the j2ee connection manager anyway! in jboss: | <track-connection-by-tx/> | enabled by default for local-tx-datasource and not really relevant for XA (unless the driver doesn't support interleaving). View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3911035#3911035 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3911035 ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
