axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [jira] Assigned: (AXIS-769) Socket Timeouts for Axis Clients
Date Wed, 24 Mar 2004 23:41:57 GMT

   The following issue has been re-assigned.

   Assignee: Davanum Srinivas (
View the issue:

Here is an overview of the issue:
        Key: AXIS-769
    Summary: Socket Timeouts for Axis Clients
       Type: Bug

     Status: Reopened

    Project: Axis
             Basic Architecture
             current (nightly)

   Assignee: Davanum Srinivas
   Reporter: Davanum Srinivas

    Created: Mon, 24 Mar 2003 1:22 PM
    Updated: Wed, 24 Mar 2004 3:39 PM
Environment: Operating System: Other
Platform: Other

Note from "Jens Schumann" <> on axis-dev@ mailing list.

Some broken load balancers in our network configuration caused hanging
connections calling WebServices using Axis Clients (1.1RC2). Since the
generated Axis Client Code does not set a default socket timeout the calling
thread was blocking forever, something which wasn't as obvious as it could
be. A default socket timeout would have been wonderful ;)

With the current client code I am unable to set the socket timeout directly,
so I need to alter the generated code to set a socket timeout for the
underlying HttpSender. You may argue easy to fix, but there is another
problem: The client code throws RemoteExceptions (and AxisFaults) only, so I
am unable to treat local and remote failures differently. Analyzing Axis
fault Strings isn't the best way to implement Exception handling.

I am somewhat short on time and thus being said I hope someone else might be
able to implement the following changes ;(.

1. Set default socket timeout for Axis Clients to 30 or 60 seconds.
2. Generate code which allows to set the socket timeout for the axis client
3. Add a local exception (IOException?) to the exposed web service
operations to allow better handling of local (socket) exceptions.

I think 1 & 2 should be easy to fix, but 3 will break backwards


This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:

If you want more information on JIRA, or have a bug to report see:

View raw message