Paul:

When I ran the same xmlrpc.jar on NT, I got the same output on webserver as
yours. 

Also I am getting the socket exception on client (NT again) which causes the
webserver to refuse any new connection.  The exception is:
java.net.SocketException: Connection reset by peer: JVM_recv in socket input
stream read.

I am using the XmlRpcClientLite in this case.

What could have caused this SocketException and how to avoid this problem?

Thanks.

- Yaxiong


> -----Original Message-----
> From: Paul Libbrecht [SMTP:[EMAIL PROTECTED]]
> Sent: Tuesday, March 19, 2002 2:17 AM
> To:   [EMAIL PROTECTED]
> Subject:      Re: connection refused error
> 
> Yaxiong,
> 
> I finally made the test with XmlRpcClientLite (thanks to BeanShell) 
> and... I get a completely different one:
> 
> > Accepted connection.
> > POST /aPath HTTP/1.0
> > User-Agent: Apache XML-RPC 1.0
> > Host: localhost:1037
> > Content-Type: text/xml
> > Content-Length: 95
> 
> 
> This makes me believe that your jar may be corrupted...
> Have you tried downloading another one ??
> 
> Paul
> 
> 
> On Lundi, mars 18, 2002, at 11:20 , Lin, Yaxiong wrote:
> 
> >
> > Paul:
> >
> > Thanks for much for giving the code as well to do my debugging!!!
> >
> > I don't know how to interpret the output as they are drastically 
> > different.
> > The first set of the output was sent by XmlRpcClientLite and the second 
> > set
> > was sent by the XmlRpcClient.
> >
> > It looks like the packet sent by XmlRpcClientLite does not have the 
> > header!
> >
> > Thanks.
> >
> > - Yaxiong

Reply via email to