------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
Can I deploy the 1.5 monitoring functionality into mx4j or is this only> available through the jdk 1.5 jmx agent?>
If yes, what are the names of those mbeans?
I'm not sure what you mean. If you use J2SE 5 then you're not using MX4J (unless you put mx4j in the bootclasspath), therefore you will use J2SE JMX monitor with J2SE JMX implementation. If you put MX4J in the classpath, then you will use MX4J JMX monitor with MX4J JMX implementation.
If no, can I use jdk1.5's jmx agent and tell it to start an rmiregistry> (that is the connection I'm using) programmatically, as in mx4j:>
// Register and start the rmiregistry MBean, needed by JSR 160> RMIConnectorServer> ObjectName namingName = ObjectName.getInstance("naming:type=rmiregistry");> mbeanServer.createMBean("mx4j.tools.naming.NamingService", namingName,> null);> mbeanServer.invoke(namingName, "start", null, null);>
I'm using mx4j 3.01.
Yes, this is possible. NamingService is a portable MBean across JMX implementations, so just put mx4j-tools.jar in the classpath of your J2SE 5 application, and everything will work.
Simon
------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_ide95&alloc_id396&op=click
Torsten Uhlmann 13 March 2005 21:07:58 [ permanent link ]
Thanks for your help!
Well JMX is a new target for me and I don't really have much insight in the available mbeans.
I've built a Server application using Spring and a client application using Eclipse RCP. As a communication platform I'm using JMX with just a few simple MBeans and Notification. And yes, I'm using j2se 1.5 on both sides with mx4j on the server side. I didn't know mx4j provides MBeans that can monitor a JVM the way the tiger integrated can. I just thought it might be a good feature to provide a way to look at the server and see how it's doing (and it makes testing for memory leaks etc. easier).
Again, thanks for your help! Torsten.
simone.bordet@hp.com wrote:
Hi,>
Can I deploy the 1.5 monitoring functionality into mx4j or is this only>>available through the jdk 1.5 jmx agent?>>
If yes, what are the names of those mbeans?>>
I'm not sure what you mean.>If you use J2SE 5 then you're not using MX4J (unless you put mx4j in the>bootclasspath), therefore you will use J2SE JMX monitor with J2SE JMX>implementation.>If you put MX4J in the classpath, then you will use MX4J JMX monitor with>MX4J JMX implementation.>
If no, can I use jdk1.5's jmx agent and tell it to start an rmiregistry>>(that is the connection I'm using) programmatically, as in mx4j:>>
// Register and start the rmiregistry MBean, needed by JSR 160>>RMIConnectorServer>>ObjectName namingName = ObjectName.getInstance("naming:type=rmiregistry");>>mbeanServer.createMBean("mx4j.tools.naming.NamingService", namingName,>>null);>>mbeanServer.invoke(namingName, "start", null, null);>>
I'm using mx4j 3.01.>>
Yes, this is possible.>NamingService is a portable MBean across JMX implementations, so just put>mx4j-tools.jar in the classpath of your J2SE 5 application, and everything>will work.>
------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
Well JMX is a new target for me and I don't really have much > insight in the available mbeans.>
I've built a Server application using Spring and a client application > using Eclipse RCP.> As a communication platform I'm using JMX with just a few > simple MBeans and Notification.
Cool.
And yes, I'm using j2se 1.5 on both sides > with mx4j on the server side.
As I told, if you're using J2SE 5, then you're *not* using MX4J JMX implementation. But you can use all MX4J tools (bundled in mx4j-tools.jar) since all tool MBeans are portable.
I didn't know mx4j provides MBeans that can > monitor a > JVM the way the tiger integrated can.
Ah, no. I thought you were referring to javax.management.monitor.* package, which is JMX standard. MX4J does not offer any MBean to monitor the JVM. Those are only available in J2SE 5.
Simon
I just thought it might be a good > feature to provide a way to look at the server and see how it's doing > (and it makes testing for memory leaks etc. easier).>
Again, thanks for your help!> Torsten.>
simone.bordet@hp.com wrote:>
Hi,> >
Can I deploy the 1.5 monitoring functionality into mx4j or > is this only> >>available through the jdk 1.5 jmx agent?> >>
If yes, what are the names of those mbeans?> >>
I'm not sure what you mean.> >If you use J2SE 5 then you're not using MX4J (unless you put > mx4j in the> >bootclasspath), therefore you will use J2SE JMX monitor with J2SE JMX> >implementation.> >If you put MX4J in the classpath, then you will use MX4J JMX > monitor with> >MX4J JMX implementation.> >
If no, can I use jdk1.5's jmx agent and tell it to start an > rmiregistry> >>(that is the connection I'm using) programmatically, as in mx4j:> >>
// Register and start the rmiregistry MBean, needed by JSR 160> >>RMIConnectorServer> >>ObjectName namingName = > ObjectName.getInstance("naming:type=rmiregistry");> >>mbeanServer.createMBean("mx4j.tools.naming.NamingService", > namingName,> >>null);> >>mbeanServer.invoke(namingName, "start", null, null);> >>
I'm using mx4j 3.01.> >>
Yes, this is possible.> >NamingService is a portable MBean across JMX > implementations, so just put> >mx4j-tools.jar in the classpath of your J2SE 5 application, > and everything> >will work.> >
Simon> >
-------------------------------------------------------> >SF email is sponsored by - The IT Product Guide> >Read honest & candid reviews on hundreds of IT Products from > real users.> >Discover which products truly live up to the hype. Start reading now.> >http://ads.osdn.com/?ad_ide95&alloc_id396&op=click> >_______________________________________________> >Mx4j-user mailing list> >Mx4j-user@lists.sourceforge.net> >https://lists.sourceforge.net/lists/listinfo/mx4j-user> >
------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_ide95&alloc_id396&op=click
Torsten Uhlmann 14 March 2005 10:53:28 [ permanent link ]
Hi,
no, I use MX4J because it's in the classpath and I use the property -Djavax.management.builder.initial=mx4j.server.MX4JMBeanServerBuilder
And I guess I have decided I'll stick with MX4J.
In addition I'm enabling the j2se JMX Agent through -Dcom.sun.management.jmxremote and be able to watch my server during development cycle. I don't think the customers the product is targeted for will use this feature. Maybe I find a way to manage those MXBeans through MX4J and then monitor them through my Eclipse RCP application.
As a side note, I'm really happy with the huge amount of solutions Java has to offer! Some years ago we built a C++ distributed application which could not use CORBA and thus had to manage everything through low level socket connections. Brrr...
bye, Torsten.
Bordet, Simone wrote:
Hi, >
Well JMX is a new target for me and I don't really have much >>insight in the available mbeans.>>
I've built a Server application using Spring and a client application >>using Eclipse RCP.>>As a communication platform I'm using JMX with just a few >>simple MBeans and Notification. >>
Cool.>
And yes, I'm using j2se 1.5 on both sides >>with mx4j on the server side. >>
As I told, if you're using J2SE 5, then you're *not* using MX4J JMX>implementation.>But you can use all MX4J tools (bundled in mx4j-tools.jar) since all>tool MBeans are portable.>
I didn't know mx4j provides MBeans that can >>monitor a >>JVM the way the tiger integrated can. >>
Ah, no.>I thought you were referring to javax.management.monitor.* package,>which is JMX standard.>MX4J does not offer any MBean to monitor the JVM.>Those are only available in J2SE 5.>
Simon>
I just thought it might be a good >>feature to provide a way to look at the server and see how it's doing >>(and it makes testing for memory leaks etc. easier).>>
Again, thanks for your help!>>Torsten.>>
simone.bordet@hp.com wrote:>>
Hi,>>>
Can I deploy the 1.5 monitoring functionality into mx4j or >>>>
is this only>>
available through the jdk 1.5 jmx agent?>>>>
If yes, what are the names of those mbeans?>>>>
I'm not sure what you mean.>>>If you use J2SE 5 then you're not using MX4J (unless you put >>>
mx4j in the>>
bootclasspath), therefore you will use J2SE JMX monitor with J2SE JMX>>>implementation.>>>If you put MX4J in the classpath, then you will use MX4J JMX >>>
monitor with>>
MX4J JMX implementation.>>>
If no, can I use jdk1.5's jmx agent and tell it to start an >>>>
rmiregistry>>
(that is the connection I'm using) programmatically, as in mx4j:>>>>
// Register and start the rmiregistry MBean, needed by JSR 160>>>>RMIConnectorServer>>>>ObjectName namingName = >>>>
Yes, this is possible.>>>NamingService is a portable MBean across JMX >>>
implementations, so just put>>
mx4j-tools.jar in the classpath of your J2SE 5 application, >>>
and everything>>
will work.>>>
Simon>>>
------------------------------------------------------->>>SF email is sponsored by - The IT Product Guide>>>Read honest & candid reviews on hundreds of IT Products from >>>
------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
If you would like to report an abuse of our service, such as a spam message, please . Если Вы хотите пожаловаться на содержимое этой страницы, пожалуйста .