tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Tony Dahbura <t...@dahbura.com>
Subject help with custom realm
Date Fri, 31 Jan 2003 05:12:06 GMT
Team:
I have written a custom realm package for some folks that have been
using it since tomcat 4.0.x through 4.1.  When they try to use the realm
package with 4.1.18 we get the following errors:

Jan 30, 2003 1:01:07 PM org.apache.commons.modeler.Registry getRegistry
INFO: Creating new Registry instance
Jan 30, 2003 1:01:09 PM org.apache.commons.modeler.Registry getServer
INFO: Creating MBeanServer
Jan 30, 2003 1:01:12 PM org.apache.coyote.http11.Http11Protocol init
INFO: Initializing Coyote HTTP/1.1 on port 8080
ServerLifecycleListener: createMBeans: MBeanException
java.lang.Exception: ManagedBean is not found with LDAPRealm
        at
org.apache.catalina.mbeans.MBeanUtils.createMBean(MBeanUtils.java:614)
        at
org.apache.catalina.mbeans.ServerLifecycleListener.createMBeans(ServerLi

fecycleListener.java:574)
        at
org.apache.catalina.mbeans.ServerLifecycleListener.createMBeans(ServerLi

fecycleListener.java:783)
        at
org.apache.catalina.mbeans.ServerLifecycleListener.createMBeans(ServerLi

fecycleListener.java:751)
        at
org.apache.catalina.mbeans.ServerLifecycleListener.createMBeans(ServerLi

fecycleListener.java:339)
        at
org.apache.catalina.mbeans.ServerLifecycleListener.lifecycleEvent(Server

LifecycleListener.java:206)
        at
org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSu

pport.java:166)
        at
org.apache.catalina.core.StandardServer.start(StandardServer.java:2182)
        at org.apache.catalina.startup.Catalina.start(Catalina.java:512)

        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(NativeMethodAccessorImpl.jav

a:39)
        at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor

Impl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:324)
        at
org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:203)
Starting service Tomcat-Standalone
Apache Tomcat/4.1.18
Jan 30, 2003 1:01:30 PM org.apache.coyote.http11.Http11Protocol start
INFO: Starting Coyote HTTP/1.1 on port 8080
Jan 30, 2003 1:01:30 PM org.apache.jk.common.ChannelSocket init
INFO: JK2: ajp13 listening on /0.0.0.0:8009
Jan 30, 2003 1:01:30 PM org.apache.jk.server.JkMain start
INFO: Jk running ID=0 time=33/75
config=/opt/tomcat/4.1.18/conf/jk2.properties

I have appeared to trace this to my realm not having an entry in the
mbeans-descriptors.xml file.  This file appears to get wrapped into the
release?  How can I still provide folks with a realm module and not have
these errors show up or get the definition added to the file when they
download pre-compiled copies of tomcat?

Any help is greatly appreciated.
Tony


Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message