Home | About | Sematext search-lucene.com search-hadoop.com
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB
 Search Hadoop and all its subprojects:

Switch to Threaded View
Chukwa >> mail # user >> HICC errors after moving from ant to maven


Copy link to this message
-
Re: HICC errors after moving from ant to maven
Matthias,

Please create a JIRA ticket for this on

https://issues.apache.org/jira/browse/CHUKWA

and submit the patch there
On Thu, Dec 8, 2011 at 8:57 AM, Schlachter, Matthias <
[EMAIL PROTECTED]> wrote:

> This is for pom.xml and bin/chukwa-config.sh in trunk 1211721
>
> Regards,
> Matthias
>
> On Wed, 2011-12-07 at 22:06 -0800, Eric Yang wrote:
> > Looks like safe change to revert back.  Maybe it's better to manually
> > construct class path than using wildcards.  Could you submit the
> > changes as a patch?  Thanks
> >
> > regard,
> > Eric
> >
> > On Wed, Dec 7, 2011 at 9:11 PM, Schlachter, Matthias
> > <[EMAIL PROTECTED]> wrote:
> > > I replaced the following in chukwa-config.sh (which gets deployed to
> > > libexec)
> > >
> > > CHUKWA_CLASSPATH="${CHUKWA_HOME}/share/chukwa/*:
> > > ${CHUKWA_HOME}/share/chukwa/lib/*"
> > >
> > > with
> > >
> > > CHUKWA_CLASSPATH=""
> > > for jarFile in ${CHUKWA_HOME}/share/chukwa/*.jar; do
> > >    CHUKWA_CLASSPATH=$CHUKWA_CLASSPATH:$jarFile;
> > > done
> > > for jarFile in ${CHUKWA_HOME}/share/chukwa/lib/*.jar; do
> > >    CHUKWA_CLASSPATH=$CHUKWA_CLASSPATH:$jarFile;
> > > done
> > >
> > > I am using ubuntu 10.04 LTS 64bit, and sun jdk:
> > > java version "1.6.0_26"
> > > Java(TM) SE Runtime Environment (build 1.6.0_26-b03)
> > > Java HotSpot(TM) 64-Bit Server VM (build 20.1-b02, mixed mode)
> > >
> > >
> > > Regards,
> > > Matthias
> > >
> > > On Wed, 2011-12-07 at 20:59 -0800, Eric Yang wrote:
> > >> In the default shell script, it is loading jar files using wildcard.
> > >> In theory, jersey-core should load before jsr311-api by alphabetic
> > >> order.  Is there customization to the deployment to make the class
> > >> path loading different?  What OS are you running to observe those
> > >> issues?
> > >>
> > >> regards,
> > >> Eric
> > >>
> > >> On Wed, Dec 7, 2011 at 8:20 PM, Schlachter, Matthias
> > >> <[EMAIL PROTECTED]> wrote:
> > >> > OK, that fixed it for me:
> > >> >
> > >> > I added exclusions to the hadoop dependency in the pox.xml:
> > >> > ...
> > >> >          <dependency>
> > >> >            <groupId>org.apache.hadoop</groupId>
> > >> >            <artifactId>hadoop-core</artifactId>
> > >> >            <version>0.20.205.0</version>
> > >> >            <exclusions>
> > >> >              <exclusion>
> > >> >                <artifactId>jasper-compiler</artifactId>
> > >> >                <groupId>tomcat</groupId>
> > >> >              </exclusion>
> > >> >              <exclusion>
> > >> >                <artifactId>jasper-runtime</artifactId>
> > >> >                <groupId>tomcat</groupId>
> > >> >              </exclusion>
> > >> >            </exclusions>
> > >> >          </dependency>
> > >> > ...
> > >> >
> > >> > This introduced then a new problem:
> > >> > IncompatibleClassChangeError javax.ws.rs.core.Response$Status does
> not
> > >> > implement the requested interface
> > >> >
> > >> > I got rid of that by making sure that the jersey-core JAR appears
> before
> > >> > the jsr311-api JAR in the classpath
> > >> >
> > >> > Regards,
> > >> >
> > >> > Matthias
> > >> >
> > >> >
> > >> > On Thu, 2011-12-08 at 11:33 +1100, Schlachter, Matthias wrote:
> > >> >> Thanks Eric.
> > >> >>
> > >> >> jasper is a dependency of hadoop-core:jar in maven
> > >> >>
> > >> >> [INFO] +- com.google.guava:guava:jar:10.0.1:compile
> > >> >> [INFO] |  \- com.google.code.findbugs:jsr305:jar:1.3.9:compile
> > >> >> [INFO] +- com.googlecode.json-simple:json-simple:jar:1.1:compile
> > >> >> [INFO] +- org.apache.hadoop:hadoop-core:jar:0.20.205.0:compile
> > >> >> [INFO] |  +- org.apache.commons:commons-math:jar:2.1:compile
> > >> >> [INFO] |  +- tomcat:jasper-runtime:jar:5.5.12:compile
> > >> >> [INFO] |  +- tomcat:jasper-compiler:jar:5.5.12:compile
> > >> >>
> > >> >> I tried to remove all the dependencies and added the hadoop/hbase
> > >> >> dependencies (by hand) in a system scope. The result is a jasper
> free
> > >> >> build, that doesn't load the Root resource classes and Provider
Ahmed Fathalla
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB