This week's book giveaway is in the OCAJP forum. We're giving away four copies of OCA Java SE 8 Programmer I Study Guide 1Z0-808 and have Jeanne Boyarsky & Scott Selikoff on-line! See this thread for details.
I have installed jakarta-tomcat-4.1.31 and j2sdk1.4.2_06 and JAVA_HOME and CATALINA_HOME has been set sccordingly, but when I run startup.bat, the command prompt coming up but disapperaing very fast and http://localhost:8080/ does not bring up the tomcat page.
Hi, I also faced this problem earlier but what i did is I set environment variable by going to Mycomputer->properties and set JAVA-HOME,TOMCAT_HOME to corresponding jre directory,tomcat home directory.Then I again start server by startup.bat then server was started.try this I hope this will work
Joined: Dec 01, 2003
I have tried this one, but I get error when I try to run tomcat. So problem is still unresolved.
It's normal for the command prompt to disappear. If you're not seeing the tomcat page when you go to http://localhost:8080 then you should check the log files under TOMCAT_HOME\logs. One of them should tell you something.
By the way, if you want the dos window to stay open don't use 'startup'. From the bin directory, type: catalina start
The reason I want to use 4.1.x is that this is the same version we are running in university and I am doing a project that alitimately I have to deploy it to University Server and we have been advised to use the same version of tomacat. I just installed the exe version of tomcat and I had the same problem and nothing written in logs.
Also I should mention that version 5.0.28 is just working fine but it supports JSP 2.o, but I need to work with previous version of JSP and tomcat 4.1.
Joined: Dec 01, 2003
I have some good news
Eventually my problem solved. First I tried to see if tomcat 5 is working or not. What I see was that, at beginning of start up of tomcat, windows was that asked if it has to block it that I said no. Then I installed version 4.1 again that this time it worked fine. I guess there is an incompatibility between service pack 2 and tomcat 4.1 (may block it without showing any alert but show that for tomcat 5) that some how was solved.