|
Description:
|
RSN-367
I've noted this issue showing up on a few message boards without anyone giving any kind of resolution. I can't really say whether this is an actual bug, or just a failure on the part of the user (including myself). Essentially, when Resin is started via httpd.sh during the Linux init sequence, shell environment variables such as JAVA_HOME may not be set. The result is that as soon as the keep-alive part of the wrapper.pl script kicks in, the user gets a message saying "Server died unexpectedly" and is told to check stderr.log and stdout.log. Neither log file provides any information that would be helpful to a user trying to determine why his server is failing on boot. However, jvm.log DOES give the answer with a "Can't start java: ..." message. While a lack of environment variables during init technically qualifies as a user error and not a bug in Resin, it would be nice if the stderr or stdout logs would inform the user that Resin failed because "java" could not be found.
If nothing else, it would be helpful to see a suggestion like "Try changing your start-up file to read: /path/to/resin/bin/httpd.sh start -java-exe /path/to/java_home/bin/java", which is at least a useful temporary fix.
|