FWIW, the network was switching to a VPN connection after the broker had started and the client had connected. It was also a VPN connection that couldn't do nslookups. Not doing that and the routing from scratch seems to be fine.
Alistair ------------------- Alistair Young Senior Software Engineer UHI@Sabhal Mòr Ostaig >>> "Alistair Young" 23/07/12 11:31 AM >>> I've just noticed in 5.6.0 that the routing doesn't work until you either send a dummy message to the start of a route to 'create the topic/wake it up' it seems, or restart the broker after the client has connected: wake-up method: - start broker - send message to topicA which should be routed to topicB - this message is lost. The routing doesn't work for the first message - send message to topicA which should be routed to topicB - connect durable topic subscriber to topicB - consumer gets message on topicB restart method: - start broker - connect durable topic subscriber to topicB - send message to topicA which should be routed to topicB - nothing happens - send more message to topicA - all are lost - restart broker - connect durable topic subscriber to topicB - send message to topicA which should be routed to topicB - consumer gets message on topicB the sending and consuming are all via STOMP. It seems to need topicA to have been created by first sending a message to it. e.g. out of the box routing doesn't do anything until the first message has been sent. Clients can connect and consume after that. If a client has already connected to a route that has not been used before a broker restart is required before it can get any messages from the route. Is this just normal behaviour? thanks, Alistair ------------------- Alistair Young Senior Software Engineer UHI@Sabhal Mòr Ostaig
