[ 
https://issues.apache.org/jira/browse/AXIS2-4705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Bheemeswara Rao Amruthavakkula closed AXIS2-4705.
-------------------------------------------------


Hi All

My issue resolved. Connection reset error may appear for any reasons that makes 
connection timed out or there is a problem wih the connection once the 
connection established between client and server.

In my case the issue is due to the session loss on the Citrix load balance once 
the initial connection been established. We resolved this issue by making the 
sessions persistant on the load balancer.

> connection reset problem with jave.net.socketexception when trying to access 
> a web service using a domain name.
> ---------------------------------------------------------------------------------------------------------------
>
>                 Key: AXIS2-4705
>                 URL: https://issues.apache.org/jira/browse/AXIS2-4705
>             Project: Axis2
>          Issue Type: Bug
>          Components: admin console, client-api, deployment, Tools, wsdl
>    Affects Versions: 1.4.1, 1.4
>         Environment: jdk1.5 axis1.4 websphere 6.1
>            Reporter: Bheemeswara Rao Amruthavakkula
>            Priority: Blocker
>         Attachments: axis2.xml, MichaelsTransaction.wsdl
>
>
> Hi All
> facing issues while accessing my webservice over a firewall server where our 
> domain name is configured. I have created webservice and client using eclipse 
> plug-in code generator. I am able to access webservice using server name or 
> the ip address such as TransactionProcessor 
> (http://ecwstest:80/axis2/services/TransactionProcessor). Same service is 
> giving us problems when trying to access using domain name instread which is 
> configured over a firewall such as 
> (http://wwwtest.michaels.com:80/axis2/services/TransactionProcessor). We are 
> struggling this issue for fast few days. Any help will be highly appreciated. 
> find client code and exception I am getting below. attached are axis2.xml, 
> wsdl file and services.xml
> Recently analyzed the logs and found that the request is hitting web server 
> but not the app server. In the working scenario it is generating logs on 
> Application server, but in the other scenario we are not seing any trace in 
> websphere logs.
> client side code: 
>   TransactionProcessorStub stub;
>                 
>                 
>                 
>           //stub = new 
> TransactionProcessorStub("http://wwwtest.michaels.com:80/axis2/services/TransactionProcessor";);
>           //stub = new 
> TransactionProcessorStub("http://wwwtest1.michaels.com";);
>           //stub = new 
> TransactionProcessorStub("http://ecwstest/axis2/services/TransactionProcessor";);
>           stub = new 
> TransactionProcessorStub("http://ecwstest:80/axis2/services/TransactionProcessor";);
>           TransactionProcessorStub.RunTransaction df = new 
> TransactionProcessorStub.RunTransaction();
>           df.setInputMessageIn(textXml); 
>           TransactionProcessorStub.RunTransactionResponse res = 
> stub.runTransaction(df);  
>           System.out.println("response value : " +res.get_return());
> exception: 
> org.apache.axis2.AxisFault: Connection reset
>       at org.apache.axis2.AxisFault.makeFault(AxisFault.java:430)
>       at 
> org.apache.axis2.transport.http.HTTPSender.sendViaPost(HTTPSender.java:193)
>       at org.apache.axis2.transport.http.HTTPSender.send(HTTPSender.java:75)
>       at 
> org.apache.axis2.transport.http.CommonsHTTPTransportSender.writeMessageWithCommons(CommonsHTTPTransportSender.java:364)
>       at 
> org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(CommonsHTTPTransportSender.java:208)
>       at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:448)
>       at 
> org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:401)
>       at 
> org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:228)
>       at 
> org.apache.axis2.client.OperationClient.execute(OperationClient.java:163)
>       at 
> com.michaels.commerce.client.online.shopping.TransactionProcessorStub.runTransaction(TransactionProcessorStub.java:198)
>       at 
> com.michaels.commerce.client.online.shopping.RealStub.main(RealStub.java:119)
> Caused by: java.net.SocketException: Connection reset
>       at java.net.SocketInputStream.read(SocketInputStream.java:168)
>       at java.io.BufferedInputStream.fill(BufferedInputStream.java:218)
>       at java.io.BufferedInputStream.read(BufferedInputStream.java:237)
>       at 
> org.apache.commons.httpclient.HttpParser.readRawLine(HttpParser.java:78)
>       at 
> org.apache.commons.httpclient.HttpParser.readLine(HttpParser.java:106)
>       at 
> org.apache.commons.httpclient.HttpConnection.readLine(HttpConnection.java:1116)
>       at 
> org.apache.commons.httpclient.MultiThreadedHttpConnectionManager$HttpConnectionAdapter.readLine(MultiThreadedHttpConnectionManager.java:1413)
>       at 
> org.apache.commons.httpclient.HttpMethodBase.readStatusLine(HttpMethodBase.java:1973)
>       at 
> org.apache.commons.httpclient.HttpMethodBase.readResponse(HttpMethodBase.java:1735)
>       at 
> org.apache.commons.httpclient.HttpMethodBase.execute(HttpMethodBase.java:1098)
>       at 
> org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(HttpMethodDirector.java:398)
>       at 
> org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:171)
>       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:542)
>       at 
> org.apache.axis2.transport.http.HTTPSender.sendViaPost(HTTPSender.java:189)
>       ... 9 more

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