How does it works on MYEclipse 3.8.1

1) Open the view: Window > Show View > Other... > MyEclipse > TCP/IP Monitor
2) Add a host to monitor: Click the down button (v) on the top right of the monitor view, select "properties" and click "Add" to add a host to monitor
3) Select the newly added domain and click "start" to begin monitoring.

Its doesnt actually seem to work for me. I used the same exact steps. I am running tomcat at port 8080 so I gave localhost and 8080 in port but it doesnt show any monitoring activity though I started it!

The monitor works as a proxy. So, you configure for monitoring port 8080 by setting:

Monitor
Hostname: localhost
Port: 8080
Protocol: HTTP

and Local monitoring port to something else, like 80.

Start your server on 8080 and start the TCP monitor. Direct your browser to http://localhost:80/WebAppContext

Hitting port 80 will redirect to 8080 through the monitor and the monitoring view will be opened. Hitting port 8080 directly bypasses the monitor.

I am trying to work with the TCP/IP monitor and I am really newby here.

I work with Apache2 + JBoss3.2.5 (+ Tomcat 5).

1. Apache is listenting on port 8080.
2. I set the TCP/IP monitor to:
Local monitoring port: 80
HostName: www.site.com
Type: HTTP
Port: 8080

THe first time I go to www.site.com the monitor gets it and I see an ew entry. But then the browser is redirected to www.site.com:8080 so my next click in the site will bypass the monitor. I am using Sruts as well v1.1, if that helps.
Please help..

Thanks in advance,

Erez

Erez,
The redirect is causing you to avoid the proxy all together, I would suggest trying to avoid the redirect all together... for example, don't navigate to www.site.com, instead navigate to the front page of the site somehow:
http://localhost/mySiteApp/index.jsp

I believe that will hit the HTTP monitor on port 80, which will redirect the request "/mysiteApp/index.jsp" to your monitored app (www.site.com) on port 8080 giving you the eventual request:
http://www.site.com:8080/mySiteApp/index.jsp

Can you give that a try? If that doesn't work, try and think of a way to avoid the redirect while still talking through the proxy.

I don't have a web sever and hence I connect to my webapp deployed in tomcat app-sever as http://localhost:8080/mycontext

How can I use this TCP/IP Monitoring plugin to sniff my requests made to my local server from my local machine?

Thanks in advance

shadangi,
You treat it like a proxy, you configure the port you want the monitor to listen on, and then the target location for it to send traffic to after it's done sniffing it... then in your browser you hit the listening port, like http://localhost:40800, and the monitor will show you all your HTTP headers as you interact with your app.