Thanks - I tried tcpmon and was able to see request/responses in it when
sending unzipped request messages. But after enabling request message
compression using the Apache CommonsHttpSender class, tcpmon shows the
compressed request, but no response comes back from the service. For the
zipped request message, here is the http header that tcpmon shows:

POST /services/Soap/u/7.0 HTTP/1.1
Content-Type: text/xml; charset=utf-8
SOAPAction: ""
User-Agent: Axis/1.3
Accept-Encoding: gzip
Content-Encoding: gzip
Transfer-Encoding: chunked
...

I am not sure if their is some glitch that is causing tcpmon to forwarding
zipped messages incorrectly to the service because of which I do not get any
response. When I remove tcpmon and send the zipped requests directly to the
webservice, it works.


Thanks,

Vish.


-----Original Message-----
From: Ulf Dittmer [mailto:[EMAIL PROTECTED]
Sent: Friday, February 17, 2006 12:31 AM
To: [email protected]
Subject: RE: Can SOAPMonitor be used to sniff http requests/responses on
c lien t side?


I don't think SOAPMonitor can be used with remote services. It's a JAX-RPC
handler, which can examine requests/responses on the host it runs on. It
has no provisions for forwarding a request to someplace else. prashanth
was probably thinking of TCPMon, which can do this.


> I got Soapmonitorservice and applet up. By default, it is on port 5001 so
> X=5001. Where do I define destination port and where do I define
> destination host?
>
> -----Original Message-----
> From: prashanth shivakumar [mailto:[EMAIL PROTECTED]
> Sent: Thursday, February 16, 2006 2:59 PM
> To: [email protected]
> Subject: Re: Can SOAPMonitor be used to sniff http requests/responses on
> clien t side?
>
> you can monitor on client as well...
> Configure your monitor so that local port is "X"[this is any free local
> port on ur local system] and destination port is "Y"[this is the port on
which ur webservice is running...Ex:8080]..
>
> Now making use of ur client,send requests to port "X" and NOT
> "Y"...everything should work fine..

Reply via email to