Return-Path: 
 <tomcat-dev-return-25037-qmlist-jakarta-archive-tomcat-dev=nagoya.apache.org@jakarta.apache.org>
Delivered-To: apmail-jakarta-tomcat-dev-archive@apache.org
Received: (qmail 6268 invoked from network); 1 Feb 2003 16:04:59 -0000
Received: from exchange.sun.com (192.18.33.10)
  by daedalus.apache.org with SMTP; 1 Feb 2003 16:04:59 -0000
Received: (qmail 527 invoked by uid 97); 1 Feb 2003 16:06:28 -0000
Delivered-To: qmlist-jakarta-archive-tomcat-dev@nagoya.betaversion.org
Received: (qmail 520 invoked from network); 1 Feb 2003 16:06:28 -0000
Received: from daedalus.apache.org (HELO apache.org) (208.185.179.12)
  by nagoya.betaversion.org with SMTP; 1 Feb 2003 16:06:28 -0000
Received: (qmail 5330 invoked by uid 500); 1 Feb 2003 16:04:49 -0000
Mailing-List: contact tomcat-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:tomcat-dev-unsubscribe@jakarta.apache.org>
List-Subscribe: <mailto:tomcat-dev-subscribe@jakarta.apache.org>
List-Help: <mailto:tomcat-dev-help@jakarta.apache.org>
List-Post: <mailto:tomcat-dev@jakarta.apache.org>
List-Id: "Tomcat Developers List" <tomcat-dev.jakarta.apache.org>
Reply-To: "Tomcat Developers List" <tomcat-dev@jakarta.apache.org>
Delivered-To: mailing list tomcat-dev@jakarta.apache.org
Received: (qmail 5317 invoked from network); 1 Feb 2003 16:04:48 -0000
Received: from curacao.dahbura.com (66.54.32.57)
  by daedalus.apache.org with SMTP; 1 Feb 2003 16:04:48 -0000
Received: (qmail 17206 invoked from network); 1 Feb 2003 15:52:44 -0000
Received: from unknown (HELO dahbura.com) (216.112.245.219)
  by 0 with SMTP; 1 Feb 2003 15:52:44 -0000
Message-ID: <3E3BF412.96DB5498@dahbura.com>
Date: Sat, 01 Feb 2003 11:21:38 -0500
From: Tony Dahbura <tony@dahbura.com>
X-Mailer: Mozilla 4.7 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Tomcat Developers List <tomcat-dev@jakarta.apache.org>
Subject: Re: help with custom realm
References: <3E3A05A6.8E3AFC56@dahbura.com> <3E3ABA7D.9050803@apache.org>
Content-Type: multipart/alternative;
 boundary="------------FB34ECB1DDD1A7884D3CC062"
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N

--------------FB34ECB1DDD1A7884D3CC062
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Amy:
Thanks for the info.  I saw some comments in the server.xml file but am not
sure how to declare the entry in the server.xml file.

<!-- Comment these entries out to disable JMX MBeans support -->
<!-- You may also configure custom components (e.g. Valves/Realms) by
       including your own mbean-descriptor file(s), and setting the
       "descriptors" attribute to point to a ';' seperated list of paths
       (in the ClassLoader sense) of files to add to the default list.
       e.g. descriptors="/com/myfirm/mypackage/mbean-descriptor.xml"
  -->
<Listener className="org.apache.catalina.mbeans.ServerLifecycleListener"
            debug="0"/>
<Listener
className="org.apache.catalina.mbeans.GlobalResourcesLifecycleListener"
            debug="0"/>


Do I want to add the descriptors entry to ServerLifecycleListener or the
GlobalResourcesLifecycleListener?

Also is the pathing based on a root of tomcat home? or the directory the
server xml file resides in?

Thanks,
Tony


Amy Roh wrote:

> Tony,
>
> Tony Dahbura wrote:
> > 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?
>
> You can add MBean description for your custom realm to
> mbeans-descriptors.xml file similar to other Catalina Realms or you can
> also configure your custom components (e.g. Valves/Realms) by including
> your own mbean-descriptor file(s), and setting the "descriptors"
> attribute to point to a ';' seperated list of paths(in the ClassLoader
> sense) of files to add to the default list.  e.g.
> descriptors="/com/myfirm/mypackage/mbean-descriptor.xml in server.xml.
> This is also documented in server.xml right before
> ServerLifecycleListener definition.
>
> Hope this helps.
> Amy
>
> >
> > Any help is greatly appreciated.
> > Tony
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org

--------------FB34ECB1DDD1A7884D3CC062--