-
Bug
-
Resolution: Done
-
Minor
-
7.0.0.GA, 7.1.0.DR19
On Windows 7, when running standalone.bat with the JAVA_HOME environment variable set (but pointing to an empty directory), JBoss EAP fails to start and does not give an error message.
On line 177 of the standalone.bat, a check is made to see if the JAVA_HOME variable points to a valid directory. If it does, it assumes this directory contains bin\java. If bin\java does not exist, the server fails to start and does not give a reason why.
expect to see an error message such as "%JAVA_HOME% path doesn't contain an executable at %JAVA_HOME%\bin\java"
Add additional checks in the standalone.conf to verify that %JAVA_HOME%\bin\java exists and warn if it does not.
- clones
-
WFCORE-3061 On Windows, when running standalone/Domain with the JAVA_HOME environment variable set (but pointing to an empty directory), JBoss EAP fails to start and does not give an error message.
- Resolved
- is cloned by
-
JBEAP-11421 On Windows, when running standalone/Domain with the JAVA_HOME environment variable set (but pointing to an empty directory), JBoss EAP fails to start and does not give an error message.
- Closed
-
JBEAP-11534 [GSS](7.0.z) On Windows, when running standalone/Domain with the JAVA_HOME environment variable set (but pointing to an empty directory), JBoss EAP fails to start and does not give an error message.
- Closed
- is incorporated by
-
JBEAP-11931 (7.1.0) Upgrade to WildFly Core to 3.0.0.Beta30
- Closed