Mailing-List: contact dev-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Developers List" <dev@tomcat.apache.org>
Received-SPF: pass (nike.apache.org: local policy)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
  s=s1024; d=yahoo.com;
  h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding;
  b=MT2g1ziFbmJzVI8HfhSfF3/a5BCbYxAZSjSlSrQ2VHojl8RCopytlGJ9avZqeQeWzuz2WirIDXFsbwc65w/MBT8lmDSY3aOqUCRRUJmiwFgDjef2/rNXpyIKEdm3R+XLJKOx+aW2Fc7qVffJ52dNMuwEjul2i+x4cY0SOipgST8=;
Message-ID: <50755.44379.qm@web112508.mail.gq1.yahoo.com>
Date: Sun, 2 Aug 2009 19:34:21 -0700 (PDT)
From: Steven Mahurin <steve_mahurin@yahoo.com>
Subject: Re: 5.5.28 issue when multiple services with engines named the same
To: Tomcat Developers List <dev@tomcat.apache.org>
In-Reply-To: <4A763916.3040109@hanik.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable


Filip,

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

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

I was thinking it was saying each Engine had to have a unique name in the s=
ervice it was defined within...but each service can only have one so what w=
ould 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 s=
ame
> 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=20
> 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
>=20
> filip
>=20
>=20
> 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.=A0 I am looking at 5.5.28 to address a
> number of security vulnerabilties.=A0 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.=A0 Is this a known issue?
> >
> > I ended up just renaming the engine defined in the
> second service and it works fine.=A0 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=3D"testservice">
> >=A0 =A0 =A0 <Engine name=3D"Catalina"
> defaultHost=3D"testpsuedohostname">
> >=A0 =A0 =A0 =A0 <Realm
> className=3D"org.apache.catalina.realm.UserDatabaseRealm"
> resourceName=3D"UserDatabase" />
> >=A0 =A0 =A0 =A0 <Host
> name=3D"testpsuedohostname" appBase=3D"webapps-testonly" />
> >=A0 =A0 =A0 </Engine>
> >=A0 =A0 =A0 <Connector port=3D"8010"
> enableLookups=3D"false" protocol=3D"AJP/1.3" address=3D"127.0.0.1"
> />
> >=A0 =A0 </Service>
> >
> > In 5.5.27, both defined services startup
> normally.=A0 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=3DHost,host=3Dtestpsuedohostname
> > java.lang.NullPointerException
> >=A0 =A0 =A0 at
> org.apache.catalina.connector.MapperListener.registerHost(MapperListener.=
java:337)
> >=A0 =A0 =A0 at
> org.apache.catalina.connector.MapperListener.handleNotification(MapperLis=
tener.java:218)
> >=A0 =A0 =A0 at
> com.sun.jmx.interceptor.DefaultMBeanServerInterceptor$ListenerWrapper.han=
dleNotification(DefaultMBeanServerInterceptor.java:1732)
> >=A0 =A0 =A0 at
> javax.management.NotificationBroadcasterSupport.handleNotification(Notifi=
cationBroadcasterSupport.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).=A0 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
> >
> >
> >=A0 =A0=20
>=20
>=20
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: dev-help@tomcat.apache.org
>=20
> =0A=0A=0A      

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