The error indicates that the server closed the connection without 
even sending an HTTP status message.  I am not sure what would cause 
this, as Tomcat usually catches errors that occur in servlets and 
returns information about them to the client.  The only things I can 
suggest are to check the Tomcat error logs, and if nothing is found 
there, turn on some Tomcat debug (although I am not sure what debug 
is available in version 3.2.3).

On 21 Jan 2003 at 17:38, Antonino Galletta wrote:

> Dear all,
> 
> I used the Apache-Soap 2.2 with TOMCAT Version 3.2.3 to develop a
> distribuited application over many european country.
> The norvegian client application raises the following exception:
> 
> Caught SOAPException (SOAP-ENV:Client): Error parsing HTTP status line "":
> java.util.NoSuchElementException
> [SOAPException: faultCode=SOAP-ENV:Client; msg=Error parsing HTTP status
> line "": java.util.NoSuchElementException; targ
> etException=java.lang.IllegalArgumentException: Error parsing HTTP status
> line "": java.util.NoSuchElementException]
>         at
> org.apache.soap.transport.http.SOAPHTTPConnection.send(SOAPHTTPConnection.ja
> va:324)
>         at org.apache.soap.rpc.Call.invoke(Call.java:205)
>         at
> com.Alenia.rtp1113.wp8.SoapHandler.soapOrb.ProxySoap.invoke(ProxySoap.java:1
> 84)
> 
> Can somebody help me ?
> 
> Many thanks
> Antonino Galletta
> 
> 
> --
> To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
> 
> 


Scott Nichol


--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to