Win a copy of Re-engineering Legacy Software this week in the Refactoring forum
or Docker in Action in the Cloud/Virtualization forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

JMX -Optional or fundamental

 
HS Thomas
Ranch Hand
Posts: 3404
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Is JMX optional or fundamental to using EJBs ?
regards
 
Lasse Koskela
author
Sheriff
Posts: 11962
5
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
The EJB specification doesn't say a word about JMX (neither does the J2EE specification if I remember correctly). However, JMX is fundamental in a way because the latest application servers utilise it heavily for their internal management and often provide management services to applications through a JMX API.
 
HS Thomas
Ranch Hand
Posts: 3404
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
If you wanted to utilise JMX for mangement of your EJBs ( or management of some other side issue, I can't imagine what) would this affect how you develop the EJBs?
Thanks
[ September 01, 2003: Message edited by: HS Thomas ]
 
Lasse Koskela
author
Sheriff
Posts: 11962
5
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
It depends on 1) the application server, 2) what you want to manage, and 3) your choice (sometimes there are several ways of doing what you want to achieve).
 
HS Thomas
Ranch Hand
Posts: 3404
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Thanks Lasse,
What sorts of *things* may I want to manage using JMX which I gather are purely Message beans?
Connection pooling , that sorts of things ?
Send messages of events and report on the events ?
Can I manage concurrency between beans using JMX ?
Does this override JMS which , I think, is part of the EJB spec?
Apologies, if these questions are crass.

regards
 
Lasse Koskela
author
Sheriff
Posts: 11962
5
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
What sorts of *things* may I want to manage using JMX which I gather are purely Message beans?
Connection pooling , that sorts of things ?
Send messages of events and report on the events ?
Can I manage concurrency between beans using JMX ?

JMX MBeans are not related to EJB. An MBean may be an EJB but just as well you can "instrument" a servlet or a plain old Java object by implementing an MBean interface and registering it with the JMX server. Take a look at the white paper (first link) I've referenced further below.
Does this override JMS which , I think, is part of the EJB spec?

No, JMX does not override JMS in any way.
Here are some JMX tutorials on the web:
http://java.sun.com/products/JavaManagement/wp/
http://ejbinfo.com/ejb/01/03/06/1430214.shtml
ftp://ftp.oreilly.com/pub/conference/java2001/Oberg_jmx.ppt
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic