It seems that the problem is that the Java command is being executed, and not with the Bash code that runs it, but the Bash code has problems that make debugging difficult. One problem is that the string is used to store the command, parameters, and arguments. This is usually a bad idea because it makes it difficult to troubleshoot problems with globbing and word splitting. Another problem is using eval , which is best avoided and rarely needed. This is a slightly modified version of the code that uses arrays to store the command and does not use "eval":
#!/bin/bash DIR="$( cd "$( dirname "${BASH_SOURCE[0]}" )" && pwd )" app_cmd_parts=( "$DIR/../Resources/jre/Contents/Home/bin/java" -XstartOnFirstThread -Xdock:name='GS Risk' -Xdock:icon="$DIR/../Resources/AppIcon.ico" -Dorg.eclipse.swt.internal.carbon.smallFonts -Dosgi.console.enable.builtin=true -jar "$DIR/../Resources/plugins/org.eclipse.equinox.launcher_1.2.0.v20110502.jar" -data @noDefault -Dfile.encoding=UTF-8 -os macosx -ws cocoa -arch x86_64 -nl en_US -consoleLog -console -showsplash AppName ) runCommand() { typeset cmd_parts=( " $@ " ) typeset ret_code printf 'cmd_parts=(' printf ' %q' "${cmd_parts[@]}" printf ' )\n' "${cmd_parts[@]}" ret_code=$? case $ret_code in 0) printf "[%s] exit OK." "$NAME" ;; 23) printf "[%s] requested a restart. Restarting..." "$NAME" runCommand "${cmd_parts[*]}" ;; *) printf "Error : [%d] when executing command: '${cmd_parts[*]}'" $ret_code ;; esac printf "\n" exit $ret_code } runCommand "${app_cmd_parts[@]}"
It should be easier to debug. Run it with bash -x to see what exactly it does. Copy and paste the text between the brackets in the output of cmd_parts=( ... ) to re-run the Java command launched by the program. I hope this allows you to determine what is wrong with the team and how to fix it.