A fix will be included in the next release. If you do not wish to wait for a release, then you could resort to any nightly build, starting with the one that was generated on February 17th, 2013.
hahahaha! forget it, it’s fixed in the latest version, i don’w know what happened, but now I made a clean installation, and it works, this is the script that appears (what I expected):
Attempt to locate JAVA_HOME
if [ -z $JAVA_HOME ]; then
JAVA_HOMES="/usr/lib/jvm/default-java
/usr/lib/jvm/java-7-sun
/usr/lib/jvm/java-6-sun
/usr/lib/jvm/java-1.5.0-sun
/usr/lib/jvm/java-7-openjdk-amd64
/usr/lib/jvm/java-7-openjdk
/usr/lib/jvm/java-6-openjdk-amd64
/usr/lib/jvm/java-6-openjdk"
for t in $JAVA_HOMES ; do
if [ -d $t ] ; then
JAVA_HOME=$t
break;
fi
done
fi
The problem was that I’am recycling an old server and updating a previous version of openfire.
The problem was that I’am recycling an old server and updating a previous version of openfire.
Hmm it may be a good idea if the debian installer/update script would replace and update the old init.d file.