On 5/22/06, pgodot <[EMAIL PROTECTED]> wrote:
Thanks Guillaume, I did some test but sleep() doesn't resolve the problem. I don't think it come from a init/start synchronization. I removed the eip and call directly my remote component and I had the same behavior. We can remove EIP form the picture.
I was not talking about the EIP component, but about the remote client which takes some times before discovering the other servicemix. I'm suspecting something wrong in the JMS Flow, configuration, client usage, Try to step by step your test code. You should see something in the log when the jms brokers discover each other. ...
I will continue to check to raise the good Jira. Could we put RemoteSMClient object in static? is it Thread Safe?
The remote client should be thread safe. The only problem is if you want to use asynchonous sends with InOut MEPs. Cheers, Guillaume Nodet Thanks for your help,
Phil -- View this message in context: http://www.nabble.com/RemoteServiceMixClient+-+EIP+component+-+done+an+IOMEX-t1644809.html#a4508216 Sent from the ServiceMix - User forum at Nabble.com.
-- Cheers, Guillaume Nodet
