I am not sure whether that bug existed even in 4.0.4. But based on the comments from the user, in the referenced forum thread in that JIRA: anonymous wrote : This was working fine in version 4.2.2 GA So you could give 4.2.2 or 4.2.3 GA a try. You did not post the entire exception stacktrace and the relevant console logs, so i am guessing its the same issue. Please post these details, and let's see if it's something else. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4224074#... Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...