I fixed it. After downloading Tomcat's source code and then walking through the API and source, I was able to get my specialized DomRealm up and running without errors. There is still a tiny problem with non-page based logins though (Craig could maybe offer some help? ;-)
Initially, I thought about importing all of the MBean classes and force feeding the Registry within the Realm constructor, but as I continued to look at the source..... JMX uses an XML configuration file located at: /org/apache/catalina/mbeans/mbeans-descriptors.xml So, after walking through the VERY LARGE xml document, I was able to add my own bean descriptor and then save the mbeans-descriptor.xml to: $CATALINA_HOME/server/classes/org/apache/...../mbeans-descriptors.xml The only problem I can think of is that you will have to pull the new descriptor with each release and add your stuff in each time. I don't really get JMX, it just seams like an archaic version of BeanUtils? Jacob Hookom Comprehensive Computer Science Student University of Wisconsin, Eau Claire | -----Original Message----- | From: Jacob Hookom [mailto:[EMAIL PROTECTED]] | Sent: Thursday, September 05, 2002 10:39 PM | To: 'Tomcat Users List' | Subject: RE: [Realm] MBeanException | | Thanks, although I'm still in the same boat as you. | | I tried commenting out the listeners, but all it did was hide the | errors. The Common's model code and the Mbean API are sparsely | commented :-( | | I did add some System.outs to the Realm and the console reads: | | INFO: Creating MBeanServer | INITIALIZING DOMREALM | ..... | ServerLifeCycleListener: createMBeans: MBeanException | java.lang.Exception: ManagedBean is not found with DomRealm | ....... | Starting service Tomcat-Standalone | ...... | STARTING DOMREALM | ...... | | I am able to use my realm to authenticate for $ROOT/admin via web page, | but authentication for the manager shows a blank page. | | -Jacob | | | | -----Original Message----- | | From: Robert Parker [mailto:[EMAIL PROTECTED]] | | Sent: Thursday, September 05, 2002 10:22 PM | | To: 'Tomcat Users List' | | Subject: RE: [Realm] MBeanException | | | | Members Equity Email System | | I have a similar problem... I found an earlier post which suggested | | commenting out the server lifecyle listeners. The post seemed to imply | | that | | it was a JMX classloading type issue. So try commenting out the | | listeners... | | This did not work for me, but I don't have exactly the same problem. | | | | regards | | | | Rob | | | | -----Original Message----- | | From: Jacob Hookom [mailto:[EMAIL PROTECTED]] | | Sent: Friday, 6 September 2002 12:39PM | | To: Tomcat Users List | | Subject: [Realm] MBeanException | | | | | | Hello, | | | | I've created a Realm that extends RealmBase, but now I'm getting an | | exception at startup from the ServerLifecycleListener. | | | | I'm running W2K, 4.1.9 and JDK 1.4 | | | | My class DomRealm extends RealmBase and both the start and stop are | | overridden, but do call super.start() and super.end(). The jar | | containing DomRealm and DomPrincipal are within $CATALINA/server/lib | | | | Here is the exception: | | | | INFO: Initializing Coyote HTTP/1.1 on port 8080 | | ServerLifecycleListener: createMBeans: MBeanException | | java.lang.Exception: ManagedBean is not found with DomRealm | | at | | org.apache.catalina.mbeans.MBeanUtils.createMBean(MBeanUtils.java:616 | | ) | | at | | org.apache.catalina.mbeans.ServerLifecycleListener.createMBeans(Serve | | rLifecycleListener.java:527) | | at | | org.apache.catalina.mbeans.ServerLifecycleListener.createMBeans(Serve | | rLifecycleListener.java:722) | | at | | org.apache.catalina.mbeans.ServerLifecycleListener.createMBeans(Serve | | rLifecycleListener.java:690) | | at | | org.apache.catalina.mbeans.ServerLifecycleListener.createMBeans(Serve | | rLifecycleListener.java:329) | | at | | org.apache.catalina.mbeans.ServerLifecycleListener.lifecycleEvent(Ser | | verLifecycleListener.java:206) | | at | | org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(Lifecycl | | eSupport.java:166) | | at | | org.apache.catalina.core.StandardServer.start(StandardServer.java:218 | | 1) | | at | org.apache.catalina.startup.Catalina.start(Catalina.java:510) | | at | | org.apache.catalina.startup.Catalina.execute(Catalina.java:400) | | at | | org.apache.catalina.startup.Catalina.process(Catalina.java:180) | | at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) | | at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) | | at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown | | Source) | | at java.lang.reflect.Method.invoke(Unknown Source) | | at | | org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:203) | | Starting service Tomcat-Standalone | | | | Any help would be apprechiated! | | | | -Jacob | | | | | | --- | | Outgoing mail is certified Virus Free. | | Checked by AVG anti-virus system (http://www.grisoft.com). | | Version: 6.0.381 / Virus Database: 214 - Release Date: 8/2/2002 | | | | | | | | -- | | To unsubscribe, e-mail: | | <mailto:[EMAIL PROTECTED]> | | For additional commands, e-mail: | | <mailto:[EMAIL PROTECTED]> | | | | --- | | Incoming mail is certified Virus Free. | | Checked by AVG anti-virus system (http://www.grisoft.com). | | Version: 6.0.381 / Virus Database: 214 - Release Date: 8/2/2002 | | | | | | --- | Outgoing mail is certified Virus Free. | Checked by AVG anti-virus system (http://www.grisoft.com). | Version: 6.0.381 / Virus Database: 214 - Release Date: 8/2/2002 | | | | -- | To unsubscribe, e-mail: <mailto:tomcat-user- | [EMAIL PROTECTED]> | For additional commands, e-mail: <mailto:tomcat-user- | [EMAIL PROTECTED]> | | --- | Incoming mail is certified Virus Free. | Checked by AVG anti-virus system (http://www.grisoft.com). | Version: 6.0.381 / Virus Database: 214 - Release Date: 8/2/2002 | --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.381 / Virus Database: 214 - Release Date: 8/2/2002 -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
