Shriram, try using tcpmon.
it's easy to setup and i think the only difference in the use of tcpmon vs. SOAPMonitor is that tcpmon must be run locally. you can still monitor remote services and clients if you have access to the Call object's endpoint setting in the client code. take a look at the Axis User Guide and try it if you haven't already. tcpmon receives the http request, including soap message, of course, since the Listen Port # is that of your endpoint. this is when you see the incoming soap request. so i guess it's the same view of the message as SOAPMonitor except you have the added benefit / distraction of a few characters of http header. tcpmon then forwards the request to the service whose location is specified as Target Hostname and Target Port # under Act as a ... Listener. the service then replies to tcpmon and this is where you see the response, including http header and soap message, before forwarding the response to the client. good luck. sherif ----- Original Message ----- From: "Shriram Kollipara" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, December 03, 2002 10:29 AM Subject: SoapMonitor Service > Hi, > > After digging throught the archives I found a post from Dennis > Sosnoski which explained how to run the soapmonitor service. I performed > all the steps mentioned at this URL: > > http://www.sosnoski.com/presents/java-xml/axis/axis-monitor.html > > I am still not able to see any soap messages. The only thing the applet > performs is, it shutsdown when i stop and restart my container. I am > trying to find if anyone got this working. Any replies would be of great > help in continuing my work. > > Thanks for the help in advance. > > shri >
