It looks to me like ejb3 is swallowing the stack trace (it has an annoying habit of doing this in async stuff). We need the stack of the original exception (wrap your code in a try-catch and use e.printStackTrace()).
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4019415#4019415 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4019415 _______________________________________________ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
