Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Web Tools Project (WTP) » Tomcat timeout - but started correctly
Tomcat timeout - but started correctly [message #230681] Fri, 24 April 2009 09:55 Go to next message
Jens Rosenthal is currently offline Jens Rosenthal
Messages: 2
Registered: July 2009
Junior Member
Hi everyone,

I stumbled across a problem with the Tomcat integration.
Sadly this is a problem, I'm experiencing from time to time.

I've used the Eclipse/Tomcat integration without any problems (brand new
eclipse, wtp from eclipse.org starting of the week). Then after a while,
the problem starts... Tomcat is up-and-running ("Server startup in 494
ms"), but eclipse doesn't recognize this fact ("Server timeout after 45
sec.") and kills the running tomcat. Btw. tried it without any projects or
with projects. Same behavior - tomcat is up, an then get's killed by
eclipse :-(.

I could occasionally fix this problem by removing the tomcat and then
adding it again, or restarting eclipse. But sometimes - like now ;-) -
nothing is really helping.

Has anyone a workaround for this problem? Any help is appreciated...

Thanks in advance,
Jens
Re: Tomcat timeout - but started correctly [message #230737 is a reply to message #230681] Mon, 27 April 2009 12:53 Go to previous messageGo to next message
Larry Isaacs is currently offline Larry Isaacs
Messages: 1305
Registered: July 2009
Senior Member
Jens Rosenthal wrote:
> Hi everyone,
>
> I stumbled across a problem with the Tomcat integration.
> Sadly this is a problem, I'm experiencing from time to time.
>
> I've used the Eclipse/Tomcat integration without any problems (brand new
> eclipse, wtp from eclipse.org starting of the week). Then after a while,
> the problem starts... Tomcat is up-and-running ("Server startup in 494
> ms"), but eclipse doesn't recognize this fact ("Server timeout after 45
> sec.") and kills the running tomcat. Btw. tried it without any projects
> or with projects. Same behavior - tomcat is up, an then get's killed by
> eclipse :-(.
> I could occasionally fix this problem by removing the tomcat and then
> adding it again, or restarting eclipse. But sometimes - like now ;-) -
> nothing is really helping.
>
> Has anyone a workaround for this problem? Any help is appreciated...
>
> Thanks in advance,
> Jens
>
>
>

Is this happening with all defaults and no Tomcat configuration changes?
The server startup time is more like "initialization" it doesn't
indicate the server is ready yet, though if there are no webapps other
than the ROOT webapp, is should be pretty close.

Cheers,
Larry
Re: Tomcat timeout - but started correctly [message #230745 is a reply to message #230737] Mon, 27 April 2009 14:23 Go to previous messageGo to next message
Jens Rosenthal is currently offline Jens Rosenthal
Messages: 2
Registered: July 2009
Junior Member
Larry Isaacs schrieb:
> Jens Rosenthal wrote:
>
> Is this happening with all defaults and no Tomcat configuration changes?
> The server startup time is more like "initialization" it doesn't
> indicate the server is ready yet, though if there are no webapps other
> than the ROOT webapp, is should be pretty close.
>
> Cheers,
> Larry

HI Larry,

yes it is... All defaults, no configuration changes and no webapp.
The tomcat is working. You can connect to the :8080 port with the
browser, and if a webapp is added to the tomcat installation, the web
pages are correctly rendered until it get's killed by eclipse.

On Saturday I tried a "eclispe -clean" start, and now it's working again
, but now I'm waiting for the problem to occur again.

If I could find the source of this problem I would be glad :-)

Cheers,
Jens
Re: Tomcat timeout - but started correctly [message #230753 is a reply to message #230745] Mon, 27 April 2009 14:51 Go to previous messageGo to next message
Larry Isaacs is currently offline Larry Isaacs
Messages: 1305
Registered: July 2009
Senior Member
Jens Rosenthal wrote:
> Larry Isaacs schrieb:
>> Jens Rosenthal wrote:
>>
>> Is this happening with all defaults and no Tomcat configuration changes?
>> The server startup time is more like "initialization" it doesn't
>> indicate the server is ready yet, though if there are no webapps other
>> than the ROOT webapp, is should be pretty close.
>>
>> Cheers,
>> Larry
>
> HI Larry,
>
> yes it is... All defaults, no configuration changes and no webapp.
> The tomcat is working. You can connect to the :8080 port with the
> browser, and if a webapp is added to the tomcat installation, the web
> pages are correctly rendered until it get's killed by eclipse.
>
> On Saturday I tried a "eclispe -clean" start, and now it's working again
> , but now I'm waiting for the problem to occur again.
>
> If I could find the source of this problem I would be glad :-)
>
> Cheers,
> Jens

This isn't something I'm able to duplicate. To find out why this is
happening, it will likely require debugging on your system. The
simplest way to do that is use the WTP SDK. I can provide details if
you want to pursue this.

Cheers,
Larry
Re: Tomcat timeout - but started correctly [message #491190 is a reply to message #230681] Tue, 13 October 2009 15:19 Go to previous messageGo to next message
Stefan Lindenberg is currently offline Stefan Lindenberg
Messages: 2
Registered: October 2009
Junior Member
I have the same problem with the Eclipse server view and Tomcat 6. I tried to set it to zero, but it changed to 1 when I was saving the config file... Sad Is there any way to disable that timeout completly? How to debug WTP?

Thanks!

[Updated on: Tue, 13 October 2009 15:55]

Report message to a moderator

icon4.gif  Re: Tomcat timeout - but started correctly [message #491220 is a reply to message #230681] Tue, 13 October 2009 16:39 Go to previous messageGo to next message
Stefan Lindenberg is currently offline Stefan Lindenberg
Messages: 2
Registered: October 2009
Junior Member
The problem disappears, if there are any HTTP connectors enabled! It does not work with AJP alone.
Re: Tomcat timeout - but started correctly [message #491221 is a reply to message #491190] Tue, 13 October 2009 16:36 Go to previous messageGo to next message
Larry Isaacs is currently offline Larry Isaacs
Messages: 1305
Registered: July 2009
Senior Member
Stefan Lindenberg wrote:
> I have the same problem with the Eclipse server view and Tomcat 6. I
> tried to set it to zero, but it changed to 1 when I was saving the
> config file... :( Is there any way to disable that timeout completly?
> Thanks!

Setting it to a ridiculously high value is as close to disabling as you
can get. Negative values aren't supported and zero means immediate timeout.

Cheers,
Larry
Re: Tomcat timeout - but started correctly [message #527691 is a reply to message #230681] Fri, 16 April 2010 07:04 Go to previous message
Filip Mechant is currently offline Filip Mechant
Messages: 1
Registered: April 2010
Junior Member
Hi,

I had the same problem.

It started when I wanted to view a page on another computer. I changed the configuration of Tomcat (the RemoteAddrValve) and changed the hostname from localhost to x.x.x.x..

Afterwards, I put the old configuration back, but forgot to change the hostname back to localhost. This was no problem, until I restarted my computer. I got a new IP address (DHCP) and then I had the behavior like described in this thread.

All I had to do was set the host name back to localhost, and voila, my problem went away.

I hope this is helpful for the next person with the same problem.

Cheers,
Filip
Previous Topic:Customization of WSDL Editor
Next Topic:How to listen to "Add and remove projects" to server event?
Goto Forum:
  


Current Time: Tue Sep 23 16:41:15 GMT 2014

Powered by FUDForum. Page generated in 0.07256 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software