accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Berman (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ACCUMULO-2267) problems running accumulo from RPM
Date Wed, 29 Jan 2014 18:50:10 GMT

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

Michael Berman commented on ACCUMULO-2267:
------------------------------------------

bq. jps should be on the path for the JDK that comes in the CentOS repos, which is OpenJDK

I'm not sure what your point is here.  I do have a default openjdk installation, but whatever
my system path is by default is irrelevant because the init.d script explicitly sets the path
to a limited set of locations that does not include the JDK bin directory.

> 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)

Mime
View raw message