Mike Edwards wrote:
Freddy,
If you don't mind me being a bit presumptive, can I ask why you don't
consider using asynchronous services in this case?
>240 seconds is quite a long time for a client to wait for a service to
respond.
If you code the client and the service as asynchronous, using callbacks,
then you don't have to worry about stuff like timeouts since the
response comes back as a separate transmission.
I think that async callback services were designed specifically to meet
the needs of cases like the one that you have here.
+1 for this suggestion. If the service is (or can be exposed as)
an SCA service, I think this is the best approach.
However, if the service is a pre-existing Web service endpoint that
can't be exposed as an SCA service, there doesn't seem to be any
alternative to increasing the client timeout.
Simon
Yours, Mike.
PS - I am happy to give advice on how to construct your service and
client using async techniques.
Porsch, Freddy wrote:
Thank you for help,
yes our client need more tahn 240 seconds, is there any solution to
configurate the timeout dynamicly ?
-----Urspr�ngliche Nachricht-----
Von: Simon Nash [mailto:[EMAIL PROTECTED]
Gesendet: Montag, 15. September 2008 19:08
An: [email protected]
Betreff: Re: customizing timeout webservice
Porsch, Freddy wrote:
hello,
our webservice have to do a lot of calculating stuff, thats why we
have a timeout problem. Is there any solution to customize the
timeout in the axis2.xml ?
Is this the client-side timeout when making a Web service request?
In Axis2BindingInvoker.invokeTarget(), this is set to a hard-coded
value of 240 seconds. Tuscany uses this value to override what
appears in axis2.xml. Does your application need a client to wait for
more than 240 seconds?
Simon
CENIT AG Systemhaus, Industriestrasse 52-54, 70565 Stuttgart, Tel.: +49
711 7825-30, Fax: +49 711 7825-4000, Internet: www.cenit.de
Geschaeftsstellen: Berlin, Duesseldorf, Frankfurt, Hamburg, Hannover,
Muenchen, Saarbruecken
Vorstandsmitglieder: Kurt Bengel, Christian Pusch
Aufsichtsratsmitglieder: Andreas Schmidt (Vorsitzender des
Aufsichtsrats), Hubert Leypoldt, Andreas Karrer
Bankverbindungen:
Deutsche Bank (BLZ 600 700 70) Kto. 1661 040 IBAN : DE85 6007 0070
0166 1040 00 SWIFT-CODE : DEUTDESS, Commerzbank (BLZ 600 400 71) Kto.
532 015 500 IBAN : DE83 6004 0071 0532
0155 00 SWIFT-Code : COBADEFF600,
BW-Bank (BLZ 600 501 01) Kto. 2 403 313 IBAN : DE17 6005 0101 0002
4033
13 SWIFT-Code : SOLADEST
Registergericht: Amtsgericht Stuttgart
Handelsregister: HRB Nr. 19117
Umsatzsteuer: ID-Nr. DE 147 862 777
CENIT AG Systemhaus, Industriestrasse 52-54, 70565 Stuttgart, Tel.:
+49 711 7825-30, Fax: +49 711 7825-4000, Internet: www.cenit.de
Geschaeftsstellen: Berlin, Duesseldorf, Frankfurt, Hamburg, Hannover,
Muenchen, Saarbruecken
Vorstandsmitglieder: Kurt Bengel, Christian Pusch
Aufsichtsratsmitglieder: Andreas Schmidt (Vorsitzender des
Aufsichtsrats), Hubert Leypoldt, Andreas Karrer
Bankverbindungen:
Deutsche Bank (BLZ 600 700 70) Kto. 1661 040 IBAN : DE85 6007 0070
0166 1040 00 SWIFT-CODE : DEUTDESS,
Commerzbank (BLZ 600 400 71) Kto. 532 015 500 IBAN : DE83 6004 0071
0532 0155 00 SWIFT-Code : COBADEFF600,
BW-Bank (BLZ 600 501 01) Kto. 2 403 313 IBAN : DE17 6005 0101 0002
4033 13 SWIFT-Code : SOLADEST
Registergericht: Amtsgericht Stuttgart
Handelsregister: HRB Nr. 19117
Umsatzsteuer: ID-Nr. DE 147 862 777
