Initially I used startup.bat but the console window closed before I could even see the stack trace. The logs folder does not contain any files for inspection. Subseqeuently I switched to invoking tomcat with the following command,
This enabled me to run tomcat within the same window and examine the stack trace, part of which I included within the original post.
I have run this version of tomcat before, albeit on a different machine (similar spec). I'm puzzled as to why I'm having problems. Installation's never been an issue before. regards, Mo
Author and all-around good cowpoke
Joined: Mar 22, 2000
You can change the last executable line in startup.bat to say:
call "%EXECUTABLE%" run %CMD_LINE_ARGS% instead of call "%EXECUTABLE%" start %CMD_LINE_ARGS%
This will let startup.bat do its thing with the environment variables AND leave the window open so you can see why tomcat dies.
That FileNotFoundException message points to a messed up environment variable somehow. You can modify catalina.bat to echo the environment variables before it tries to start Tomcat. Bill [ February 10, 2007: Message edited by: William Brogden ]
Joined: Jan 25, 2006
Thanks for taking the time to answer my query.
It turned out to be a simple problem. Actually I feel rather sheepish (baa baa baa).
When I checked the path, I noticed that my system variable for TOMCAT had a / at the end. Therefore the actual path was tomcat//bin. Eeeks.
Such a silly error. I feel so silly that I'm wearing a paper bag over my head with holes cut out for my eyes and mouth.