In regards to : "Tripple check your client and TcpTunnel setup. I've seen problems with TcpTunnel not flushing output to a waiting client" ... I have that exact problem! My SOAP client gets hung in call.invoke() even though I see the normal req/resp msgs in the tcp tunnel gui... How do I get or configure TCPTunnelGui to flush the response on the line, so that my SOAP client can get returned from call.invoke() ??? Anyone know? Paula Young -----Original Message----- From: Irfan Mohammed [mailto:[EMAIL PROTECTED]] Sent: Thursday, July 26, 2001 7:01 PM To: '[EMAIL PROTECTED]' Subject: RE: XML error while invoking a service Yeah, this is surely strange....it looks like when i talk directly from the client to the rpcrouter the http header being sent is messed up. The request doesn't even get past the web server on the server machine. However when i use the tcptunnel it works fine. I don't know if its a jvm issue over how the http headers are sent. To overcome this problem im sending all service requests to a proxy server on my machine which then forwards it to the rpcrouter. This works fine..but this is a bad fix. Any knows why this may be happening. I have jdk1.3.02, websphere3.5.4, ibm http server, soap2.2 Irfan -----Original Message----- From: Jim Hazen [mailto:[EMAIL PROTECTED]] Sent: Thursday, July 26, 2001 3:01 PM To: [EMAIL PROTECTED] Subject: Re: XML error while invoking a service Tripple check your client and TcpTunnel setup. I've seen problems with TcpTunnel not flushing output to a waiting client, but never seen things work via TcpTunnel and not work on a regular client. There has always been a misconfiguration in either the TcpTunnel or the client. So make sure your TcpTunnel is pointing to your new server, make sure the client is also pointing to this new server on the same port, etc. -Jim > Jim, > > When I invoke the service through the TcpTunnel it works fine, however when > I invoke the service directly from my client, it fails. Im not sure why > this is happening. Any clues on this. > > Thanks > Irfan
