Re: JMX Support in Tomcat 4
On Wednesday 13 February 2002 04:11, Remy Maucherat wrote: On Tue, 12 Feb 2002, Remy Maucherat wrote: What could be done is maybe to write a (complex) tag library, which would ease the process of writing admin pages which would manipulate MBeans. Of course, that's quite a bit harder than writing custom admin pages, so I can understand the rationale behind that from a dev schedule standpoint ;-) To get such a tag library started, there's an attribute tag in the admin webapp (HEAD branch) that displays a named attribute from a named MBean. It would certainly make sense to abstract this out into a general MBean manipulation tag library (perhaps in jakarta-taglibs?). Yes, that would be a good starting point. The taglib is IMO the only satisfactory solution, as the application needs to be able to decide of the LnF of the admin app, as well as how the beans should be organized / presented (for example, the Tomcat admin webapp uses a tree, but other applications may do something different altogether). The only problem is that a significant part of the development would still need to be done by the application (it's not a your HTML admin interface in 5 mins type of deal). jakarta-taglibs looks like the right home for this, but I'd like to hear from Carlos to know how he plans to implement it. Hi It is in our TODO list a collection of taglibs, and that's the place where I see a convergence between Tomcat and OpenJMX. I agree that a generalized admin app won't be too useable/useful, but the basic building blocks can be common. We haven't progressed on this but I should start working on that soon. I'd like to have them in OpenJMX, but if I'm not the main contributor I don't see any problems having them in jakarta-taglibs. We can build our admin app out of them later Regards Remy -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: JMX Support in Tomcat 4
Hi Craig, Well, I grabbed last nights build and as you had indicated, I now see two Listener elements in server.xml that should be un-commented to enable jmx support in tomcat. I can now get tomcat to start (thought not without some ugly stack traces thrown to stdout) and I can successfully login to the admin app. After that, I dont get much further without getting javax.servlet.UnavailableException: MBeanServer is not available being thrown all over the place. I'm going to grab a snapshot of the code and try and wrap my mind around this one. However, I was wondering if you might be able to comment on this part of catalina and give some insight as to where its going in terms of functionality (will it be the 'full meal deal' in terms of server admin and webapp admin???) and what release version it may be targeted for? I'm very interested in this part of the app and would be willing to help out where I could. Thanks! Mark - Original Message - From: Craig R. McClanahan [EMAIL PROTECTED] To: Tomcat Developers List [EMAIL PROTECTED] Sent: Monday, February 11, 2002 3:11 PM Subject: Re: JMX Support in Tomcat 4 On Mon, 11 Feb 2002, mark wrote: Date: Mon, 11 Feb 2002 14:25:15 -0500 From: mark [EMAIL PROTECTED] Reply-To: Tomcat Developers List [EMAIL PROTECTED] To: Tomcat Developers List [EMAIL PROTECTED] Subject: Re: JMX Support in Tomcat 4 Hi Craig, Thanks for the reply! Please see comments inline: - Original Message - From: Craig R. McClanahan [EMAIL PROTECTED] To: Tomcat Developers List [EMAIL PROTECTED] Sent: Monday, February 11, 2002 11:02 AM Subject: Re: JMX Support in Tomcat 4 On Mon, 11 Feb 2002, mark wrote: Date: Mon, 11 Feb 2002 10:37:39 -0500 From: mark [EMAIL PROTECTED] Reply-To: Tomcat Developers List [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: JMX Support in Tomcat 4 Hello All, Just grabbed one of the tomcat 4 nightly builds (feb10) in an effort to explore the JMX support and some of the new admin features and am not having much luck. I unpacked it, uncommented the line to add the JMX listener in server.xml and after executing the start script, I end up with the error message below, any ideas? What is it looking for in terms of a 'userDatabase' and where should this be located? A couple of things to check: * There should have been two Listener elements that you uncommented, not just one. Was that the case? I only see one as follows: !-- Uncomment this entry to enable JMX MBeans support -- Listener className=org.apache.catalina.mbeans.ServerLifecycleListener debug=0/ I'm using the nightly build dated: 20020211 Ah ... checked my build logs and that build is corrupted :-(. It should be fixed in tonight's build (20020212). Craig -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: JMX Support in Tomcat 4
On Tuesday 12 February 2002 17:41, mark wrote: Hi I'm one of developers of OpenJMX. We will be developing in OpenJMX an admin app for JMX applications inside web containers. I wonder whether Tomcat will be doing exactly the same (A general JMX admin app) or a specific admin tool for Tomcat only. Anyway I'd be interested to collaborate specially if it can benefit both OpenJMX and Tomcat Regards Carlos Quiroz Hi Craig, Well, I grabbed last nights build and as you had indicated, I now see two Listener elements in server.xml that should be un-commented to enable jmx support in tomcat. I can now get tomcat to start (thought not without some ugly stack traces thrown to stdout) and I can successfully login to the admin app. After that, I dont get much further without getting javax.servlet.UnavailableException: MBeanServer is not available being thrown all over the place. I'm going to grab a snapshot of the code and try and wrap my mind around this one. However, I was wondering if you might be able to comment on this part of catalina and give some insight as to where its going in terms of functionality (will it be the 'full meal deal' in terms of server admin and webapp admin???) and what release version it may be targeted for? I'm very interested in this part of the app and would be willing to help out where I could. Thanks! Mark - Original Message - From: Craig R. McClanahan [EMAIL PROTECTED] To: Tomcat Developers List [EMAIL PROTECTED] Sent: Monday, February 11, 2002 3:11 PM Subject: Re: JMX Support in Tomcat 4 On Mon, 11 Feb 2002, mark wrote: Date: Mon, 11 Feb 2002 14:25:15 -0500 From: mark [EMAIL PROTECTED] Reply-To: Tomcat Developers List [EMAIL PROTECTED] To: Tomcat Developers List [EMAIL PROTECTED] Subject: Re: JMX Support in Tomcat 4 Hi Craig, Thanks for the reply! Please see comments inline: - Original Message - From: Craig R. McClanahan [EMAIL PROTECTED] To: Tomcat Developers List [EMAIL PROTECTED] Sent: Monday, February 11, 2002 11:02 AM Subject: Re: JMX Support in Tomcat 4 On Mon, 11 Feb 2002, mark wrote: Date: Mon, 11 Feb 2002 10:37:39 -0500 From: mark [EMAIL PROTECTED] Reply-To: Tomcat Developers List [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: JMX Support in Tomcat 4 Hello All, Just grabbed one of the tomcat 4 nightly builds (feb10) in an effort to explore the JMX support and some of the new admin features and am not having much luck. I unpacked it, uncommented the line to add the JMX listener in server.xml and after executing the start script, I end up with the error message below, any ideas? What is it looking for in terms of a 'userDatabase' and where should this be located? A couple of things to check: * There should have been two Listener elements that you uncommented, not just one. Was that the case? I only see one as follows: !-- Uncomment this entry to enable JMX MBeans support -- Listener className=org.apache.catalina.mbeans.ServerLifecycleListener debug=0/ I'm using the nightly build dated: 20020211 Ah ... checked my build logs and that build is corrupted :-(. It should be fixed in tonight's build (20020212). Craig -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: JMX Support in Tomcat 4
On Tue, 12 Feb 2002, mark wrote: Date: Tue, 12 Feb 2002 10:41:04 -0500 From: mark [EMAIL PROTECTED] Reply-To: Tomcat Developers List [EMAIL PROTECTED] To: Tomcat Developers List [EMAIL PROTECTED] Subject: Re: JMX Support in Tomcat 4 Hi Craig, Well, I grabbed last nights build and as you had indicated, I now see two Listener elements in server.xml that should be un-commented to enable jmx support in tomcat. I can now get tomcat to start (thought not without some ugly stack traces thrown to stdout) and I can successfully login to the admin app. After that, I dont get much further without getting javax.servlet.UnavailableException: MBeanServer is not available being thrown all over the place. I'm going to grab a snapshot of the code and try and wrap my mind around this one. However, I was wondering if you might be able to comment on this part of catalina and give some insight as to where its going in terms of functionality (will it be the 'full meal deal' in terms of server admin and webapp admin???) and what release version it may be targeted for? I'm very interested in this part of the app and would be willing to help out where I could. In my environment, the only actions required to run the admin app are: * Include either the JMX RI's jmx.jar or the OpenJMX project's openjmx.jar (from the 1.0-beta-2 release; earlier ones had bugs) in $CATALINA_HOME/server/lib. * Uncomment the two listener entries in $CATALINA_HOME/conf/server.xml * Add a user with the admin role in $CATALINA_HOME/tomcat-users.xml and I can start up Tomcat with no exception messages, and log in to the admin application (http://localhost:8080/admin/). Getting any further on your problem is going to require seeing the actual stack traces ... W.R.T. the admin app's goals, the intent is that it will be a full meal deal for managing the entire contents of server.xml -- essentially every internal object that is represented by an XML element in the server.xml file (plus some that Catalina creates internally at startup time) are also available internally as MBeans that can be manipulated. Right now, we're focusing on the screens that correspond to standard components that come with Tomcat -- the ones that correspond to the Tomcat-Standalone service in the default file. You've probably seen commits from Manveen on this -- she is working her way down the component hierarchy tree from top to bottom. Big things that are outstanding: * Finishing the bottom leafs of the standard component tree. * Enabling all the create and destroy actions that are required. * Global JNDI resource configuration for resources that Tomcat already knows about (such as the UserDatabase object, JDBC connection pools, and so on). * Supporting the component hierarchy in the Tomcat-Apache service (which is slightly different -- for example, there is no Host element here). * Supporting user-defined Listener, Logger, Manager, Realm, and Valve components in some generic fashion so that the manageable properties can be captured. * Saving the resulting configuration information back to server.xml again (right now, the changes only happen against the running server). The initial thought was to use the save APIs of the MBeans themselves to do this, but it doesn't exist yet. * Usability testing of the UI itself, along with associated performance tweaks for hot spots. There's somewhat more detail in the original design proposals -- see http://localhost:8080/tomcat-docs/catalina/funcspecs for more info. Thanks! Mark Craig -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: JMX Support in Tomcat 4
On Tue, 12 Feb 2002, Carlos Quiroz wrote: Date: Tue, 12 Feb 2002 17:55:30 +0200 From: Carlos Quiroz [EMAIL PROTECTED] Reply-To: Tomcat Developers List [EMAIL PROTECTED] To: Tomcat Developers List [EMAIL PROTECTED] Subject: Re: JMX Support in Tomcat 4 On Tuesday 12 February 2002 17:41, mark wrote: Hi I'm one of developers of OpenJMX. We will be developing in OpenJMX an admin app for JMX applications inside web containers. I wonder whether Tomcat will be doing exactly the same (A general JMX admin app) or a specific admin tool for Tomcat only. Hello Carlos, The current thinking has been a Tomcat-specific tool. My personal belief is that it's really hard to make a high quality UI for an administrative interface in a generic way (i.e. one that doesn't know anything about the internal relationships between the components being managed) -- but I would enjoy being proven wrong if you think it's feasible. The response I just sent back to Mark's question talks about some of the goals, and has a pointer to the original design docs. Anyway I'd be interested to collaborate specially if it can benefit both OpenJMX and Tomcat I'd welcome your help, and agree that this will benefit both communities. Regards Carlos Quiroz Craig -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: JMX Support in Tomcat 4
On Tuesday 12 February 2002 17:41, mark wrote: Hi I'm one of developers of OpenJMX. We will be developing in OpenJMX an admin app for JMX applications inside web containers. I wonder whether Tomcat will be doing exactly the same (A general JMX admin app) or a specific admin tool for Tomcat only. Anyway I'd be interested to collaborate specially if it can benefit both OpenJMX and Tomcat I am very interested, as it would be very useful for projects other than Tomcat. I have tried integrating with the current administration interface (for providing some admin features for Slide), but it's clearly not designed to do that. What could be done is maybe to write a (complex) tag library, which would ease the process of writing admin pages which would manipulate MBeans. Of course, that's quite a bit harder than writing custom admin pages, so I can understand the rationale behind that from a dev schedule standpoint ;-) Remy -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: JMX Support in Tomcat 4
On Tue, 12 Feb 2002, Remy Maucherat wrote: Date: Tue, 12 Feb 2002 15:24:53 -0800 From: Remy Maucherat [EMAIL PROTECTED] Reply-To: Tomcat Developers List [EMAIL PROTECTED] To: Tomcat Developers List [EMAIL PROTECTED] Subject: Re: JMX Support in Tomcat 4 On Tuesday 12 February 2002 17:41, mark wrote: Hi I'm one of developers of OpenJMX. We will be developing in OpenJMX an admin app for JMX applications inside web containers. I wonder whether Tomcat will be doing exactly the same (A general JMX admin app) or a specific admin tool for Tomcat only. Anyway I'd be interested to collaborate specially if it can benefit both OpenJMX and Tomcat I am very interested, as it would be very useful for projects other than Tomcat. I have tried integrating with the current administration interface (for providing some admin features for Slide), but it's clearly not designed to do that. What could be done is maybe to write a (complex) tag library, which would ease the process of writing admin pages which would manipulate MBeans. Of course, that's quite a bit harder than writing custom admin pages, so I can understand the rationale behind that from a dev schedule standpoint ;-) To get such a tag library started, there's an attribute tag in the admin webapp (HEAD branch) that displays a named attribute from a named MBean. It would certainly make sense to abstract this out into a general MBean manipulation tag library (perhaps in jakarta-taglibs?). Remy Craig -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: JMX Support in Tomcat 4
On Tue, 12 Feb 2002, Remy Maucherat wrote: What could be done is maybe to write a (complex) tag library, which would ease the process of writing admin pages which would manipulate MBeans. Of course, that's quite a bit harder than writing custom admin pages, so I can understand the rationale behind that from a dev schedule standpoint ;-) To get such a tag library started, there's an attribute tag in the admin webapp (HEAD branch) that displays a named attribute from a named MBean. It would certainly make sense to abstract this out into a general MBean manipulation tag library (perhaps in jakarta-taglibs?). Yes, that would be a good starting point. The taglib is IMO the only satisfactory solution, as the application needs to be able to decide of the LnF of the admin app, as well as how the beans should be organized / presented (for example, the Tomcat admin webapp uses a tree, but other applications may do something different altogether). The only problem is that a significant part of the development would still need to be done by the application (it's not a your HTML admin interface in 5 mins type of deal). jakarta-taglibs looks like the right home for this, but I'd like to hear from Carlos to know how he plans to implement it. Remy -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
