axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dennis Merkel (JIRA)" <>
Subject [jira] Created: (AXIS2-3725) TCP connections in CLOSE_WAIT state after axis calls resulting in an exception
Date Thu, 10 Apr 2008 11:44:22 GMT
TCP connections in CLOSE_WAIT state after axis calls resulting in an exception

                 Key: AXIS2-3725
             Project: Axis 2.0 (Axis2)
          Issue Type: Bug
          Components: codegen
    Affects Versions: 1.1.1, 1.3
         Environment: BEA-Weblogic 8.1 SP6
            Reporter: Dennis Merkel

Similar problems reported in AXIS-2430, AXIS-2883 and SOAP-170.

Every axis call resulting in an exception (whether the server is down or server responding
with wsdl:fault) leaves behind a new tcp connection in the CLOSE_WAIT state. 
Once the maximum number for SOCKET_WAITs is reached (depending on operating system - the maximum
number of open file descriptors) no more calls could be handled until restart of BEA-Weblogic-Server.

The problem was fixed by adapting each java (wsdl:operation)-method of the generated client
stub as followed: the try-catch-block was extended with the finally block

            if(_messageContext != null){

The cleanup method in original stub is called only in try-block, so if an exception rises
during a web service call, code execution is continued in catch block without calling the
cleanup method leading by that to a new not cleaned up connection in the CLOSE_WAIT state.

- It is required to move the declaration of _messageContext variable before the try block
to make it visible in finally block
- Problem was initialy found on axis2 1.1.1, upgrade to 1.3 did not eliminate the problem

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message