Anita,
I agree it would be nice to have these statistic interfaces implemented
so we can provide performance data. IIRC somebody created a patch that
uses ServletStats and I created an EJBModuleStats for the EJB Server
portlet patch I submitted a few months ago. I’m not sure if this is even
required for JEE 5. I assume it’s not because we didn’t implement it for
J2EE 1.4. We can definitely put cycles to this but I personally wanted
to work on the JEE 5 compliance issues first so we can make tiny steps
to our JEE 5 goals. If you want to start working on JSR 77 performance
monitoring you can go ahead.
Best wishes,
chris
anita kulshreshtha wrote:
Chris,
As you said, there is not much to do in upgrading JSR77 from 1.0 to
1.1. However it would be nice to have some of the missing things
implemented in 1.0. We could provide implementation of the following
interfaces:
EJBStats.java
EntityBeanStats.java
JCAConnectionPoolStats.java
JCAConnectionStats.java
JCAStats.java
JDBCConnectionPoolStats.java
JDBCConnectionStats.java
JDBCStats.java
JMSConnectionStats.java
JMSConsumerStats.java
JMSEndpointStats.java
JMSProducerStats.java
JMSSessionStats.java
JMSStats.java
JTAStats.java
JVMStats.java
JavaMailStats.java
MessageDrivenBeanStats.java
ServletStats.java
SessionBeanStats.java
StatefulSessionBeanStats.java
StatelessSessionBeanStats.java
URLStats.java
Some of these interfaces might be already implemented. I am aware of
JVMStatsImpl. In that case we should enable the 'stastisticsProvider'
attribute of the ManagedObject.
Thanks,
Anita
*/"Christopher M. Cardona" <[EMAIL PROTECTED]>/* wrote:
I’m currently investigating what it would take to update our J2EE
Management (JSR 77) implementation for compliance with JEE 5 in
Geronimo. Looking at the changes between spec releases 1.0 (June 18,
2002) and 1.1 (June 22, 2006) there are 4 items that changed:
1. JSR77.4.2.1.3 will be/ changed from "sequence" to/
"sequenceNumber" -
This is just a typo error change.
2. JSR77.3.5.0.1 the deploymentDescriptor attribute must provide a
full
deployment descriptor based on any partial deployment descriptor plus
deployment annotations.
3. JSR77.9.1 J2EE Management CIM. The Managed Object Format (MOF) and
UML representation of the model are available from the Distributed
Management Task Force (DMTF) web site:
http://www.dmtf.org/standards/cim
4. JSR77.9.6 Appendix (CIM - Common Information Model) pages
190-214 removed
Here’s the link to the spec change log:
http://jcp.org/aboutJava/communityprocess/maintenance/jsr077/JSR77_MR.html
My first question is do we even have to update our current JSR 77
implementation to become JEE 5 compliant. If the spec changes are
all we
need to consider then it looks like only item 2 needs some attention
since item 1 is just a typo error correction and items 3 and 4 are
related to CIM which we didn’t implement. I’m not even sure if we
need
to do anything with item 2 like checking for deployment descriptor
value. Are there any other changes that I need to consider? Please
let
me know if I am missing anything. Any suggestions, ideas, and
concerns
are welcome.
Thanks,
chris
------------------------------------------------------------------------
How low will we go? Check out Yahoo! Messenger’s low PC-to-Phone call
rates.
<http://us.rd.yahoo.com/mail_us/taglines/postman8/*http://us.rd.yahoo.com/evt=39663/*http://voice.yahoo.com>
