HTTP Protocol error occurs

[Mikio Satsukawa <sa...@ysp.co.jp>]

Hi all,
(from Japan, sorry for my poor English.)

I have a problem on the following environment.

Client: VB.NET on WIN2000
Server: WIN2000 + IBM HTTP Server + IBM WebSphere4.0.4 + Axis1.0
Network: LAN 100M

I often get an error message of "Basic connection closed. HTTP Protocol
violation."(the actual message is Japanese) on after getting the
response from Axis.
This message is issued from .NET Framework where is
System.Web.Services.Protocols.WebClientProtocol.GetWebResponse method.

The following is the TCP trace in case of this error.

******************** TCP MON output starts ********************
HTTP/1.1 200 OK
Server: WebSphere Application Server/4.0
Content-Type: text/xml; charset=utf-8
Content-Language: ja
Transfer-Encoding: chunked

771
<?xml version="1.0" encoding="UTF-8"?>
<soapenv:Envelope 
         xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" 
         xmlns:xsd="http://www.w3.org/2001/XMLSchema"
         xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
 <soapenv:Body>
  <ns1:getLeavesResponse 
        soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
        xmlns:ns1="http://maui/AxisV1/services/WWUYCLeafEditApp">
   <getLeavesReturn href="#id0"/>
  </ns1:getLeavesResponse>
  <multiRef id="id0" soapenc:root="0" 
       soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
       xsi:type="ns2:WWUYCLeavesResult"
       xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
       xmlns:ns2="urn:result.wwuy.wwux">
   <arLeaves xsi:type="soapenc:Array" 
       soapenc:arrayType="ns3:WWUYCLeafHeader[1]"
       xmlns:ns3="urn:container.wwuy.wwux">
    <item href="#id1"/>
   </arLeaves>
   <retMsg xsi:type="xsd:string" xsi:nil="true"/>
   <retCode xsi:type="xsd:string">OK</retCode>
  </multiRef>
  <multiRef id="id1" soapenc:root="0" 
       soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
       xsi:type="ns4:WWUYCLeafHeader" xmlns:ns4="urn:container.wwuy.wwux"
       xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/">
   <lock_Status xsi:type="xsd:boolean">false</lock_Status>
   <lock_User_Nm xsi:type="xsd:string" xsi:nil="true"/>
   <editable xsi:type="xsd:boolean">false</editable>
   <no_OrderLeaf xsi:type="xsd:string">0</no_OrderLeaf>
   <lock_User_Id xsi:type="xsd:string" xsi:nil="true"/>
   <status xsi:type="xsd:string" xsi:nil="true"/>
   <leaf_Id xsi:type="xsd:string">11100024</leaf_Id>
   <version xsi:type="xsd:string">1 </version>
   <nm_Leaf xsi:type="xsd:string"></nm_Leaf>
   <revision xsi:type="xsd:string">1 </revision>
   <upd_Date xsi:type="xsd:string" xsi:nil="true"/>
   <upd_Time xsi:type="xsd:string" xsi:nil="true"/>
   <root_Id xsi:type="xsd:string">11100024JA0100</root_Id>
  </multiRef>
 </soapenv:Body>
</soapenv:Envelope>
0

0
******************** TCP MON output ends ********************
Like this, SOAP response itself is OK.
I have a thing on my chest.
In case of working well, TCP MON trace ends "</soapenv:Envelope> 0".
But otherwise, it ends "</soapenv:Envelope> 0  0" like above.
I have no idea about "0" and the number(length?) before XML header. 
Who puts this numbers in the http response?

We have 2 server environments, our company's and our customer's, then
above error occurs on our company's env only.
Both configurations are basically same, 
ex. WebSphere version, XML processor,..
and still, client PC(note) is shared so I think no problem in 
the client PC.
LAN, or other factor of server causes this?

Please give me any hints or related information.

Thanks.

Mikio