Solved - Java Update Stops Adito Again
I do system patching on servers every Saturday morning during a maintenance period. Almost always, nothing goes wrong. I’ve seen some really big patch sets for huge, complex systems go in cleanly … then there’s Java. Every Java update causes some kind of problem for Adito.
Here’s the fix to the latest and most future Java update issues with Adito … I hope.
The Fix
Edit the wrapper.conf file – usually placed in /opt/adito/conf/wrapper.conf
Find the line with
wrapper.java.command=/usr/lib/jvm/java-6-sun-xxxxxxxxx/jre/bin/java
in it.
Change that line to
wrapper.java.command=/usr/lib/jvm/java-6-sun/jre/bin/java
Next verify that /usr/lib/jvm/java-6-sun/ exists and if it doesn’t, create a softlink using
ln -s /usr/lib/jvm/java-6-sun-1.6.0.xx /usr/lib/jvm/java-6-sun
Obviously the exact command will need to be specific to your system.
The Root Problem
The Adito installation program/script was too specific on the exact location of Java and placed that inside the wrapper.conf file. There are other places where JAVA_HOME isn’t used and it should be. Basically, my original complaint about Adito doing startup the hard way still applies. A script that calls a script that calls a program that finally calls java to start something. Too complex. I nice script can perform all that easily without any smoke and mirrors. The use of a “wrapper” program just seems foolish to me.
Trackbacks
Use the following link to trackback from your own site:
https://blog.jdpfu.com/trackbacks?article_id=623
