Eclipse Community Forums: ServerTools (WTP) » TCP/IP Monitor doing nothing

Home » Language IDEs » ServerTools (WTP) » TCP/IP Monitor doing nothing

TCP/IP Monitor doing nothing [message #87605]

Sun, 27 March 2005 20:27

Eclipse User

Hi,

I'm using
* Eclipse 3.1M5
* WTP 1.0M3
* Web Services (installation as described in http://www.eclipse.org/webtools/wst/components/ws/download_i nstructions_for_jars.html).
* Tomcat 5.0.28
* j2sdk1.4.2_04
* Windows 2000

The Web Services TCP/IP Monitor appears to doing nothing.

In the WTP Servers view I've selected a server -> context menu -> "Monitoring" -> "Monitor Port 8080 (HTTP)" -> checked.
Then I've started the server in debug mode.
Checking the Properties in the TCP/IP Monitor view shows a (started) monitor entry: localhost:8080 / HTTP / 14333 (local monitoring port)
Then I've called http://localhost:8080 in the browser - all the web applications on localhost:8080 are working well.

I've tried the server in run and debug mode. I've tried other local monitoring ports. Nothing helps.
There is no error in the Eclipse Error log.
Am I missing some configuration or preperation job?
Or is the monitor not supposed to work in the current state?

I tried the monitor with Eclipse 3.1M4 / WTP 1.0M2 / Web Services before as well (completely different installation) - didn't work either.

Big thanks for help,
Chily

Re: TCP/IP Monitor doing nothing [message #87671 is a reply to message #87605]

Mon, 28 March 2005 08:03

Eclipse User

I think I got the point:
I have to call the local monitoring port through the browser's URL.

So if monitor entry is: localhost:8080 / HTTP / 14333 (local monitoring port)
then I have to call http://localhost:14333/ instead of the server's http://localhost:8080/
Right?

Chily

Chily wrote0:
> Hi,
>
> I'm using * Eclipse 3.1M5
> * WTP 1.0M3
> * Web Services (installation as described in
> http://www.eclipse.org/webtools/wst/components/ws/download_i nstructions_for_jars.html).
>
> * Tomcat 5.0.28
> * j2sdk1.4.2_04
> * Windows 2000
>
> The Web Services TCP/IP Monitor appears to doing nothing.
>
> In the WTP Servers view I've selected a server -> context menu ->
> "Monitoring" -> "Monitor Port 8080 (HTTP)" -> checked.
> Then I've started the server in debug mode.
> Checking the Properties in the TCP/IP Monitor view shows a (started)
> monitor entry: localhost:8080 / HTTP / 14333 (local monitoring port)
> Then I've called http://localhost:8080 in the browser - all the web
> applications on localhost:8080 are working well.
>
> I've tried the server in run and debug mode. I've tried other local
> monitoring ports. Nothing helps.
> There is no error in the Eclipse Error log.
> Am I missing some configuration or preperation job?
> Or is the monitor not supposed to work in the current state?
>
> I tried the monitor with Eclipse 3.1M4 / WTP 1.0M2 / Web Services before
> as well (completely different installation) - didn't work either.
>
> Big thanks for help,
> Chily
>

Re: TCP/IP Monitor doing nothing [message #87746 is a reply to message #87671]

Mon, 28 March 2005 13:02

Eclipse User

That's right Chily.

>I think I got the point:
>I have to call the local monitoring port through the browser's URL.
>
>So if monitor entry is: localhost:8080 / HTTP / 14333 (local monitoring
port)
>then I have to call http://localhost:14333/ instead of the server's
http://localhost:8080/
>Right?
>
>Chily

Re: TCP/IP Monitor doing nothing [message #87954 is a reply to message #87746]

Tue, 29 March 2005 04:50

Eclipse User

But this way, you get one problem:
The monitor always forwards the wrong request URL: Not the real
Browser's URL (here with port 14333), but the server's URL (here with port 8080).
And it even sets the request header "host" to the wrong port (here 8080).

So the Java methods request.getRequestURL() or request.getServerPort() don't
return the URL from the Browser's address bar, but the server's URL.

This is especcially a problem, since response.sendRedirect() (or the JSP tag
<jsp:forward>) use the wrong host as well.
So it's not possible to klick through a web application using the TCP/IP
monitor if the website uses redirects. You always end up calling the server
directly, not through the monitor port.

The only workaround I found so far is to set the monitor's host/port as proxy in the
browser's settings and call the server's host in the browser's address bar. But
this way it's not possible to call any other website from the browser than the
monitored application.

Any suggestions?

Thanks,
Chily

Lawrence Mandel wrote:
> That's right Chily.
>
>
>>I think I got the point:
>>I have to call the local monitoring port through the browser's URL.
>>
>>So if monitor entry is: localhost:8080 / HTTP / 14333 (local monitoring
>
> port)
>
>>then I have to call http://localhost:14333/ instead of the server's
>
> http://localhost:8080/
>
>>Right?
>>
>>Chily
>
>

Re: TCP/IP Monitor doing nothing [message #100858 is a reply to message #87954]

Sat, 07 May 2005 14:15

Eclipse User

Originally posted by: laurentd75___no.sp_am.yahoo.fr

Hi Chily,

Any update on your TCP Monitor problem ?
Have you solved it in M3 ? If not, have you filed a bug report ?

Is it still happening in M4 ?

Thanks,

Laurent

----- "Chily" wrote:

> The monitor always forwards the wrong request URL: Not the real
> Browser's URL (here with port 14333), but the server's URL (here with port
8080).
> And it even sets the request header "host" to the wrong port (here 8080).
>
> So the Java methods request.getRequestURL() or request.getServerPort()
don't
> return the URL from the Browser's address bar, but the server's URL.
>
> This is especcially a problem, since response.sendRedirect() (or the JSP
tag
> <jsp:forward>) use the wrong host as well.
> So it's not possible to klick through a web application using the TCP/IP
> monitor if the website uses redirects. You always end up calling the
server
> directly, not through the monitor port.
>
> The only workaround I found so far is to set the monitor's host/port as
proxy in the
> browser's settings and call the server's host in the browser's address
bar. But
> this way it's not possible to call any other website from the browser than
the
> monitored application.
>
> Any suggestions?
>
>> I think I got the point:
>> I have to call the local monitoring port through the browser's URL.
>> So if monitor entry is: localhost:8080 / HTTP / 14333 (local monitoring
port)
>> then I have to call http://localhost:14333/ instead of the server's
>> http://localhost:8080/
>>

Re: TCP/IP Monitor doing nothing [message #975233 is a reply to message #87671]

Wed, 07 November 2012 13:10

Eclipse User

Thanks man,

I was about to break my head against the wall as this issue was taking considerable amount of my TIme.

By, the way what is "Local monitoring Port". Why would I need as my server is already running on 8080?

This is quite confusing. Could make this understand in a more better way.

Previous Topic:	Exporting static web project
Next Topic:	Local Client Problem

Goto Forum:

-=] Back to Top [=-

Current Time: Wed Jul 23 00:20:30 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter