Hi
        Just guessing here, but can you fetch the document and all the
urls in it from the machine that's having the timeout? Maybe you can in
your browser, but it might be going through a proxy: you could write a
simple java program to fetch them all. Xerces doesn't do anything
particularly special when it fetches documents, so I'd guess the timeout
issue is something more basic -- like you can't access the URL.


        Chris


-----Original Message-----
From: Ramya Manian [mailto:[EMAIL PROTECTED] 
Sent: Thursday, July 01, 2004 03:34
To: [EMAIL PROTECTED]
Subject: Urgent: "Read timed out" error while parsing the XML response

Hi

We have a SOAP client and server. The SOAP utility used in the client
internally uses Xerces to parse the response.

But the client throws a Socketexception: "Read timed out" error while
parsing the response from the server.

I tried increasing the timeout settings for the connection but but it
did not work.
The complete data is received properly at client side.

After debugging, it was realised that the error occurs while trying to
get the document version in the XML response which is included below.

Any pointers on why is this occurring will be very helpful?

Thanks
Ramya

RESPONSE
----------
HTTP/1.1 200 OK
Accept: application/soap+xml, application/dime, multipart/related,
text/*
Cache-Control: no-cache
Content-Type: text/xml; charset="UTF-8"
Host: 127.0.0.1
Pragma: no-cache
User-Agent: MyAgentSrv
Content-Length: 728

<?xml version="1.0" encoding="UTF-8"?>
   <E:Envelope xmlns:E="http://schemas.xmlsoap.org/soap/envelope/";
xmlns:A="http://schemas.xmlsoap.org/soap/encoding/";
xmlns:s="http://www.w3.org/2001/XMLSchema-instance";
xmlns:y="http://www.w3.org/2001/XMLSchema";
E:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/";>
      <E:Body>
         <m:ConnectResponse xmlns:m="http://www.PData.com/MyAgent";>
            <m:id s:type="y:int">6</m:id>
            <m:result>
               <m:resultCode s:type="y:int">0</m:resultCode>
               <m:errorCode s:type="y:int">0</m:errorCode>
               <m:errorMessage s:type="y:string"></m:errorMessage>
               <m:diagonsticMessage
s:type="y:string"></m:diagonsticMessage>
               <m:size s:type="y:int">0</m:size>
            </m:result>
         </m:ConnectResponse>
      </E:Body>
   </E:Envelope>


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

Reply via email to