I think this issue is caused by a bug in JBoss AS 6.A workaround for JBoss AS 6.0.CR1 would be to move your jdbc driver from <AS_HOME>/server/lib to <AS_HOME>/server/default/lib (supposing you are using the default configuration).
Reply to this message by going to Community
Start a new discussion in JBoss Tools at Community