[jira] [Commented] (ACCUMULO-2267) problems running accumulo from RPM

["Christopher Tubbs (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/ACCUMULO-2267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13885638#comment-13885638 ] 

Christopher Tubbs commented on ACCUMULO-2267:
---------------------------------------------

jps should be on the path for the JDK that comes in the CentOS repos, which is OpenJDK. I think I only put a dependency on the JRE, not the JDK. On the other hand, if it's not on the path because you've installed a different JDK than the one provided by the target distro, I'm not sure that should can be easily addressed. It seems to me that one should use the alternatives system or manipulate the PATH environment variable if that's the situation. On the other hand, it's not hard for us to explicitly try $JAVA_HOME/bin if `which jps` fails.

The start jar isn't technically in $JAVA_HOME/accumulo... that's a coincidence, at best, and we shouldn't rely on that. Technically, it's in the %{_javadir}/accumulo directory (built-in RPM macro for standard java library locations). The bootstrap classpath for the RPM can either get the start jar from $(rpm -E %{_javadir})/accumulo or identify the absolute path explicitly. Alternatively, we can symlink this directory to lib/, but then we need to deal with the 3rd issue you raise, which is that these jars have version decoration, if we don't want to make any other alterations.

For the remaining jars... that's a very simple fix, because it's just a matter of deploying a sensible default accumulo-site.xml file in /etc/accumulo.

> problems running accumulo from RPM
> ----------------------------------
>
>                 Key: ACCUMULO-2267
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-2267
>             Project: Accumulo
>          Issue Type: Bug
>    Affects Versions: 1.6.0
>            Reporter: Michael Berman
>
> - jps is called in the init.d scripts but it's not in the PATH it sets.  on my centos box, it's in $JAVA_HOME/bin
> - in bin/accumulo, accumulo-start.jar is expected to be in $ACCUMULO_HOME/lib, but actually it's in $JAVA_HOME/accumulo
> - in bin/accumulo, accumulo-start.jar does not have version decoration, but the installed jar does
> - nothing else (other accumulo jars from $JAVA_HOME/accumulo, other dependencies from $ACCUMULO_HOME/lib) seems to be getting into the classpath.  initial failure is NoClassDefFoundError: org/apache/commons/vfs2/provider/FileProvider
> i wonder if the standardization on RPM deployment locations is worth the departure from the standard accumulo deployment locations, at least for 1.6.0, since it seems like the impact on all the script infrastructure hasn't really been thought through yet, so close to the release.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)