For these service creation events I'm addressing now to decouple JSR-77 from the core I don't see the event volume as an issue. If it is, then we need to use asynchronous events.
For all of the stats I have read about so far, the corresponding component should be an mbean with this information availble for reading via JMX so that the JSR-77 just queries the component on demand when it is requested. I agree that if you take the spec and literally create a MBean for every management object there will be an absurd number of MBeans. So what does this super MBean look like? xxxxxxxxxxxxxxxxxxxxxxxx Scott Stark Chief Technology Officer JBoss Group, LLC xxxxxxxxxxxxxxxxxxxxxxxx ----- Original Message ----- From: Scott McLaughlin To: [EMAIL PROTECTED] ; [EMAIL PROTECTED] Sent: Thursday, January 16, 2003 6:17 AM Subject: Re: [JBoss-dev] JSR-77 refactoring has begun Scott, When the original code was written we did not use JMX notifications because we were concerned that the number of notifications would be very high and might cause the server to bottle neck because of the notification volume. Is your idea to also populate the statistics using notifications? In any case I can start updating the JSR-77 classes to the final spec, then I will start working on the population of the statistics data. One other issue that was brought up on the forum relating to JSR-77 was the number of MBeans that were being created. I have started looking at the possibility of all the MBeans into a single MBean that keeps track of all the JSR-77 related information including state management and statistics. Given this single MBean my idea is all access to the JSR-77 related data with JBoss is through the MEJB, but since it is just going to delegate to the JSR-77 repository MBean, the MBean could be accessed directly if other MBeans with in JBoss required JSR-77 related data. comments always welcome, Scott McLaughlin >>> [EMAIL PROTECTED] 01/15/03 10:29PM >>> I started the refactoring of the JSR-77 layer to pull it out of the core. The initial checkin focuses on the SAR related code. The change will be to move the JSR-77 object creation out of the core deployers and components and into the JSR-77 module itself. The interaction between the two layer is vis JMX notifications. So far this has simplified both the core and the JSR-77 code. I expect this to be complete by the end of the week. Beyond that updating the classes to the JSR-77 1.0 final release and populating the statistics is what will take some work. xxxxxxxxxxxxxxxxxxxxxxxx Scott Stark Chief Technology Officer JBoss Group, LLC xxxxxxxxxxxxxxxxxxxxxxxx ------------------------------------------------------- This SF.NET email is sponsored by: A Thawte Code Signing Certificate is essential in establishing user confidence by providing assurance of authenticity and code integrity. Download our Free Code Signing guide: http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0028en _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development ------------------------------------------------------- This SF.NET email is sponsored by: Thawte.com Understand how to protect your customers personal information by implementing SSL on your Apache Web Server. Click here to get our FREE Thawte Apache Guide: http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0029en _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
