chukwa-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Eric Yang <>
Subject Re: chukwa agent jar not on classpath when agent starts
Date Fri, 20 Jan 2012 01:04:18 GMT
That was what happened.  We found it easier to maintain by having a
consolidated jar file which we are currently using it as
chukwa-core-${CHUKWA_VERSION}.jar.  We probably should stop building
chukwa agent jar file in the future releases.


On Thu, Jan 19, 2012 at 3:31 PM, Noel Duffy <> wrote:
> Using chukwa 0.4.0, I built an RPM with "ant rpm", then installed the rpm. I noticed
that chukwa-agent-0.4.0.jar is not on the classpath when I start a new agent. This means that
there are no adapters available by default. Is this intentional?
> Looking through the shell scripts used to start the agent, I found, in $CHUKWA_HOME/bin/,
these lines:
> export CHUKWA_CORE=${CHUKWA_HOME}/chukwa-core-${CHUKWA_VERSION}.jar
> export CHUKWA_AGENT=${CHUKWA_HOME}/chukwa-agent-${CHUKWA_VERSION}.jar
> export HICC_JAR=${CHUKWA_HOME}/hicc.war
> The environment variable CHUKWA_AGENT is never referenced again. The variable CHUKWA_CORE
is used in $CHUKWA_HOME/bin/chukwa when setting the classpath, as follows:
>  if [ "$BACKGROUND" = "false" ]; then
>    ${JAVA_HOME}/bin/java ${JAVA_OPT} -Djava.library.path=${JAVA_LIBRARY_PATH} -DCHUKWA_HOME=${CHUKWA_\
> WA_DATA_DIR} -DAPP=${APP} -classpath ${CHUKWA_CONF_DIR}:\
>  else
>    exec ${JAVA_HOME}/bin/java ${JAVA_OPT} -Djava.library.path=${JAVA_LIBRARY_PATH}
> {CHUKWA_DATA_DIR} -DAPP=${APP} -classpath
>  fi
> fi
> This leads me to suspect that CHUKWA_AGENT was meant to be on the classpath. Or perhaps
it was at one point, and was removed.

View raw message