oodt-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Hart (JIRA)" <j...@apache.org>
Subject [jira] [Created] (OODT-567) show JAVA_HOME env var in RADiX start command in all cases
Date Thu, 28 Feb 2013 21:11:14 GMT
Andrew Hart created OODT-567:
--------------------------------

             Summary: show JAVA_HOME env var in RADiX start command in all cases
                 Key: OODT-567
                 URL: https://issues.apache.org/jira/browse/OODT-567
             Project: OODT
          Issue Type: Bug
    Affects Versions: 0.5
            Reporter: Andrew Hart
            Assignee: Andrew Hart
            Priority: Minor
             Fix For: 0.6


The RADiX deployment script prints out a list of the environment variables when it starts
up. This looks something like: 

{code}
user@foo ~/Development/sandbox/oodt-deploy/bin $ ./oodt start
Using OODT_BASE:   /home/user/Development/sandbox/oodt-deploy
Using OODT_HOME:   /home/user/Development/sandbox/oodt-deploy
Using OODT_TMPDIR: /home/user/Development/sandbox/oodt-deploy/temp
Using JRE_HOME:    /usr
Using CLASSPATH: 
{code}

A common startup problem is related to JAVA_HOME not being properly set on the target system.
Currently, the RADiX script only includes the JAVA_HOME value if the the "oodt" command is
run with the debug flag. To make it easier to immediately diagnose potential environment problems,
the value for JAVA_HOME should be displayed in all modes of operation.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message