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

Chris commented on AXIS2-1473:
------------------------------

I have a work-around for the problem with a change to the 
org.apache.axis2.transport.http.AbstractHTTPSender class in 
axis2-kernel-1.2.jar. 

At the end of the getHttpClient method, before the   return httpClient; 
statement I have inserted the following:


        HttpMethodRetryHandler myretryhandler = new HttpMethodRetryHandler() {
          public boolean retryMethod(
              final HttpMethod method, 
              final IOException exception, 
              int executionCount) {
              if (executionCount >= 5) {
                  // Do not retry if over max retry count
                  return false;
              }
              if (exception instanceof SocketException) {
                log.warn("retry " + executionCount +" after 
SocketException",exception);
//              Retry if the server dropped connection on us
                return true;
              }
              
              
              if (exception instanceof NoHttpResponseException) {
                  // Retry if the server dropped connection on us
                  return true;
              }
              if (!method.isRequestSent()) {
                  // Retry if the request has not been sent fully or
                  // if it's OK to retry methods that have been sent
                  return true;
              }
              
              
              // otherwise do not retry
              return false;
          }
      };
      
      httpClient.getParams().
      setParameter(HttpMethodParams.RETRY_HANDLER, myretryhandler);

I am not familiar with the intenals of axis so I do not know if there is a 
better way of doing this, and do not know how to make it a settable 
configuration parameter. I will attach my changed source file and patched jar 
file for others to try.

> org.apache.axis2.AxisFault: Connection reset - connections are not closing 
> for long time
> ----------------------------------------------------------------------------------------
>
>                 Key: AXIS2-1473
>                 URL: https://issues.apache.org/jira/browse/AXIS2-1473
>             Project: Axis 2.0 (Axis2)
>          Issue Type: Bug
>          Components: client-api, codegen
>    Affects Versions: nightly
>         Environment: Client in Windows XP SP2, jdk 1.5, Axis2 1.1 Nightly 
> build(October 20, 2006), Microsoft SQL Reporting Services 2005 in Windows XP, 
> JVM Heap settings : -Xrs -Xmx700M -Xms512M.., Memory :1 GB
>            Reporter: GNANASEKARAN VINAYAKAMURTHY
>         Assigned To: Deepal Jayasinghe
>            Priority: Critical
>         Attachments: Connection-reset-exeption.txt, netstat-output.doc, 
> reportexecution2005.wsdl, reportservice2005.wsdl, SSRS-Main.zip
>
>
> Getting connection reset problem in Axis2 1.1 Nightly, when I try to make web 
> service calls to .Net client (MS Reporting services in XP) again and 
> again.... But it works fine when called at initial couple of times... I think 
> system breaks, when we make web service call at 5th consecutive time. 
> I am trying to create web application with axis2, where I could show all the 
> reports and folders from MS reporting services.
> Axis2 client and .Net web service server(MS Reporting services) are running 
> on windows platform and I just tried using 'netstat -a' in the system, where 
> my Axis2 client is running and  found that connections made by Axis2 were not 
> closing for long time...... I think Axis2 is not closing the socket 
> connections after end of web service calls in client side.
> I have also attached the following with this,
> 1. Netstat output
> 2. Exception stack trace
> 3. wsdl files
> 4. Source code
> Please let me know about how could we close connections completely from Axis2 
> or how to fix this?
> Thanks,

-- 
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]

Reply via email to