Hi Arun,
I have been looking into this a bit more, but seem to have a hard time getting this to reproduce the exact same error that you're seeing. I suspect there either is a problem with the Filter in the OsgiSimpleClusterRegistration (that's what I had earlier on with the plain Spring syntax, where the ref fixed it) or something like that. Perhaps with a simple example, we can troubleshoot this further but I'm a bit out of ideas here at the moment, I'm afraid. Given that JBI is deprecated, another option could be to look at an alternative and explicitly introduce JMS endpoints between the two HTTP endpoints. Since you already have the ActiveMQ network-of-brokers setup, you can put a message on a queue on machine 1 and receive it on machine 2. You could do http -> jms on machine 1 and then jms -> http on machine 2. If you ever migrate the application the application to plain Camel routes, that approach would remain the same. Regards, Gert Vanthienen On Mon, Mar 31, 2014 at 10:54 PM, arun kumar <[email protected]> wrote: > Hello Gert, > > Its an xbean.xml file package in a SU and the SU inturn packaged in a SA. > > Regards, > Arun > > > > -- > View this message in context: > http://servicemix.396122.n5.nabble.com/JBI-cluster-not-working-with-ActiveMQPool-tp5719698p5719771.html > Sent from the ServiceMix - User mailing list archive at Nabble.com.
