Stephen, We're getting same thing :)
Think we just figured things out -- our EAR had jms.jar and jboss-messaging-client.jar.
We removed both of these just in case of classpath conflict and this message went away.
Give this a shot and see. Not sure if you have to remove BOTH of the jars, but this is
what we did.
-Dustin
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4058923#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...