Are you using JDK 1.6? Seeing the stack trace, it must be the same problem reported in
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4126422, for which we
already have a solution.
The current workaround is to use JDK 1.5. You can stay on JBoss 4.2.2.GA or try JBoss
4.0.5.GA, as shefagarwal suggests. But the key point is to avoid JDK 1.6.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4126423#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...