Thanks for your reply, actually, it pointed me the way to solve my problem..
Just for the record I had the same error as you mate (same stack). In this particular case the app wasn't using Hibernate as a jboss service. And the resolution was different. I spent a long time trying to figure what was going wrong when i found in the middle of app's legacy jars a jta.jar that was causing the problem. This jar was placed in the app's context (/lib). A simple shift+del solved it. ;-) Cheers, :Luiz. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3920085#3920085 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3920085 ------------------------------------------------------- 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://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
