Yes, that is what I tried in my desperation:) It is easyer to wait 5 seconds than 5 minutes. It does not seem to have any effect though. The timeout is still 60 secs.
thanks, attila Agustín Gañán wrote: > > Hi, > > I think the clientSoTimeout specifies the timeOut in miliseconds [1]. > With your config (clientSoTimeout="5000"), you specify a 5 seconds timeout > > Hope this helps, > > Agus > > [1] http://servicemix.apache.org/servicemix-http-new-endpoints.html > > 2010/4/29 attilav <[email protected]> > >> >> Hi everyone, >> >> I'm using servicemix 3.3.1 with camel 1.6.2 for routing messages to an >> external webservice. Basically the message is taken from a queue by >> camel, >> and routed to a jbi servicemix soap-provider. The remote service >> sometimes >> take up to five minutes to respond, but servicemix timeouts after 60 >> seconds. >> I figured I need to set the clientSoTimeout property of the >> soap-provider, >> however that does not seem to have any effect on the timeout. >> >> Is clientSoTimeout the right parameter for this? >> >> ------------------------ >> from("activemq:queue:flower2wfms?disableReplyTo=true") >> .to("jbi:endpoint:http://blabla...&mep=in-out";) >> >> ------------------------ >> <http:soap-provider service="wfms:fault_ticket" >> endpoint="fault_ticket" >> locationURI="${wfms.outbound.uri.fault_ticket}" >> wsdl="${wfms.outbound.wsdl.fault_ticket}" >> useJbiWrapper="false" >> clientSoTimeout="5000"> >> </http:soap-provider> >> >> regards, >> attila >> -- >> View this message in context: >> http://old.nabble.com/http%3Asoap-provider-timeout-question-tp28398366p28398366.html >> Sent from the ServiceMix - User mailing list archive at Nabble.com. >> >> > > -- View this message in context: http://old.nabble.com/http%3Asoap-provider-timeout-question-tp28398366p28398624.html Sent from the ServiceMix - User mailing list archive at Nabble.com.
