[jira] Updated: (AXIS-1253) Posting large SOAP requests (4MB) to WLS fails with java.net.SocketException: Software caused connection abort: socket write error

[ji...@apache.org]

The following issue has been updated:

    Updater: Danno Ferrin (mailto:shemnon@yahoo.com)
       Date: Fri, 12 Mar 2004 7:33 AM
    Comment:
The problem is that the socket is created and opened, then the soap message is calculated, then the post is made.  This can take several seconds and WLS is quite imatiant WRT starting the HTTP request.  By delaying the creation of the socket to after we make the message the socket is used immediatle.

I use a single item array to work as a C++ style references since something is already being returned from writeToSocket.
    Changes:
             Attachment changed to diffLarge.txt
    ---------------------------------------------------------------------
For a full history of the issue, see:

  http://issues.apache.org/jira/secure/ViewIssue.jspa?key=AXIS-1253&page=history

---------------------------------------------------------------------
View the issue:
  http://issues.apache.org/jira/secure/ViewIssue.jspa?key=AXIS-1253

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: AXIS-1253
    Summary: Posting large SOAP requests (4MB) to WLS fails with java.net.SocketException: Software caused connection abort: socket write error
       Type: Bug

     Status: Unassigned
   Priority: Critical

    Project: Axis
   Versions:
             current (nightly)

   Assignee: 
   Reporter: Danno Ferrin

    Created: Fri, 12 Mar 2004 7:30 AM
    Updated: Fri, 12 Mar 2004 7:33 AM
Environment: Windows XP SP1, (client) J2SE1.4.2_04, (server) Weblogic 6.1 SP4, one WSDL request with one xsd:string field of about 4MB in length.  Client and Server cannot be same machine, i.e. network cables must be involved.

Description:
When posing a soap request that is large in size (4MB total wire size) and hosting the Axis servlet inside of weblogic 6.1 SP4 after a few second or so the post fails with 

SEVERE: java.io.IOException:
java.net.SocketException: Software caused connection abort: socket write error
	at java.net.SocketOutputStream.socketWrite0(Native Method)
	at java.net.SocketOutputStream.socketWrite(Unknown Source)
	at java.net.SocketOutputStream.write(Unknown Source)
	at java.io.BufferedOutputStream.write(Unknown Source)
	at sun.nio.cs.StreamEncoder$CharsetSE.writeBytes(Unknown Source)
	at sun.nio.cs.StreamEncoder$CharsetSE.implWrite(Unknown Source)
	at sun.nio.cs.StreamEncoder.write(Unknown Source)
	at java.io.OutputStreamWriter.write(Unknown Source)
	at java.io.BufferedWriter.flushBuffer(Unknown Source)
	at java.io.BufferedWriter.write(Unknown Source)
	at java.io.Writer.write(Unknown Source)
	at org.apache.axis.SOAPPart.writeTo(SOAPPart.java:313)
	at org.apache.axis.Message.writeTo(Message.java:548)
	at org.apache.axis.transport.http.HTTPSender.writeToSocket(HTTPSender.java:465)
	at org.apache.axis.transport.http.HTTPSender.invoke(HTTPSender.java:128)
	at org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.java:71)
	at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:157)
	at org.apache.axis.SimpleChain.invoke(SimpleChain.java:122)
	at org.apache.axis.client.AxisClient.invoke(AxisClient.java:183)
	at org.apache.axis.client.Call.invokeEngine(Call.java:2682)
	at org.apache.axis.client.Call.invoke(Call.java:2665)
	at org.apache.axis.client.Call.invoke(Call.java:2355)
	at org.apache.axis.client.Call.invoke(Call.java:2278)
	at org.apache.axis.client.Call.invoke(Call.java:1777)
	[snip... WSDL2Java generated clall stubs ...snip]

This is based on a CVS build from on or about 25 Feb for the line numbers, pre 2.0 license renaming.

Patch to follow


---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira