Is your client is a JBoss instance and the target is on a different instance?
In this case the exception occurs if the ServerPeerID (messaging-service.xml)
is not unique for all instances.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4224721#4224721
Reply
We solved the problem by deactivating the JMS JCA adapter before shutdown via a
twiddle script:
twiddle.sh invoke jboss.jca:name=\'jms-ra.rar\',service=RARDeployment stop
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4222889#4222889
Reply to the post :
Hello,
I have a problem with jboss server shutdown using a two-node jboss cluster
(4.2.2.GA) with JBM 1.4.2.GA. In the cluster are several queues and topics
deployed, all are configured as clustered and all messages are send with the
ClusteredConnectionFactory (Failover and Loadbalancing