|
Re: Tomcat timeout - but started correctly [message #230737 is a reply to message #230681] |
Mon, 27 April 2009 12:53 |
Larry Isaacs Messages: 1354 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 |
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 |
Larry Isaacs Messages: 1354 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
|
|
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.03147 seconds