Updated to Sun Java JDK 6 on Debian

ronkymac · 07-02-2009, 08:11 AM

Hello all,

I had been using the JDK 5 for some time, but wished to upgrade the lenny/debian box to Sun JDK 6, for various reasons.

Using the non-free repos, I found the installation quite straightforward and after following README.alternatives, I was well on the way to getting it up and running.

I did the usual and everything seemed all right :

Code:

update-java-alternatives --jre --set java-6-sun
update-java-alternatives --set java-6-sun

Next step was to get Tomcat up and running again, so I went about setting the JAVA_HOME in the applicable locations:

Code:

root@de003221:/home/ronald# cat /etc/default/tomcat5.5 | grep HOME
# JDK version 1.4. If JAVA_HOME is not set, some common directories for
JAVA_HOME=/usr/lib/jvm/java-6-sun

and also...

Code:

root@de003221:/home/ronald# cat /etc/profile | grep HOME
JAVA_HOME="/usr/lib/jvm/java-6-sun"
export JAVA_HOME

hence java -version displays the following:

Code:

root@de003221:/home/ronald# java -version
java version "1.6.0_12"
Java(TM) SE Runtime Environment (build 1.6.0_12-b04)
Java HotSpot(TM) Client VM (build 11.2-b01, mixed mode, sharing)

Hell yes! Or not... since things seem to have taken a turn for the worse.

upon /etc/init.d/tomcat5.5 start, nothing is executed and no errors display. All tomcat logs have no changes appended, and neither do log/messages, log/debug, or log/syslog. Doing an strace /etc/init.d/tomcat5.5 start shows nothing out of the ordinary either.

So my question is, what's the best way of going about to find out what's going on? How do I get any logs? I'm logless! Help!

Ronald.

ronkymac · 07-02-2009, 08:48 AM

Oh well after a bit of poking around, it was due to the fact that /usr/share/java had been renamed and removed. Thank goodness I didn't delete it completely.

FNT (for next time): Don't manually remove JDK from your Debian system!

R

nowonmai · 07-02-2009, 08:52 AM

Try starting it using $CATALINA_HOME/bin/startup.sh instead... that way all the startup messages will go to stdout and you can see any problems.

{edit} Ah, I see you got it sorted...

ronkymac · 07-02-2009, 09:05 AM

Quote:

Originally Posted by nowonmai

Try starting it using $CATALINA_HOME/bin/startup.sh instead... that way all the startup messages will go to stdout and you can see any problems.

I did... however, as Java (as I've since discovered) was non-existent, it was refusing to find the "VM" [as it put it - presumably catalina is what handles the Tomcat instances/hence breaks on not finding java interpreter?]

Thanks,
Ronald.