We are experiencing the exact same bug in both JBoss 4.2.1 AS and JBoss 4.2.2 AS which has become a showstopper for us.
I can provide any kinds of stack traces, AOP XML files or any other code you will require to fix this major bug. Does Redhat have any suggestions or a timeline for resolution of this major bug? Thank you. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4109443#4109443 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4109443 _______________________________________________ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
