You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@servicemix.apache.org by attilav <dz...@freemail.hu> on 2010/04/29 11:24:34 UTC

http:soap-provider timeout question

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.


Re: http:soap-provider timeout question

Posted by iocanel <ca...@upstreamsystems.com>.

Is option 1)  global? All http endpoints will be affected?

Isn't it possible to configure a jetty client from sppring, and pass it to
the endpoint?

iocanel wrote:
> 
> 

Option 1 is global. However the component.properties doesn't seem to include
a property for socket timeout.



-----
Ioannis Canellos
-- 
View this message in context: http://old.nabble.com/http%3Asoap-provider-timeout-question-tp28398366p28410607.html
Sent from the ServiceMix - User mailing list archive at Nabble.com.


Re: http:soap-provider timeout question

Posted by attilav <dz...@freemail.hu>.
thanks for your reply.

I'm quite new to servicemix. Does that mean that your 2nd option would not
work?

Is option 1)  global? All http endpoints will be affected?

Isn't it possible to configure a jetty client from sppring, and pass it to
the endpoint?

regards,
attila


iocanel wrote:
> 
> 
> 
> iocanel wrote:
>> 
>> The HttpProviderEndpoint and HttpSoapProviderEndpoint use a pool of jetty
>> client connections. By default this pool is managed/configured by the
>> endpoint itself and not the endpoint.
>> 
>> There are 2 ways to set the timeout.
>> 1) Configure it on the component by editing the component.properties
>> file.
>> 2) Specify the your endpoint uses its own client. you can do that by
>> adding
>> ownClient="true" on your endpoint.
>> 
>> Edit: I checked the source and it set explicitly the timeout even when
>> the client is shared. :-((
>> 
>> 
>> 
> 
> 

-- 
View this message in context: http://old.nabble.com/http%3Asoap-provider-timeout-question-tp28398366p28402547.html
Sent from the ServiceMix - User mailing list archive at Nabble.com.


Re: http:soap-provider timeout question

Posted by iocanel <ca...@upstreamsystems.com>.


iocanel wrote:
> 
> The HttpProviderEndpoint and HttpSoapProviderEndpoint use a pool of jetty
> client connections. By default this pool is managed/configured by the
> endpoint itself and not the endpoint.
> 
> There are 2 ways to set the timeout.
> 1) Configure it on the component by editing the component.properties file.
> 2) Specify the your endpoint uses its own client. you can do that by
> adding
> ownClient="true" on your endpoint.
> 
> Edit: I checked the source and it set explicitly the timeout even when the
> client is shared. :-((
> 
> 
> 


-----
Ioannis Canellos
-- 
View this message in context: http://old.nabble.com/http%3Asoap-provider-timeout-question-tp28398366p28401127.html
Sent from the ServiceMix - User mailing list archive at Nabble.com.


Re: http:soap-provider timeout question

Posted by iocanel <ca...@upstreamsystems.com>.
The HttpProviderEndpoint and HttpProviderEndpoint use a pool of jetty client
connections. By default this pool is managed/configured by the endpoint
itself and not the endpoint.

There are 2 ways to set the timeout.
1) Configure it on the component by editing the component.properties file.
2) Specify the your endpoint uses its own client. you can do that by adding
ownClient="true" on your endpoint.



-----
Ioannis Canellos
-- 
View this message in context: http://old.nabble.com/http%3Asoap-provider-timeout-question-tp28398366p28401065.html
Sent from the ServiceMix - User mailing list archive at Nabble.com.


Re: http:soap-provider timeout question

Posted by attilav <dz...@freemail.hu>.
Tried it:  Invalid property 'timeout' of bean class
[org.apache.servicemix.http.endpoints.HttpSoapProviderEndpoint].

Maybe it applies only for consumer endpoints, it is not clear from the doc.

thanks,
attila





Agustín Gañán wrote:
> 
> Have you tried the "timeout" property of the endpoint [1]?
> According to the docs it should be 0 (no timeout), but maybe you can
> try...
> 
> 
> [1]
> http://repo1.maven.org/maven2/org/apache/servicemix/servicemix-http/2009.01/servicemix-http-2009.01-schema.html#endpoint
> 
> 2010/4/29 attilav <dz...@freemail.hu>
> 
>>
>> 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 <dz...@freemail.hu>
>> >
>> >>
>> >> 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.
>>
>>
> 
> 

-- 
View this message in context: http://old.nabble.com/http%3Asoap-provider-timeout-question-tp28398366p28399950.html
Sent from the ServiceMix - User mailing list archive at Nabble.com.


Re: http:soap-provider timeout question

Posted by Agustín Gañán <ag...@gmail.com>.
Have you tried the "timeout" property of the endpoint [1]?
According to the docs it should be 0 (no timeout), but maybe you can try...


[1]
http://repo1.maven.org/maven2/org/apache/servicemix/servicemix-http/2009.01/servicemix-http-2009.01-schema.html#endpoint

2010/4/29 attilav <dz...@freemail.hu>

>
> 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 <dz...@freemail.hu>
> >
> >>
> >> 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.
>
>

Re: http:soap-provider timeout question

Posted by attilav <dz...@freemail.hu>.
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 <dz...@freemail.hu>
> 
>>
>> 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.


Re: http:soap-provider timeout question

Posted by Agustín Gañán <ag...@gmail.com>.
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 <dz...@freemail.hu>

>
> 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.
>
>