Have you been able to find out the root cause of this issue? I'm seeing the same
exception thrown using JBossAS 4.0.5CR1. I'd like to find out if there's a
solution or known bug to this before I start digging in the code.
Thanks,
Hany
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3971917#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...