Eclipse Community Forums: ServerTools (WTP) » Server Starting... Tomcat 6 on 127.0.0.2

Help

Home

Home » Language IDEs » ServerTools (WTP) » Server Starting... Tomcat 6 on 127.0.0.2

Show: Today's Messages :: Show Polls :: Message Navigator

Server Starting... Tomcat 6 on 127.0.0.2 [message #230953]

Fri, 01 May 2009 21:05

jfrank

Messages: 2
Registered: July 2009

Junior Member

I have an interesting problem with WTP Servers. I setup localhost aliases
in my hosts file as follows:

127.0.0.2 www.domain.jf

I then set my server.xml connector node to address 127.0.0.2 on port 80
and saved it. I have included the relevant parts of server.xml here.

<Connector connectionTimeout="20000" address="127.0.0.2" port="80"
protocol="HTTP/1.1" redirectPort="8443"/>
<Engine defaultHost="www.domain.jf" name="Catalina">
<Host appBase="webapps" autoDeploy="true" name="www.domain.jf" ...

I started the server through eclipse WTP, it starts as expected, and
responds perfectly in a browser.

INFO: Starting Coyote HTTP/1.1 on http-127.0.0.2-80
May 1, 2009 1:58:45 PM org.apache.catalina.startup.Catalina start
INFO: Server startup in 76949 ms

However it never leaves the server starting state. At the end of the
startup timeout which is really really high, it kills the server.

I assume it is because it doesn't properly attempt a connection to the
correct server, but I don't know how else to tell it, "hit 127.0.0.2:80".

My WST server core is version 3.0.4.v20090115-20Am8s733J3_4F1256

- Joshua

Report message to a moderator

Re: Server Starting... Tomcat 6 on 127.0.0.2 [message #230964 is a reply to message #230953]

Sat, 02 May 2009 00:02

jfrank

Messages: 2
Registered: July 2009

Junior Member

I am beginning to think that localhost is just assumed. Could someone
confirm this? I tried installing a virtual adapter and registered
192.168.0.1, again tomcat doesn't care but WTP Servers won't detect the
started server. Loads up great in a browser, until it times out and gets
killed.

I notice the server editor gui has a section for ports, but none for IP. I
would assume it looks up the ip via the 'hostname' configuration, but
AFAICanTell it does not for the purposes of "checking whether started".

There is nothing to deploy in this example, and if I move it back to
localhost it works fine.

The problem is I need to run three servers, and want to use port 80 for
all of them on different ips (as they run in production).

Report message to a moderator

Re: Server Starting... Tomcat 6 on 127.0.0.2 [message #231004 is a reply to message #230964]

Mon, 04 May 2009 07:45

Eclipse User

Originally posted by: mauro.molinari.cardinis.com

jfrank ha scritto:
> I am beginning to think that localhost is just assumed. Could someone
> confirm this? I tried installing a virtual adapter and registered
> 192.168.0.1, again tomcat doesn't care but WTP Servers won't detect the
> started server. Loads up great in a browser, until it times out and gets
> killed.

What can I say is that I had a similar problem in the past when trying
to completely disable the HTTP connector to keep only the HTTPS
connector: Eclipse wouldn't ever realize that the server had been
properly started. At last I gave up and enabled back the HTTP connector.

Mauro.

Report message to a moderator

Re: Server Starting... Tomcat 6 on 127.0.0.2 [message #231012 is a reply to message #231004]

Mon, 04 May 2009 13:20

Larry Isaacs

Messages: 1354
Registered: July 2009

Senior Member

Mauro Molinari wrote:
> jfrank ha scritto:
>> I am beginning to think that localhost is just assumed. Could someone
>> confirm this? I tried installing a virtual adapter and registered
>> 192.168.0.1, again tomcat doesn't care but WTP Servers won't detect
>> the started server. Loads up great in a browser, until it times out
>> and gets killed.
>
> What can I say is that I had a similar problem in the past when trying
> to completely disable the HTTP connector to keep only the HTTPS
> connector: Eclipse wouldn't ever realize that the server had been
> properly started. At last I gave up and enabled back the HTTP connector.
>
> Mauro.

The problem is that TomcatServerBehavior is currently hard coded to ping
"http://localhost". Feel free to open a bug against the WTP Server
Tools jst.server component.

Cheers,
Larry

Report message to a moderator

Previous Topic:	JSDT tests errors/failures
Next Topic:	REST services

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Fri Apr 19 13:09:16 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter