Thank you for your answer, R�my. The problem is not pressing, it was mainly
out of curiousity that I was asking this question. What puzzles me is that
judging from the source in org.apache.jk.common.JkMX#loadAdapter the warning
issued seems to indicate that tomcat failed to load "com.sun.jd...", well,
the HTTP adaptor shipped in Sun's RI, and which is definitely in
common/lib/. IIRC, loadAdaptor() does a
Thread.currentThread().getContextClassloader().loadClass("com.sun....")
which by all means should succeed, yet does not. Strange.

Olaf Bergner

> -----Original Message-----
> From: Remy Maucherat [mailto:remm@(protected)]
> Sent: Tuesday, December 09, 2003 5:30 PM
> To: Tomcat Users List
> Subject: Re: Connecting to tomcat 5.0.16 via MC4J/XtremeJ
>
>
> Olaf Bergner wrote:
> > I have been trying to connect to tomcat 5.0.16 via MC4J and XtremeJ - a
> > management-console for Eclipse - in order to access tomcat's
> MBean server.
> > Adapting instructins found in an article targeted at tomcat 4.1
> I tried the
> > following:
> >
> > 1) Edit jk2.properties under conf/ to contain the line 'mx.port=9000'
> >
> > 2) Drop mx4j-jmx.jar, mx4j-tools.jar and log4j-1.2.7.jar into
> common/lib.
> >
> > In step 2 I have also tried SUN's jmxri 1.0.1 and 1.2.1.
> However, I always
> > get
> >
> > 09.12.2003 16:43:57 org.apache.coyote.http11.Http11Protocol start
> > INFO: Starting Coyote HTTP/1.1 on port 8080
> > 09.12.2003 16:43:57 org.apache.jk.common.ChannelSocket init
> > INFO: JK2: ajp13 listening on /0.0.0.0:8009
> > 09.12.2003 16:43:57 org.apache.jk.common.JkMX loadAdapter
> > WARNUNG: No adaptors were loaded but mx.enabled was defined.
> > 09.12.2003 16:43:57 org.apache.jk.common.JkMX init
> >
> > and cannot connect to tomcat 5.0.16 via XtremeJ/MC4J. The exact same
> > approach used to work in tomcat 5.0.12. Any ideas?
>
> I don't know. Maybe Bill or Henri have the answer.
>
> This is proprietary, though. I plan to add JSR 160 support built in in a
> future release (it will be a server listener you have to uncomment in
> server.xml), which should solve that kind of problems. At least as soon
> as clients adopt JSR 160, which should happen very quickly.
>
> --
> xxxxxxxxxxxxxxxxxxxxxxxxxxxxx
> R�my Maucherat
> Senior Developer & Consultant
> JBoss Group (Europe) S�RL
> xxxxxxxxxxxxxxxxxxxxxxxxxxxxx
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tomcat-user-unsubscribe@(protected)
> For additional commands, e-mail: tomcat-user-help@(protected)
>


---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@(protected)
For additional commands, e-mail: tomcat-user-help@(protected)