Re: Review issues with using mx4j in WebLogic 8.1

"Simone Bordet" <[email protected]>
Newsgroups gmane.comp.java.mx4j.user
Message-ID <[email protected]>
Hi,

> I've been experimenting with using mx4j (or jmanager, or mc4j) to
> connect to mbeans registered through Spring (1.2.1), running in WebLogic
> 8.1(sp4).  I've found some of the notes that talk about the problems
> with doing this.  Referring specifically to the note written by "Roland
> Huss" on 8/5/2005, titled "Re: mx4j and weblogic problems!"
> (http://sourceforge.net/mailarchive/message.php?msg_id=12569736).  In
> this note, Roland says the following:
>
> "You could try to put mx4j.jar on the system classpath (e.g. in the
>  startup script) before weblogic jar, but for Weblogic 8.1. this must be
>  a JMX 1.0 version of mx4j. I"m afraid this won"t work either."
>
> I could use some clarification of this statement.  First of all, is
> there a JMX 1.0 version of mx4j?  I couldn't see any obvious statement
> about that on the web site.  Most importantly, what does "I'm afraid
> this won't work" mean.  Does he mean he thinks it probably won't work,
> or he knows it won't?  If this is known to not work, why does it not
> work?

I never used WL, but I guess Roland says that for versions < 9.0, you're stuck.

WL < 9.0 have or use a JMX implementation of the 1.0 version of the
JMX specification.
MX4J never implemented that version, but went directly to implementing
version 1.1 of the JMX specification.
MX4J 3.0.1 implements version 1.2.1 of the JMX specification.

Simon
-- 
http://bordet.blogspot.com


-------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid0709&bid&3057&dat1642
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.