[
https://issues.apache.org/jira/browse/OOZIE-863?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13397751#comment-13397751
]
Alejandro Abdelnur commented on OOZIE-863:
------------------------------------------
had a chat with Venkatesh on this one, it seems he was looking at an Oozie
built via Bigtop, and not the latest, the latest uses a Bigtop utility to
resolve the Java location.
I've opened OOZIE-878 to handle a config file on the client, may be as part of
that patch we could have also an oozie-env.sh on the client for people that use
directly Apache Oozie releases.
Would be OK to close this one as invalid then?
> 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
