Jakarta Tomcat Newsgroup (@Basebeans.com) wrote: > Subject: Re: tomcat 4.0.2 -> 4.1.8test; problem with Realm not loading > From: Torgeir Veimo <[EMAIL PROTECTED]> > === > Remy Maucherat wrote: > >>Jakarta Tomcat Newsgroup (@Basebeans.com) wrote: >> >> >>>Subject: tomcat 4.0.2 -> 4.1.8test; problem with Realm not loading >>>From: Torgeir Veimo <[EMAIL PROTECTED]> >>> === >>>I just moved to tomcat 4.1.8-LE-jdk14 on my linux development machine, >>>and one Realm which worked flawlessly under tomcat 4.0.2 now gives an >>>exception at startup. This Realm uses special class loading; the realm >>>impl itself is in server/lib, while some classes it makes use of >>>(which also need to be visible to webapps, lives in common/lib. >>> >>>Any clues on where to look for errors? >> >> >>You can't use custom components along with the JMX features (at least >>how they're implemented in 5.0). >>You can disable the ServerLifecycleListener to solve this. > > > This is strange. specifying any of the included realm implementations > does not give this error, only my own, which extends RealmBase. I do > nothing in reference to JMX, I only triggers lifecycle events when my > realm starts. Are you saying I shouldn't do this?
Yes, I know, but the JMX code attempts to create model MBeans for all the running Catalina components. To do that, it uses the modeler (from commons), and this needs the description of the object. Remy -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
