Hi, http://developers.sun.com/mobility/midp/questions/chunking/
I've also been thinking trying Http 1.0 might solve this (same with the properties I think). Either that or IIS 5.5 does not support persistent connections? Like you the issue is solved but I am not happy about the workarounds and am still digging around on the issue. Note that IIS 6.0 seems happy without chunking and http keep alives - since I imagine all our production servers will use Windows 2003 its not the most urgent issue I have right now. Jira - is the bug tracking system. I guess if we can make a small project that demonstrates the problem we could submit it to Axis as a bug. I just think this should work without all the IIS tinkering required...I'll look at this. HTH Tim -----Original Message----- From: Jan Verstuyft [mailto:[EMAIL PROTECTED] Sent: Monday, June 23, 2008 10:43 AM To: [email protected] Subject: Re: [Axis2] - Software caused connection abort: recv failed Thanks Tim, that seems to work with the chunk disabled. What is the advantage/disadvantage of this? What about the Jira? I don't know what you mean. I'm a newbie at Axis and Axis2. Kind regards Jan 2008/6/23 Tim James McConechy <[EMAIL PROTECTED]>: > Hi, > Not entirely sure about this: > > 1) I still get the http 100 messages - I don't think they are a problem > - you might want to keep looking for other http errors.. > 2) Try to disable chunking since the message mentions that... > > > WebServiceManager.generalServiceObject=new WsDataObjectStub(); > > WebServiceManager.generalServiceObject._getServiceClient().getOptionsz). > setProperty(HTTPConstants.CHUNKED, "false"); > > 3) Did you try to switch off the http keep alives? > > I really think there is a bug in here somewhere because it did not cause > these problems in Axis 1.4, maybe between the two of us we can workout a > Jira for this issue. > > Thanks > Tim > > > -----Original Message----- > From: Jan Verstuyft [mailto:[EMAIL PROTECTED] > Sent: Monday, June 23, 2008 7:51 AM > To: [email protected] > Subject: Re: [Axis2] - Software caused connection abort: recv failed > > Thanks Tim for the feedback. > > I've tried this, and it was very strange. I've tried it with a couple > different TCP/IP Monitors. > > Tcpmon gave a soap request, but won't work for either Java or C#. > BurpSuite gave a soaprequest, still works for C# but won't work for > Java, but also not for my development server. so still no comparison > to make. > > With the builtin TCP/IP Monitor of Eclipse (thanks Tim, because I > didn't know that eclipse had one) I was finally able to reproduce the > problems. > > For a working request (from C#) I've got the following request and > response: > POST /Services/services/SessionService HTTP/1.1 > User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; MS Web Services Client > Protocol 2.0.50727.1433) > VsDebuggerCausalityData: > uIDPo8FRiJt6dApCgLnnU6wYfaUAAAAAkjB0NmjdRUGJqMp9Kl5++Hl/4ih23iRFpjSeSp/J > cOEACAAA > Content-Type: text/xml; charset=utf-8 > SOAPAction: "urn:login" > Host: stg.websrv.eu.sony.com > Content-Length: 360 > Expect: 100-continue > Connection: Keep-Alive > <?xml version="1.0" encoding="utf-8"?> > <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"; > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; > xmlns:xsd="http://www.w3.org/2001/XMLSchema";> > <soap:Body> > <login xmlns="http://session.ws.ideal.com";> > <username>id_hemmsync</username> > <password>myhemmsync</password> > </login> > </soap:Body> > </soap:Envelope> > > > And a wrong request (from Java) as follow: > POST /Services/services/SessionService HTTP/1.1 > Content-Type: application/soap+xml; charset=UTF-8; action="urn:login" > User-Agent: Axis2 > Host: stg.websrv.eu.sony.com > Transfer-Encoding: chunked > > > > > Ok, I see that the message is not complete, but with some of the other > tcp/ip monitors it gave me a complete soap message > > Can somebody helps? > > Kind regards > Jan Verstuyft > > > > > 2008/6/20 Tim James McConechy <[EMAIL PROTECTED]>: >> Hi Jan, >> I went through this recently. In my case there was also other errors > happening before this occured. Specifically "403 transport error". >> To resolve it I used some instructions from here to look into > tcpmonitor: >> >> 1. Goto window->show view->other in eclipse >> 2. Search for TCP and you will find TCP/IP Monitor >> 3. Right click->properties >> 4. click add >> 5. Set local monitoring port to 8080, host name (The place where the > service is at, if its running locally localhost), port (the port which > the service is running on) >> 6. Configure your client to send the request to the TCP monitor > instead of the actual service (for e.g localhost:8080) by changing > plm.properties to: >> url.dataobjects=http://localhost:8080/FsSvcCore/DataObjects/ and the > TCP monitor will forward it to the actual service. You will see the > message on the TCP monitor. >> >> I found out the error was HTTP 403.9 - Access Forbidden: Too many > users are connected. Which was helpful to solve that I did this: >> >> o Open IIS console >> o Right click on Default Web Service - Properties >> o Uncheck "Http Keep-Alives Enabled" >> >> But now I am getting some other errors in my C# client to resolve. I > am going to now try upping the users >> >> http://www.dslreports.com/faq/10253 >> >> At least that should get you to the right error message if not solve > the issue. Not that it seems this problem only occurs running ISS on > windows XP as there is some sort of a ten user limit and the Axis2 > services seem to hammer the server asyncronously and exceed that > limit...Another choice is to run IIS 6 on a Windows 2003 server where I > did not see this problem... >> >> Regards >> Tim >> >> >> -----Original Message----- >> From: Jan Verstuyft [mailto:[EMAIL PROTECTED] >> Sent: Fri 6/20/2008 4:15 AM >> To: [email protected] >> Subject: [Axis2] - Software caused connection abort: recv failed >> >> Hi, >> >> I've created a webservice that works fine on our development >> environment. When we deploy it to a staging environment I can connect >> to my webservice with a C# client. But when I create the stub by the >> Axis2 framework for Java, I get the error below. >> If I create the same stubs for the webservice at my development >> environment, everything works fine. >> >> The infrastructure is like this: >> The development Web application Server is a WebLogic that is running >> on my local machine. >> >> For the staging environment we have 2 Weblogic Instance that are >> behind an Apache that deals with a load balancing. The address I >> receive is off course the address of the Apache. >> >> Can you please help? >> >> Jan Verstuyft >> >> >> org.apache.axis2.AxisFault: Software caused connection abort: recv > failed >> at org.apache.axis2.AxisFault.makeFault(AxisFault.java:430) >> at > org.apache.axis2.transport.http.HTTPSender.sendViaPost(HTTPSender.java:1 > 93) >> at > org.apache.axis2.transport.http.HTTPSender.send(HTTPSender.java:75) >> at > org.apache.axis2.transport.http.CommonsHTTPTransportSender.writeMessageW > ithCommons(CommonsHTTPTransportSender.java:364) >> at > org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(Common > sHTTPTransportSender.java:208) >> at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:448) >> at > org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOper > ation.java:401) >> at > org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInA > xisOperation.java:228) >> at > org.apache.axis2.client.OperationClient.execute(OperationClient.java:163 > ) >> at > com.ideal.ws.session.SessionServiceStub.login(SessionServiceStub.java:19 > 2) >> at TestService.main(TestService.java:23) >> Caused by: java.net.SocketException: Software caused connection abort: >> recv failed >> at java.net.SocketInputStream.socketRead0(Native Method) >> at java.net.SocketInputStream.read(SocketInputStream.java:129) >> at java.io.BufferedInputStream.fill(BufferedInputStream.java:183) >> at java.io.BufferedInputStream.read(BufferedInputStream.java:201) >> 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.jav > a:1116) >> at > org.apache.commons.httpclient.MultiThreadedHttpConnectionManager$HttpCon > nectionAdapter.readLine(MultiThreadedHttpConnectionManager.java:1413) >> at > org.apache.commons.httpclient.HttpMethodBase.readStatusLine(HttpMethodBa > se.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(HttpMe > thodDirector.java:398) >> at > org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMetho > dDirector.java:171) >> at > org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:3 > 97) >> at > org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:3 > 46) >> at > org.apache.axis2.transport.http.AbstractHTTPSender.executeMethod(Abstrac > tHTTPSender.java:542) >> at > org.apache.axis2.transport.http.HTTPSender.sendViaPost(HTTPSender.java:1 > 89) >> ... 9 more >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
