I second this opinion. Our development is focused on using 2.1 since that is what is available. Although we are many months from deploying I wouldn't want to make a switch to 2.2 that late in the development. We have a requirement to be able to instrument as much as possible, so getting a handle on pool sizes, etc. would be very valuable. We have a requirement to do this through JMX, so I'm definitely up to doing some work on this. This task is actually already on my schedule for the week after next.
As for how hard it is, you just create Mbeans that monitor and manage things. As long as they can call methods that get and set the needed information you're set. There are also some very nice tools around to do some of this for you. One of the tools we are evaluating is AdventNet JMX Studio and Applications Manager. If anyone has experience with these please let me know. Ralph -----Original Message----- From: Gianugo Rabellino [mailto:[EMAIL PROTECTED] Sent: Thursday, March 04, 2004 8:28 AM To: [EMAIL PROTECTED] Subject: Re: Instrumentation, anyone? It really depends on how far we are from 2.2. I don't want to sound pessimistic, and I must confess that I'm the first one lagging behind the Fortress migration, but I have an overall feeling that we are still quite far away, and I think that we could use something ASAP. I'm no JMX expert at all, but I understand that basic JMX support can be easily "piggybacked" on existing code, as long as you're basically happy with monitoring and small management tasks: more important needs might require significant changes to the code base, so if I were to draw a plan I would say that we _might_ include some JMX code right now and that we _should_ plan JMX support for 2.2, even if that requires some refactoring. I have the feeling that a complex application like Cocoon really could use some management tools. Ciao, -- Gianugo Rabellino Pro-netics s.r.l. - http://www.pro-netics.com Orixo, the XML business alliance - http://www.orixo.com (Blogging at: http://www.rabellino.it/blog/)
