Oops !
Maybe it doesn't with JDK1.3 on Linux, because I've 4 servers running with
long up-times and my own machine using tomcat 3.1 AND JDK1.3. The problem I
found on NT was when using Tomcat as a service as soon as you logged off the
JDK was being shut down, but even this was a problem on the JDK, not TOMCAT,
and it seems to have been solved.
Wellington Silva
UN/FAO
-----Original Message-----
From: Sterling [mailto:[EMAIL PROTECTED]]
Sent: 10 November 2000 20:48
To: [EMAIL PROTECTED]
Cc: '[EMAIL PROTECTED]'
Subject: Re: Setting JAVA_HOME path on Linux 7.0
H-
This might not be relevant now, but I have read that Tomcat 3.1 doesn't work
with JDK1.3. It only works with JDK1.2.
I was having problems getting Tomcat running using JDK1.3. I switched and
changed my JAVA_HOME to point to JDK1.2 and all the problems went away. Well
not
all, but it started working as soon as I set my CLASS_PATH correctly. (The
whole
500 error terror. 8^)
Newbies .002$.
-Sterling
"Lambert, Stephen : CO IR" wrote:
> I have Tomcat 3.1 running standalone on a RedHat 6.2 server(yeah).
>
> However, on a Redhat 7.0 server, I having difficulty setting the path for
> JAVA_HOME after installing JDK1.3
> I can't cd to $JAVA_HOME.
>
> The .bash_profile is as follows:
> # .bash_profile
>
> # Get the aliases and functions
> if [ -f ~/.bashrc ]; then
> . ~/.bashrc
> fi
>
> # User specific environment and startup programs
>
> PATH=/usr/local/sbin:/usr/sbin:/sbin:$PATH:$HOME/bin:/usr/local/jdk1.3/bin
> BASH_ENV=$HOME/.bashrc
> USERNAME="root"
>
> export USERNAME BASH_ENV PATH
>
> JAVA_HOME=/usr/local/jdk1.3
> export JAVA_HOME
>
> -----------
>
> Also, when I shutdown the server, it requires /sbin/./shutdown -h now
>
> The only difference I can tell between the two Linux version is the
ENV(6.2)
> vs BASH_ENV(7.0)
>
> Can someone help?
> Thanks.
