I just encountered this same issue in jboss-6.0.0.Final. Maybe a regresion? The ClassLoader switching suggested by jaikiran worked around it but the same application code was previously working on jboss 5.1 without it.
Reply to this message by going to Community
Start a new discussion in JBoss Messaging at Community