This generally happens when you have your JDBC driver jar files inside another deployable
unit (WAR, EAR) and not in server/lib. It is a ClassLoader issue with the DriverManager in
the VM, not in JBossAS.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3993421#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...