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]>
