I am encountering the same error on JBoss 4.2.2 with JBossMQ. Is there a patch for this
issue in JBoss 4.2.2 or do we have to migrate to JBoss 4.2.3.GA?
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4151510#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...