axis-c-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Raghu Udupa" <rud...@easylink.com>
Subject RE: Spurious client time out errors -- duplicate transmission
Date Fri, 06 Feb 2009 16:39:31 GMT
It was my problem. I forgot to multiply by 1000 when setting time-out in
milliseconds.



Regards,

Raghu

 

________________________________

From: Raghu Udupa [mailto:rudupa@easylink.com] 
Sent: Friday, February 06, 2009 9:45 AM
To: Apache AXIS C User List
Subject: RE: Spurious client time out errors -- duplicate transmission

 

Hi,

 

This problem happens only when I use HTTP protocol.  With HTTPS every
thing works fine. One message is sent and one is received.

 

I am using Axis2C/1.5.0 on a Linux server as a client communicating to a
Web service. Each message is delivered to a possibly different web
service through a separate process. The process communicates either via
http or https depending on remote web service configuration

 

On couple of occasions, I got time out error at the client, while
message was successfully received at the host. I have set the session
time out to 3 minutes. When I enable the trace log, this problem does
not happen. Here is a snapshot of axis2c log.

 

1)

[Thu Feb  5 17:05:03 2009] [error] http_client.c(460) Response timed out

[Thu Feb  5 17:05:03 2009] [error] http_sender.c(1342) status_code < 0

[Thu Feb  5 17:05:03 2009] [error] engine.c(179) Transport sender invoke
failed

2)

[Thu Feb  5 17:05:03 2009] [error] http_client.c(460) Response timed out

[Thu Feb  5 17:05:03 2009] [error] http_sender.c(1342) status_code < 0

[Thu Feb  5 17:05:03 2009] [error] engine.c(179) Transport sender invoke
failed

3)

[Thu Feb  5 17:15:41 2009] [error] http_client.c(460) Response timed out

[Thu Feb  5 17:15:41 2009] [error] http_sender.c(1342) status_code < 0

[Thu Feb  5 17:15:41 2009] [error] engine.c(179) Transport sender invoke
failed

4)

[Thu Feb  5 17:19:47 2009] [error] http_client.c(460) Response timed out

[Thu Feb  5 17:19:47 2009] [error] http_sender.c(1342) status_code < 0

[Thu Feb  5 17:19:47 2009] [error] engine.c(179) Transport sender invoke
failed

 

For each of the above 4 attempts, message was delivered at the web
service. In addition, the client received time-out as soon as the
request was sent even though session timeout is set to 180 seconds.

 

Here is the time when message was sent.

1)

17:05:02 16 [9406] SendMessage: Call web service. Signature reqd <0>

17:05:03 16 [9406] axis2_stub_op_ReceiveEasyLinkFaxService_ReceiveFax:
return code is null

 

2)

17:05:03 16 [9407] SendMessage: Call web service. Signature reqd <0>

17:05:03 16 [9407] axis2_stub_op_ReceiveEasyLinkFaxService_ReceiveFax:
return code is null

3)

17:15:41 16 [9672] SendMessage: Call web service. Signature reqd <0>

17:15:41 16 [9672] axis2_stub_op_ReceiveEasyLinkFaxService_ReceiveFax:
return code is null

4)

17:19:47 16 [9726] SendMessage: Call web service. Signature reqd <0>

17:19:47 16 [9726] axis2_stub_op_ReceiveEasyLinkFaxService_ReceiveFax:
return code is null

 

Thanks,

Raghu

 


Mime
View raw message