[
https://issues.apache.org/jira/browse/BOOKKEEPER-765?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14019836#comment-14019836
]
Rakesh R commented on BOOKKEEPER-765:
-------------------------------------
bq.all we need is the java executable
JAVA_HOME checks added as part of BOOKKEEPER-712. I agree this fix will at
least make my server run. But I've one doubt, assume user by mistake not set
JAVA_HOME and starting with 'which version'. Will this creates problem like, my
server started with older version and later point of time unfortunately when
tries to execute few statements(which needs higher version) the process can
crash or unresponsive ?. Previously user would get err messages during start up
itself.
> bookkeeper script should fall back to java in path if JAVA_HOME is not set
> --------------------------------------------------------------------------
>
> Key: BOOKKEEPER-765
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-765
> Project: Bookkeeper
> Issue Type: Bug
> Components: bookkeeper-server
> Reporter: Ivan Kelly
> Assignee: Ivan Kelly
> Priority: Blocker
> Fix For: 4.3.0, 4.2.3
>
> Attachments:
> 0001-BOOKKEEPER-765-bookkeeper-script-should-fall-b.trunk.patch,
> 0001-BOOKKEEPER-765-bookkeeper-script-should-fall-back-to.patch
>
>
> The current behaviour requires JAVA_HOME to be set, which isn't set by
> default on all machines. So machines on which bookkeeper ran fine, no longer
> work.
> Solution is to fallback to java in path is JAVA_HOME not set.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
