The admin doc says. "A SQL statement that should be run on a connection before it is returned from the pool to test its validity. This allows for the dection of stale pool connections. An example statement could be Âselect count(*) from x " Does this mean that this sql is executed every time i call the datasource.getConnection (say in a session bean). This sounds like an ineffecient way to achieve transparent failover. The exception sorter misses out on one transaction. Is there a better way of achieving transparent failover. Theoretically it should be possible to re execute the sql with another connection. Is it possible to do this with jboss. I have searched the forum and google and cant find any information about this. Any help will be appreciated
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3847710#3847710 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3847710 ------------------------------------------------------- This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170 Project Admins to receive an Apple iPod Mini FREE for your judgement on who ports your project to Linux PPC the best. Sponsored by IBM. Deadline: Sept. 13. Go here: http://sf.net/ppc_contest.php _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
