Taking a hint from Adrian's comments in that Jira issue, I extracted a copy of jboss-local-jdbc.jar from jboss-local-jdbc.rar and put it in my ear (actually, I put it in a .deployer in my ear that contains all my other jars). This solves the issue. To answer the question that Adrian posed in his comments - reloading the ear appears to work fine.
An interesting note - even if the suggestion I made for changing LocalManagedConnectionFactory is adopted, driver loading is not fully isolated unless you have the local copy of the jboss-local-jdbc.jar. If another version of a driver is placed in the central lib directory (e.g. server/default/lib) or in another, not isolated sar or ear, you will get that version of the driver, not the one in your ear. Having your own copy of jboss-local-jdbc.jar appears to be the only full way to isolate drivers from outside interference. Can you tell my app is deployed in environments where I have to be very careful of what other apps are doing? ;-) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3942947#3942947 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3942947 ------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
