I am facing the same issue in production right now. The axis stub already has cleanTransport -- _messageContext.getTransportOut().getSender().cleanup(_messageContext);
We have set reuse_option to true. Rest of values are set to default.. Greatly appreciate help... The thread dump shows threads waiting like this: at java.lang.Object.wait(Native Method) at org.apache.commons.httpclient.MultiThreadedHttpConnectionManager.doGetConnection(MultiThreadedHttpConnectionManager.java:509) at org.apache.commons.httpclient.MultiThreadedHttpConnectionManager.getConnectionWithTimeout(MultiThreadedHttpConnectionManager.java:394) at org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:152) at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:396) at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:346) at org.apache.axis2.transport.http.AbstractHTTPSender.executeMethod(AbstractHTTPSender.java:558) at org.apache.axis2.transport.http.HTTPSender.sendViaPost(HTTPSender.java:176) at org.apache.axis2.transport.http.HTTPSender.send(HTTPSender.java:73) at org.apache.axis2.transport.http.CommonsHTTPTransportSender.writeMessageWithCommons(CommonsHTTPTransportSender.java:305) at org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(CommonsHTTPTransportSender.java:201) at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:452) at org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:330) at org.apache.axis2.description.OutInAxisOperationClient.execute(OutInAxisOperation.java:294) at com.xxx.HelloStub.hello1(HelloStub.java:173) JIRA j...@apache.org wrote: > > > [ > https://issues.apache.org/jira/browse/AXIS2-3670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12682033#action_12682033 > ] > > Dobri Kitipov commented on AXIS2-3670: > -------------------------------------- > > I think that this issue has a solution. You can solve it doing one of the > following: > > - Call the "cleanupTransport" in service client > (client.cleanupTransport()); > - setting the option.setCallTransportCleanup(true); > - invoke > messageContext.getTransportOut().getSender().cleanup(messageContext); > > all this should release your http connection and return it into the pool > for reuse. > > Additionally it is always a good practice to invoke: > > client.cleanup(); > > Doing so you releases resources (and memory) assigned to the client and > can solve "java.lang.OutOfMemoryError: Java heap space" issues if any. > > IMHO this JIRA should be closed. What do you think? > > Regards, > Dobri > >> Problem using REUSE_HTTP_CLIENT - Application stalls >> ---------------------------------------------------- >> >> Key: AXIS2-3670 >> URL: https://issues.apache.org/jira/browse/AXIS2-3670 >> Project: Axis 2.0 (Axis2) >> Issue Type: Bug >> Affects Versions: 1.3 >> Reporter: Alois Reitbauer >> Priority: Critical >> Attachments: Stalled call vs. executing call.jpg >> >> >> When using REUSE_HTTP_CLIENT on a service client to reuse a http client >> the client application hangs after 3 executions. The reason is that it >> obviously waits in >> MultithreadedHttpConnectionManager.getConnectionWithTimeout() > > -- > This message is automatically generated by JIRA. > - > You can reply to this email to add a comment to the issue online. > > > -- View this message in context: http://www.nabble.com/-jira--Created%3A-%28AXIS2-3670%29-Probelm-using-REUSE_HTTP_CLIENT-tp16331279p23302377.html Sent from the Axis - Dev mailing list archive at Nabble.com.
