You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by "Sri (JIRA)" <ji...@apache.org> on 2009/11/19 17:49:39 UTC
[jira] Issue Comment Edited: (AXIS2-4330) axis2 client machine has
many CLOSE_WAIT tcp
[ https://issues.apache.org/jira/browse/AXIS2-4330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12779603#action_12779603 ]
Sri edited comment on AXIS2-4330 at 11/19/09 4:49 PM:
------------------------------------------------------
Daniels,
We upgraded to axis2 1.5.1 from axis2 1.3 (Since we hit the CLOSE_WAIT conecction built up over period of time issue in production and 'too many open files' error with axis2 1.3) to get the above said fix and added the following statement after service call.
stub._getServiceClient().cleanupTransport();
It does help to have one CLOSE_WAIT connection per client instance. (we have multiple client instances in running)
But all of sudden, one instance threw nullpointerexception while releasing the connection.
Exception in thread "Timer-0" java.lang.NullPointerException
at org.apache.commons.httpclient.HttpMethodBase.responseBodyConsumed(HttpMethodBase.java:2405)
at org.apache.commons.httpclient.HttpMethodBase$1.responseConsumed(HttpMethodBase.java:1892)
at org.apache.commons.httpclient.AutoCloseInputStream.notifyWatcher(AutoCloseInputStream.java:198)
at org.apache.commons.httpclient.AutoCloseInputStream.close(AutoCloseInputStream.java:158)
at org.apache.commons.httpclient.HttpMethodBase.releaseConnection(HttpMethodBase.java:1181)
at org.apache.axis2.transport.http.CommonsHTTPTransportSender.cleanup(CommonsHTTPTransportSender.java:84)
at org.apache.axis2.client.ServiceClient.cleanupTransport(ServiceClient.java:824)
at java.util.TimerThread.mainLoop(Unknown Source)
at java.util.TimerThread.run(Unknown Source)
Any ideas? Do I need to do as Amila advised above in the thread?
Thanks in advance,
Sri
was (Author: time):
Daniels,
We upgraded to axis2 1.5.1 from axis2 1.3 (Since we hit the CLOSE_WAIT conecction built up over period of time issue in production and 'too many open files' error with axis2 1.3) to get the above said fix and added the following statement after service call.
stub._getServiceClient().cleanupTransport();
It does help to have one CLOSE_WAIT connection per client instance. (we have multiple client instances in running)
But all of sudden, one instance threw nullpointerexception while releasing the connection.
Exception in thread "Timer-0" java.lang.NullPointerException
at org.apache.commons.httpclient.HttpMethodBase.responseBodyConsumed(HttpMethodBase.java:2405)
at org.apache.commons.httpclient.HttpMethodBase$1.responseConsumed(HttpMethodBase.java:1892)
at org.apache.commons.httpclient.AutoCloseInputStream.notifyWatcher(AutoCloseInputStream.java:198)
at org.apache.commons.httpclient.AutoCloseInputStream.close(AutoCloseInputStream.java:158)
at org.apache.commons.httpclient.HttpMethodBase.releaseConnection(HttpMethodBase.java:1181)
at org.apache.axis2.transport.http.CommonsHTTPTransportSender.cleanup(CommonsHTTPTransportSender.java:84)
at org.apache.axis2.client.ServiceClient.cleanupTransport(ServiceClient.java:824)
at com.telcordia.sirgpd.driver.titan.v_6_5.TitanNormalizedDriver.sendBatch(TitanNormalizedDriver.java:181)
at com.telcordia.sirgpd.driver.titan.v_6_5.TitanNormalizedDriver.batch(TitanNormalizedDriver.java:133)
at com.telcordia.sirgpd.common.Distributor.batch(Distributor.java:93)
at com.telcordia.sirgpd.common.OutputQConsumerTask.processOutputQData(OutputQConsumerTask.java:250)
at com.telcordia.sirgpd.common.OutputQConsumerTask.run(OutputQConsumerTask.java:376)
at java.util.TimerThread.mainLoop(Unknown Source)
at java.util.TimerThread.run(Unknown Source)
Any ideas? Do I need to do as Amila advised above in the thread?
Thanks in advance,
Sam
> axis2 client machine has many CLOSE_WAIT tcp
> ---------------------------------------------
>
> Key: AXIS2-4330
> URL: https://issues.apache.org/jira/browse/AXIS2-4330
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: client-api
> Affects Versions: 1.4.1
> Environment: solaris
> Reporter: jenny anderson
> Fix For: 1.5.1
>
> Attachments: TuxedoWebServiceStub.java
>
>
> My application is using axis2 web service. It invokes web service thousand times per second. We observed thousand CLOSE_WAIT connection after the application is run for less than 10 hours. I checked even I set REUSE_HTTP_CLIENT to false, it still gets CLOSE_WAIT.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.