I have no idea how the very complicated start script try to detect the java version, you could remove “exit 83” below “echo You can also try to delete the JVM cache file $HOME/.install4j” somewhere in the file and define “INSTALL4J_JAVA_HOME_OVERRIDE=’’/usr/lib/j2re1.5-sun’’” within the first lines.
It may exit with another error, so you may want to comment some more “exit” lines.
Then it should start someway, but I’'m not sure that it will really run.
I’‘m running into the same problem. I’‘m installing Wildfire 3 on Gentoo Linux. I installed the sun jdk and it’'s the one that is setup. I made no changes to the config file
I had the same issue… It happens in linux and its some odd linking error that makes the default JRE the wrong one. I dont know why this happens nor how to fix it sorry, but I will ask my co worker who did fix it, and I will come back. stay tuned tomarrow i think this is the same exact thing that happened to me. o and btw you will run into some other errors on the path to getting this to work
would you please run “sh -x ./wildfire start” and look at the output of the script and where it is exiting. Then remove or comment the exit statement(s).
echo No suitable Java Virtual Machine could be found . . .
I did try adding that extra line right before it started, but this didn’'t seem to affect anything either. I get the same response, even with that debug output.
echo No suitable Java Virtual Machine could be found on your system.
echo The version of the JVM must be at least 1.5.
echo Please define INSTALL4J_JAVA_HOME to point to a suitable JVM.
echo You can also try to delete the JVM cache file $HOME/.install4j
exit 83
fi
in your wildfire file. Change exit 83 to #exit 83 and it shoud run much better. You may hit another exit some line later which you also want to comment. This section should look like:
if [ -z “$app_java_home” ]; then
echo No suitable Java Virtual Machine could be found on your system.
echo The version of the JVM must be at least 1.5.
echo Please define INSTALL4J_JAVA_HOME to point to a suitable JVM.
echo You can also try to delete the JVM cache file $HOME/.install4j
so, I concluded that $app_java_home wasn’'t being set correctly. I saw that it was set in line 92 to $test_dir
I checked ‘‘which java’’ to find the location of java and changed line 92 to
app_java_home=$test_dir
app_java_home=/opt/sun-jdk-1.4.2.10
That didn’‘t seem to help so I assumed it was reset elsewhere so I undid the above change on line 92, couldn’'t find the variable set anywhere elso so I added this to blank line 243. (right after ‘‘echo “Starting wildfire”’’)
app_java_home=/opt/sun-jdk-1.4.2.10
now, if I run it using the command ‘‘sh -x ./wildfire start’’
It returns “nohup: appending output to `nohup.out’’”
cat nohup.out shows the file is empty, but exists.
If I run it directly, it reports the same error, but doesn’'t exit and then shows the same thing with an empty nohup.out file.
after any of these commands, ps aux|grep wild shows no instances of wildfire running.