This looks like a JVM bug, could you try to update to 1.5.0_15 or 1.5.0_16 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4186744#4186744 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4186744