-
1. Re: Failed to Route Reference[<message#>]:RELIABLE to queue
clebert.suconic Mar 23, 2009 6:21 PM (in response to javadba)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. -
2. Re: Failed to Route Reference[<message#>]:RELIABLE to queue
mlange Mar 24, 2009 8:18 AM (in response to javadba)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[68418585]:RELIABLE to moDnForwardQueue
at org.jboss.jms.server.endpoint.ServerConnectionEndpoint.sendMessage(ServerConnectionEndpoint.java:743)
Cheers,
Marek -
3. Re: Failed to Route Reference[<message#>]:RELIABLE to queue
javadba Apr 7, 2009 1:28 PM (in response to javadba)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 -
4. Re: Failed to Route Reference[<message#>]:RELIABLE to queue
javadba Apr 8, 2009 4:38 PM (in response to javadba)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.
-
5. Re: Failed to Route Reference[<message#>]:RELIABLE to queue
alexander.meyer Apr 9, 2009 10:31 AM (in response to javadba)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.