I am still confused with the usage of the tool. Can anybody show me a worked
example? Please let me know the details, like:

1. what you type in the command line on your monitoring machine?
2. what is needed to be running on your monitoring machine except soap.jar?
3. what url you specify in your SOAP client, like
http://localhost:8888/soap/servlet/rpcrouter or http://localhost:8888?
because the port number 8888 is an randomly selected, will
http://localhost:8888/soap/servlet/rpcrouter work?

Rufeng

-----Original Message-----
From: Mark Childerson [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, May 28, 2002 12:16 PM
To: [EMAIL PROTECTED]
Subject: Re: About using TcpTunnelGui tool


Your SOAP client should be looking for
http://localhost:8888/soap/servlet/rpcrouter TcpTunnelGUI will
automatically translate that to the desired URL.

Mark.

At 11:58 AM 28/05/2002 -0400, you wrote:
>Hello,
>
>I was trying to use the TcpTunnelGui tool like the following on my local
>machine:
>
>c:\>java org.apache.soap.util.net.TcpTunnelGui 8888 ren.cs.odu.edu 8989
>
>where 8888 is listenport on my local machine, ren.cs.odu.edu is tunnelhost
>(a UNIX machine), and 8989 is tunnelport. My soap service is running on
>ren.cs.odu.edu:8989 hosted by tomcat.
>
>The GUI tool received and showed the request message from the soap client,
I
>see it in the first window and it looks fine, but in the second window it
>showed the tomcat exception messages and it seemed the soap request didn't
>get to the soap service.
>
>My question is don't we need to specify the router like
>http://ren.cs.odu.edu:8989/soap/servlet/rpcrouter or
>http://ren.cs.odu.edu:8989/soap/servlet/messagerouter? How will
TcpTunnelGui
>konw where to find the soap router and services if we don't provide this
>detail.
>
>Please give me some help.
>
>Thanks alot!
>
>Rufeng



Reply via email to