tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Steven Mahurin <steve_mahu...@yahoo.com>
Subject Re: 5.5.28 issue when multiple services with engines named the same
Date Mon, 03 Aug 2009 02:34:21 GMT

Filip,

Yeah, I just went back and re-read the Engine config documentation. It seems as though I misunderstood
it when I read it last time.  

   "When using muliple Service elements 
    in the same Server, each Engine MUST 
    be assigned a unique name."

I was thinking it was saying each Engine had to have a unique name in the service it was defined
within...but each service can only have one so what would be the point of that statement.
:)

Thanks for the clarification.

-steve

--- On Sun, 8/2/09, Filip Hanik - Dev Lists <devlists@hanik.com> wrote:

> From: Filip Hanik - Dev Lists <devlists@hanik.com>
> Subject: Re: 5.5.28 issue when multiple services with engines named the same
> To: "Tomcat Developers List" <dev@tomcat.apache.org>
> Date: Sunday, August 2, 2009, 9:10 PM
> Hi Steven, I think the engine name
> unique per server has been there for 
> a very long time. for example the directory
> conf/Catalina/localhost/
> is
> conf/Engine name/Host name
> and not Service name, so this would make the engine unique
> 
> filip
> 
> 
> On 08/02/2009 12:16 PM, Steven Mahurin wrote:
> > I am using tomcat 5.5.27 to run a set of simple set of
> applications.  I am looking at 5.5.28 to address a
> number of security vulnerabilties.  When I tried the
> 5.5.28, we ran into an issue when two services were defined
> in server.xml, if the same engine name was used for both but
> different host names/settings, the second engine would not
> start up. This worked in 5.5.27, and the documentation
> indicates that the engine name must be unique-per-service,
> not per server.  Is this a known issue?
> >
> > I ended up just renaming the engine defined in the
> second service and it works fine.  However, this may
> cause other people issue when going to 5.5.28 from previous
> releases, and it seems to differ from the configuration
> reference.
> >
> > Note that I verified that this issue is present using
> the 5.5.28 build that Filip had as a release candidate on
> 7/24:
> > http://people.apache.org/~fhanik/tomcat/tomcat-5.5/v5.5.28/
> >
> > You should be able to reproduce this by adding a
> service definition similar to the following to the end of
> the default server.xml file (and creating a webapps-testonly
> folder in the tomcat directory):
> >
> > <Service name="testservice">
> >      <Engine name="Catalina"
> defaultHost="testpsuedohostname">
> >        <Realm
> className="org.apache.catalina.realm.UserDatabaseRealm"
> resourceName="UserDatabase" />
> >        <Host
> name="testpsuedohostname" appBase="webapps-testonly" />
> >      </Engine>
> >      <Connector port="8010"
> enableLookups="false" protocol="AJP/1.3" address="127.0.0.1"
> />
> >    </Service>
> >
> > In 5.5.27, both defined services startup
> normally.  In 5.5.28, the following trace is generated
> when the above testservice starts up:
> > INFO: Starting service testservice
> > Aug 1, 2009 2:22:19 PM
> org.apache.catalina.core.StandardEngine start
> > INFO: Starting Servlet Engine: Apache Tomcat/5.5.28
> > Aug 1, 2009 2:22:19 PM
> org.apache.catalina.connector.MapperListener
> handleNotification
> > WARNING: Error registering Host
> Catalina:type=Host,host=testpsuedohostname
> > java.lang.NullPointerException
> >      at
> org.apache.catalina.connector.MapperListener.registerHost(MapperListener.java:337)
> >      at
> org.apache.catalina.connector.MapperListener.handleNotification(MapperListener.java:218)
> >      at
> com.sun.jmx.interceptor.DefaultMBeanServerInterceptor$ListenerWrapper.handleNotification(DefaultMBeanServerInterceptor.java:1732)
> >      at
> javax.management.NotificationBroadcasterSupport.handleNotification(NotificationBroadcasterSupport.java:257)
> > ...
> >
> >
> > I haven't looked into the change that caused the
> difference, as the work around appeared to be simple (just
> rename the engine).  I believe its a bug, but haven't
> reported it yet as a bug because I wanted to make sure my
> understanding of the configuration documentation was correct
> (engine name unique-per-service vs unique-per-server).
> >
> > Thanks,
> >
> > -steve
> >
> >
> >
> >
> >
> >
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
> > For additional commands, e-mail: dev-help@tomcat.apache.org
> >
> >
> >    
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: dev-help@tomcat.apache.org
> 
> 


      

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org


Mime
View raw message