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/chukwa-config.sh, 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_\
HOME} -DCHUKWA_CONF_DIR=${CHUKWA_CONF_DIR} -DCHUKWA_LOG_DIR=${CHUKWA_LOG_DIR}
-DCHUKWA_DATA_DIR=${CHUK\
WA_DATA_DIR} -DAPP=${APP} -Dlog4j.configuration=chukwa-log4j.properties
-classpath ${CHUKWA_CONF_DIR}:\
${CLASSPATH}:${CHUKWA_CORE}:${HADOOP_JAR}:${COMMON}:${tools} ${CLASS} $OPTS $@
else
exec ${JAVA_HOME}/bin/java ${JAVA_OPT}
-Djava.library.path=${JAVA_LIBRARY_PATH} -DCHUKWA_HOME=${CH\
UKWA_HOME} -DCHUKWA_CONF_DIR=${CHUKWA_CONF_DIR}
-DCHUKWA_LOG_DIR=${CHUKWA_LOG_DIR} -DCHUKWA_DATA_DIR=$\
{CHUKWA_DATA_DIR} -DAPP=${APP} -Dlog4j.configuration=chukwa-log4j.properties
-classpath ${CHUKWA_CONF_\
DIR}:${CLASSPATH}:${CHUKWA_CORE}:${HADOOP_JAR}:${COMMON}:${tools} ${CLASS}
$OPTS $@ &
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.
