Thank you very much. I followed your instruction on tcpmon and it worked!. But I'm greedy: in my situation, where client and service are on the same host, how can I use SOAPMonitor?
Thanks again.
Zhaohua
Norris Merritt wrote:
If your client and service are on the same host, you only need tcpmon. You
have to arrange for your client to explicitly send the SOAP request to the
host/port that tcpmon is listening on, and configure tcpmon to forward the
SOAP request to the host/port that the web service is listening on. In other
words, tcpmon uses a man-in-the-middle strategy. -----Original Message-----
From: Zhaohua Meng [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, January 15, 2003 4:17 PM
To: [EMAIL PROTECTED]
Subject: tcp and SOAP monitor
Gurus,
I'm a newbie here. I invoke the tcp and SOAP monitor as following
java org.apache.axis.utils.tcpmon 10001 localhost 8080
http://localhost:8080/axis/SOAPMonitor
When making a request to a service deployed successfully using command line, I can get the response back in the java console. However, nothing happens in the monitor screen except "Waiting for Connection..."
I didn't change anything in the web.xml.
Am I doing something wrong here? I'm using axis1.1beta.
Thanks,
Zhaohua Meng
