Thanks, I was having trouble with 2 networked Fuse brokers (using store and forward activemq connection) where the JMS Flow messages ended up in the "other" broker (giving rise to no such service/endpoint errors) so I wanted to exclude those destinations from the network channel...
Turns out it was much simpler and the problem was that the servicemix containers had the same name on both servers (the default). Switched it and works fine now :) Thanks anyway, Alex Megalokonomos gnodet wrote: > > These are all prefixed with "org.apache.servicemix.jms.". > There is a queue for each endpoint (append the service qname and the > endpoint name to obtain the queue name), component and container. > > On 10/11/07, Alex_ynr <[EMAIL PROTECTED]> wrote: >> >> This might be a very silly question but I can't seem to figure it out... >> >> When using JMSFlow what are the queue/topic names created for the >> communication between components? >> >> Alex >> -- >> View this message in context: >> http://www.nabble.com/JMSFlow-Queue-Topic-Names-tf4606105s12049.html#a13152460 >> Sent from the ServiceMix - User mailing list archive at Nabble.com. >> >> > > > -- > Cheers, > Guillaume Nodet > ------------------------ > Blog: http://gnodet.blogspot.com/ > > -- View this message in context: http://www.nabble.com/JMSFlow-Queue-Topic-Names-tf4606105s12049.html#a13153503 Sent from the ServiceMix - User mailing list archive at Nabble.com.
