Hi Sonja,
I used TCPMonitor for the first time this last weekend. It worked fine for me. The main thing is to remember that your SOAPClinet should point to the listen port of the monitor and the target port of the monitor should point to the http server that the client pointed to. The TCPMonitor is a pass-though application where your soap messages pass through that app on the way to the http server (Tomcat in my case).
I tried to get the SOAPMonitor Applet to compile but for some reason the class file was not int the axis jar so I never got that to work.
From the sounds of it your SOAP Client is not pointing to the listen port of the TCPMonitor app.
Best Regards,
Tony
-----Original Message-----
From: Sonja Pieper [mailto:[EMAIL PROTECTED]]
Sent: Monday, March 10, 2003 5:00 AM
To: [EMAIL PROTECTED]
Subject: Re: AW: SOAPMonitor
> http://www.sosnoski.com/presents/java-xml/axis/axis-monitor.html
I managed to compile the SOAPMonitor and I have tried to use tcpmon
well neither is doing what it should, I think!
Tcpmon: "Waiting for Connection" but nothing happens when I send a
request via my test-programm. Do I need to enter a special port to
listen on?
Anyhow. SoapMonitor cannot even connect to the server.
"SOAPMonitor is unable to communicate with server"
I have deployed it and modified my deployment for my service.
I redeployed the service. I reloaded the axis app.
What is wrong here? I followed the instructions of the page in the link
above.
Is anyone using SOAPMonitor?
Ciao
Sonja
--
[EMAIL PROTECTED], Tel: 91374-370
Always do sober what you said you'd do drunk. That will teach you to
keep your mouth shut. --Ernest Hemingway
