You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@oozie.apache.org by "Seetharam Venkatesh (JIRA)" <ji...@apache.org> on 2012/06/07 00:07:22 UTC

[jira] [Updated] (OOZIE-863) JAVA_HOME needs to be explicitly set at client since bin/oozie does not invoke oozie-env.sh

     [ https://issues.apache.org/jira/browse/OOZIE-863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Seetharam Venkatesh updated OOZIE-863:
--------------------------------------

    Attachment: OOZIE-863.patch
    
> JAVA_HOME needs to be explicitly set at client since bin/oozie does not invoke oozie-env.sh 
> --------------------------------------------------------------------------------------------
>
>                 Key: OOZIE-863
>                 URL: https://issues.apache.org/jira/browse/OOZIE-863
>             Project: Oozie
>          Issue Type: Bug
>          Components: client
>    Affects Versions: 3.2.0, trunk
>            Reporter: Seetharam Venkatesh
>            Assignee: Seetharam Venkatesh
>            Priority: Minor
>              Labels: patch
>             Fix For: trunk
>
>         Attachments: OOZIE-863.patch
>
>
> bin/oozie doesnt seem to be picking the java home from oozie-env.sh. User has to explicitly export JAVA_HOME to the installed JAVA_HOME to make sure it works. On an EC2 cluster the default java points to Java 1.4. So in that case if you just run bin/oozie without export JAVA_HOME (path for 1.6) it will error out with incompatibilty exception. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira