Could be prepared statement caching is not working out for you. Perhaps you're not closing them?
What did your profiler saying? It could be your use of the JDBC on the legacy server wasn't correct. Likely an unclosed result set or something. The pooling is a little bit of overhead, but not significant (more than 1-2ms I'd say) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3913903#3913903 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3913903 ------------------------------------------------------- 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 JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
