[ 
https://issues.apache.org/jira/browse/AXIS2-5251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13219137#comment-13219137
 ] 

TEST commented on AXIS2-5251:
-----------------------------

I tried the same code with axis2-1.6.1 version but not sure if it resolves the 
issue as the problem cannot be reproduced in test environment. It can be 
checked when it goes live next time.

The steps for the code are -
1) receives the request
2) creates a thread
3) creates client stub
4) calls the method of server using client stub.(the framework internally 
processes the request and cleans the transport) 

The above steps are done for the thousands of requests received.
                
> org.apache.commons.httpclient.ConnectionPoolTimeoutException: Timeout waiting 
> for connection
> --------------------------------------------------------------------------------------------
>
>                 Key: AXIS2-5251
>                 URL: https://issues.apache.org/jira/browse/AXIS2-5251
>             Project: Axis2
>          Issue Type: Bug
>          Components: transports
>    Affects Versions: 1.5.5
>         Environment: Solaris,UNIX,Java
>            Reporter: TEST
>            Priority: Critical
>              Labels: performance
>         Attachments: getCustomer_autogeneratedcode.rtf, getCustomer_client.rtf
>
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> The client stub was working perfectly fine with lower load/requests. The same 
> application when went live failed, giving some successful responses and some 
> " Timeout waiting for connection" exceptions with heavy load/requests.
> The axis version used is axis2-1.5.5
> Please find the exception below -
> Feb 23, 2012 1:10:11 AM org.apache.axis2.transport.http.HTTPSender sendViaPost
> INFO: Unable to sendViaPost to url[http://97.16.143.78:8080/ua/soap]
> org.apache.commons.httpclient.ConnectionPoolTimeoutException: Timeout waiting 
> for connection
>         at 
> org.apache.commons.httpclient.MultiThreadedHttpConnectionManager.doGetConnection(MultiThreadedHttpConnectionManage
> r.java:497)
>         at 
> org.apache.commons.httpclient.MultiThreadedHttpConnectionManager.getConnectionWithTimeout(MultiThreadedHttpConnect
> ionManager.java:416)
>         at 
> org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:153)
>         at 
> org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:397)
>         at 
> org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:346)
>         at 
> org.apache.axis2.transport.http.AbstractHTTPSender.executeMethod(AbstractHTTPSender.java:557)
>         at 
> org.apache.axis2.transport.http.HTTPSender.sendViaPost(HTTPSender.java:199)
>         at org.apache.axis2.transport.http.HTTPSender.send(HTTPSender.java:76)
>         at 
> org.apache.axis2.transport.http.CommonsHTTPTransportSender.writeMessageWithCommons(CommonsHTTPTransportSender.java
> :400)
>         at 
> org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(CommonsHTTPTransportSender.java:225)
>         at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:438)
>         at 
> org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:402)
>         at 
> org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:229)
>         at 
> org.apache.axis2.client.OperationClient.execute(OperationClient.java:165)
>         at 
> org.apache.axis2.axis2userguide.QuantumUAStub.getSubscriber(QuantumUAStub.java:1340)
>         at 
> org.apache.axis2.axis2userguide.SOExecutionThread.getCustomer(AAA_Broadhop.java:1070)
>         at 
> org.apache.axis2.axis2userguide.SOExecutionThread.run(AAA_Broadhop.java:3446)
>         at java.lang.Thread.run(Thread.java:595)
> According to me, the above exception is taken care in the original base code 
> generated with wsdl file. The code is pasted below which should take care the 
> cleanup of the transport ( http sessions) but it is not as I am getting some 
> "Timeout waiting for connection" exceptions.
> finally {
>                 if (_messageContext.getTransportOut() != null) {
>                       
> _messageContext.getTransportOut().getSender().cleanup(_messageContext);
>                 }
> Can you please suggest what is going wrong here.
> The code uses thread mechanism for each request. The code is attached for 
> your reference.
> Let me know if more information is required.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to