- This topic has 1 reply, 2 voices, and was last updated 18 years, 3 months ago by
.
-
Posts
-
Hi all,
I’ve upgraded from Eclipse 3.1.2 to 3.2.1. MyEclipse was working fine in 3.1.2, but not in 3.2.1. Tomcat starts without error messages, but when I try to access a JSP page, an empty (HTML) page is returned. However, other web apps (e.g. opencms) are working fine. If I type in a wrong URL (to a non-existing JSP page), I get a tomcat error (which is fine). But no luck in getting a response from existing JSP pages. The console does not show any log messages. Also when the JSP page is modified, nothing will happen. Redeploying the application / reinstalling eclipse did not solve the problem.
The application is deployed as an exploded archive.
—–
Eclipse SDK
Version: 3.2.1
Build id: M20060921-0945—–
MyEclipse Web Services Support
Version: 5.0.1
Build id: 20060810-5.0.1-GAMyEclipse isn’t going to effect Tomcat half-running in any way like this. All MyEclipse does is launch Tomcat and connect the debugger to it, so Tomcat will either work or not work.
If your application is specifically not working, while others are working fine, you need to start looking at your startup logs to see if you can figure out why that application is failing to start. That should shed some light on it. Lastly, I would suggest removing the deployment for that project, cleaning/rebuilding it and then redeploying it as exploded to make sure it’s all up to snuff. That could possibly be an issue.
The important thing here is to check the startup Log for Tomcat in the console view. I have a feeling that either the project is failing to startup or the deployment could be failing, either way we can figure some things out from it.
