I have seen that when a Clustered Destination is not deployed on every node.
As you should have all your clustered-destinations deployed on every node.
I have also seen this error if there are problems with the persistent store (db connection is gone e.g.):
2009-03-24 12:08:52,216 596710123 ERROR [org.jboss.messaging.util.ExceptionUtil] (WorkerThread#20[:54733]:) SessionEndpoint[tgbk-bjnhhosf-1-hu58mesf-7l6lod-l31e6a] send [vgbk-sjnhhosf-1-hu58mesf-7l6lod-l31e6a]
javax.jms.JMSException: Failed to route Reference:RELIABLE to moDnForwardQueue
Hi thanks for the replies. This is a non-clustered destination.
Regarding the db connection problems: why would that occur? The connections are under the control of the jboss messaging. Can you post a recommended postgres-persistence-service.xml -- I have tried ones from the samples and the distributions and so far they all have issues when using with non-clustered durable destinations
It appears that the problem were due to mismatch on the jboss-messaging.jar libraries. The default and production branch versions work, but the "all" does not.
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.