[
https://issues.apache.org/jira/browse/AXIS2-4709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
mohan sainath updated AXIS2-4709:
---------------------------------
Description:
Every axis call results in a TCP connection in the CLOSE_WAIT state. Although
the stub class gives the following call to close the connection in the finally
block, yet a netstat command shows the connection in the CLOSE_WAIT mode
_messageContext.getTransportOut().getSender().cleanup(_messageContext);
I use the weblogic server v8.1.5. I also observe that certain of the AXIS web
service calls do get closed, but a certain number of calls remain in the
CLOSE_WAIT mode.
I also used the following cleanup calls to close the connection but none of
them really works:
stub._getServiceClient().cleanupTransport();
stub._getServiceClient().cleanup();
stub.cleanup();
stub._getServiceClient().getAxisConfiguration().cleanup();
Any help will be appreciated.
> TCP connections in CLOSE_WAIT state in axis2 v1.4.1 even after client sockets
> are closed
> ----------------------------------------------------------------------------------------
>
> Key: AXIS2-4709
> URL: https://issues.apache.org/jira/browse/AXIS2-4709
> Project: Axis2
> Issue Type: Bug
> Components: transports
> Affects Versions: 1.4.1
> Reporter: mohan sainath
>
> Every axis call results in a TCP connection in the CLOSE_WAIT state. Although
> the stub class gives the following call to close the connection in the
> finally block, yet a netstat command shows the connection in the CLOSE_WAIT
> mode
> _messageContext.getTransportOut().getSender().cleanup(_messageContext);
> I use the weblogic server v8.1.5. I also observe that certain of the AXIS web
> service calls do get closed, but a certain number of calls remain in the
> CLOSE_WAIT mode.
> I also used the following cleanup calls to close the connection but none of
> them really works:
> stub._getServiceClient().cleanupTransport();
> stub._getServiceClient().cleanup();
> stub.cleanup();
> stub._getServiceClient().getAxisConfiguration().cleanup();
> Any help will be appreciated.
--
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: [email protected]
For additional commands, e-mail: [email protected]
