You are viewing a plain text version of this content. The canonical link for it is here.
Posted to soap-user@ws.apache.org by Tatsuya Tsurukawa <tu...@isl.melco.co.jp> on 2002/07/02 02:02:59 UTC
call.invoke() doesn't return in case of using TcpTunnelGui
Hi All,
I'm now in trouble that if I launch a soap client program like hello
sample with monitoring soap messages by TcpTunnelGui, it doesn't
return for ever, although TcpTunnelGui shows proper send and receive
messages.
It returns immediately without TcpTunnelGui, of course.
In detai, I also found call.invoke() in the client doesn't return in
case of using TcpTunnelGui.
I'm using JDK 1.3.1, apache-soap 2.3.1 and tomcat 3.2.3 on Red Hat
Linux 7.2.
Does anybody know that ? Are there any work arounds ?
Any comments would be appreciated.
Best regards,
Tatsuya Tsurukawa
----
Tatsuya turukawa@isl.melco.co.jp
Re: call.invoke() doesn't return in case of using TcpTunnelGui
Posted by Fred Meredith <fm...@nc.rr.com>.
I have seen the problem you are describing on an identical setup. The
method will return, although it will be several minutes for it to do so. I
did not explore any workarounds to fix the situation because the
TcpTunnelGui is, in of itself, just a tool. Once the application has been
debugged and the messages are being sent and received as expected, why worry
about a tool causing a delay in the response of a method invocation?
Just a thought,
----- Original Message -----
From: "Tatsuya Tsurukawa" <tu...@isl.melco.co.jp>
To: <so...@xml.apache.org>
Sent: Monday, July 01, 2002 8:02 PM
Subject: call.invoke() doesn't return in case of using TcpTunnelGui
> Hi All,
>
> I'm now in trouble that if I launch a soap client program like hello
> sample with monitoring soap messages by TcpTunnelGui, it doesn't
> return for ever, although TcpTunnelGui shows proper send and receive
> messages.
>
> It returns immediately without TcpTunnelGui, of course.
>
> In detai, I also found call.invoke() in the client doesn't return in
> case of using TcpTunnelGui.
>
> I'm using JDK 1.3.1, apache-soap 2.3.1 and tomcat 3.2.3 on Red Hat
> Linux 7.2.
>
> Does anybody know that ? Are there any work arounds ?
> Any comments would be appreciated.
>
> Best regards,
> Tatsuya Tsurukawa
>
> ----
> Tatsuya turukawa@isl.melco.co.jp
>
> --
> To unsubscribe, e-mail: <ma...@xml.apache.org>
> For additional commands, e-mail: <ma...@xml.apache.org>
>
Re: call.invoke() doesn't return in case of using TcpTunnelGui
Posted by Fred Meredith <fm...@nc.rr.com>.
I have seen the problem you are describing on an identical setup. The
method will return, although it will be several minutes for it to do so. I
did not explore any workarounds to fix the situation because the
TcpTunnelGui is, in of itself, just a tool. Once the application has been
debugged and the messages are being sent and received as expected, why worry
about a tool causing a delay in the response of a method invocation?
Just a thought,
----- Original Message -----
From: "Tatsuya Tsurukawa" <tu...@isl.melco.co.jp>
To: <so...@xml.apache.org>
Sent: Monday, July 01, 2002 8:02 PM
Subject: call.invoke() doesn't return in case of using TcpTunnelGui
> Hi All,
>
> I'm now in trouble that if I launch a soap client program like hello
> sample with monitoring soap messages by TcpTunnelGui, it doesn't
> return for ever, although TcpTunnelGui shows proper send and receive
> messages.
>
> It returns immediately without TcpTunnelGui, of course.
>
> In detai, I also found call.invoke() in the client doesn't return in
> case of using TcpTunnelGui.
>
> I'm using JDK 1.3.1, apache-soap 2.3.1 and tomcat 3.2.3 on Red Hat
> Linux 7.2.
>
> Does anybody know that ? Are there any work arounds ?
> Any comments would be appreciated.
>
> Best regards,
> Tatsuya Tsurukawa
>
> ----
> Tatsuya turukawa@isl.melco.co.jp
>
> --
> To unsubscribe, e-mail: <ma...@xml.apache.org>
> For additional commands, e-mail: <ma...@xml.apache.org>
>
--
To unsubscribe, e-mail: <ma...@xml.apache.org>
For additional commands, e-mail: <ma...@xml.apache.org>