FYI this is likely the result of
https://jira.jboss.org/jira/browse/JBPAPP-366. The bug
is present in JBoss 4.2.3 (and presumably 4.2.2). We ended up having go with JBossNative,
to work around the issue.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4208774#...
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...