@chuck and @martin You both helped me. Turns out that I could move all
weblogic classes in WEB-INF/lib and out of the System classloader. But
moving just weblogic.jar did not do the trick. I needed to package the
following jars from the BEA distribution into the Webapp:
weblogic.jar
wljmxclient.ja
@Chuck: Yes, I did kind of munge the bootstrap and System classloaders
together. But the problem still remains. When I remove weblogic.jar from
common/lib and my code attempts to establish a JMX connection using below:
JMXConnector connector = JMXConnectorFactory.connect(serviceURL, h);
I get the
request TOMCAT use the weblogic.management.remote package from wljmxclient.jar
instead as illustrated here:
Djmx.remote.protocol.provider.pkgs=weblogic.management.remote
and
Djava.class.path="D:\jdk1.5.0_16\lib\jconsole.jar;D:\jdk1.5.0_16\lib\tools.jar;%WL_HOME%\server\lib\wljmxclient.jar
> From: Pankaj Tandon [mailto:pankajtan...@gmail.com]
> Subject: Using JMX with Tomcat: classloading issues
>
> Because rt.jar is (probably) used by the bootstrap classloader,
> I HAVE to include weblogic.jar in the CATALINA_HOME/common/lib
> directory.
Yes, rt.jar is handled by the bootstrap cla
