tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bill Barker" <wbar...@wilshire.com>
Subject Fw: [BUG] jk2 jni doesn't work
Date Thu, 19 Sep 2002 06:42:40 GMT
Erm, somehow the reply-to didn't take.

----- Original Message -----
From: "Bill Barker" <wbarker@wilshire.com>
To: "Mladen Turk" <mturk@mappingsoft.com>
Sent: Wednesday, September 18, 2002 11:08 PM
Subject: Re: [BUG] jk2 jni doesn't work


>
> ----- Original Message -----
> From: "Mladen Turk" <mturk@mappingsoft.com>
> To: "'Tomcat Developers List'" <tomcat-dev@jakarta.apache.org>
> Cc: "Bill Barker" <wbarker@wilshire.com>
> Sent: Wednesday, September 18, 2002 10:43 PM
> Subject: RE: [BUG] jk2 jni doesn't work
>
>
> > This is the classloader problem.
> >
> > Think that Bill Baker is solving this, but until then add the
> > commons-logging.jar to the loaded classes when started inprocess:
> >
> > OPT=-Djava.class.path=${TOMCAT_HOME}\bin\tomcat-jni.jar;${TOMCAT_HOME}\s
> > erver\lib\commons-logging.jar
> >
> > Adding commons-logging to the classpath solves the JNI problem.
> >
> > Bill, when can ve expect this will get solved?
> >
>
> Urm, it's really a separate issue.  Last week I converted some of the 3.3
> classes to using c-l, but trusted too much that if it compiles, then it
will
> run.  Since tonight I wanted to focus on the JSSE client-cert problem, I
> just patched the startup scripts so that the 3.3.2-dev nightly would still
> work.
>
> However, I have no problem taking a look at the Jk2 ClassLoader issue at
the
> same time that I try to work out why 3.3.2-dev broke.
>
> >
> >
> > >
> > > java.lang.NoClassDefFoundError: org/apache/commons/logging/LogFactory
> > > at org.apache.jk.apr.AprImpl.<clinit>(AprImpl.java:348)
> > > java.lang.NoClassDefFoundError
> > >
> > >
> >
> > MT.
> >
>


--
To unsubscribe, e-mail:   <mailto:tomcat-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:tomcat-dev-help@jakarta.apache.org>


Mime
View raw message