Tomcat Problem

[Mukul]

Hi all,
I installed Tomcat 4 on my PC.But I am having problem starting it when I click the startup.bat file it give me a error saying that WINDOWS CANNOT FIND 'DJava.endorsed.dirs=.' .What might be the problem I am having JDK 1.4
Any help will be highly appreciated
Bye
Mukul

[Jason Brawner]

Did you set the JAVA_HOME environment variable?

[Anonymous]

Mukul,
I am sorry to say that you name does not comply with the Javaranch naming policy. Please choose a name that does and re-register.

[Nicole Swan]

I received the same error when I installed Tomcat 4.0.3. It's caused by the JAVA_HOME env variable not being set.

[Gale Greaser]

I am having the same problem as Mukul.
I am trying to run Tomcat on WindowsXP.
My JAVA_HOME env variable is set to
C:\Program Files\Java\j2re1.4.1 which seems correct.
However I am getting a
"Windows connot find '-Djava.endorsed.dirs=' error when it trys to use JAVA_HOME.
Any suggestions?
Thanks!

[Rene Larsen]

JAVA_HOME is NOT 'C:\Program Files\Java\j2re1.4.1' it is something like 'C:\j2sdk1.4.1'
Rene

[Anonymous]

Mango,
Unless I am sorely mistaken, Mango Cheeta runs afoul of the Official Javaranch Naming Policy in its "obviously fictitious" clause. Please choose a name that complies.

[Nigel Kat]

JAVA_HOME can be anything you need it to be. The important part is that it is the path which leads to the bin directory of the SDK that you want to provide the JVM for the web server. Different people set up their machines differently. Not wrong, just different.
I have the same issue with XP, although when comparing to the JAVA_HOME definition on both a WinNT and Win2K system, there is no difference in the format of the JAVA_HOME definition, just differences in the path itself.
Make sure there are no additional characters after the directory name that is the parent of bin. Many path variables end with ..;.; to indicate that the current and parent directory should also be checked, these should not be included here. Not sure if that will fix it, but give it a shot.
Kat
>^..^<

[Mike Curwen]

Originally posted by Nigel Kat:
JAVA_HOME can be anything you need it to be. The important part is that it is the path which leads to the bin directory of the SDK that you want to provide the JVM for the web server. Different people set up their machines differently. Not wrong, just different.

With the caveat that the poster was referring to a particular version of JAVA_HOME that definately *is* wrong. You can't substitute a JRE for a JDK.

[Jacky Chow]

I have the same problem before even i set "JAVA_HOME ", the wrong thing in my case is that there is a space after JAVA_HOME.