You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by Uw...@t-systems.com on 2011/08/30 09:36:04 UTC
Problems with manager app under Tomcat 6.0.29
Hello,
I have an odd problem occuring while using 4 tomcat instances on the same server.
These Instances all configured to run on different ports and the application seems to run well but
the manager application does only run on the instance which is started first.
On the other instances I'll receive a strange error message in catalina.out.
The only thing I have added to the web.xml of the manager application are some new roles definitions and authorization.
INFO: Deploying configuration descriptor manager.xml
30.08.2011 09:19:41 org.apache.tomcat.util.digester.Digester endElement
SCHWERWIEGEND: End event threw exception
java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:616)
at org.apache.tomcat.util.IntrospectionUtils.callMethod1(IntrospectionUtils.java:928)
at org.apache.tomcat.util.digester.SetNextRule.end(SetNextRule.java:193)
at org.apache.tomcat.util.digester.Rule.end(Rule.java:229)
at org.apache.tomcat.util.digester.Digester.endElement(Digester.java:1138)
at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.endElement(AbstractSAXParser.java:604)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanEndElement(XMLDocumentFragmentScannerImpl.java:1750)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDriver.next(XMLDocumentFragmentScannerImpl.java:2906)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentScannerImpl.java:624)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:486)
at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:810)
at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:740)
at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:110)
at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1208)
at com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(SAXParserImpl.java:525)
at org.apache.tomcat.util.digester.Digester.parse(Digester.java:1642)
at org.apache.catalina.startup.ContextConfig.applicationWebConfig(ContextConfig.java:365)
at org.apache.catalina.startup.ContextConfig.start(ContextConfig.java:1076)
at org.apache.catalina.startup.ContextConfig.lifecycleEvent(ContextConfig.java:261)
at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:119)
at org.apache.catalina.core.StandardContext.start(StandardContext.java:4540)
at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:791)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:771)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:546)
at org.apache.catalina.startup.HostConfig.deployDescriptor(HostConfig.java:637)
at org.apache.catalina.startup.HostConfig.deployDescriptors(HostConfig.java:563)
at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:498)
at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1277)
at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:321)
at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:119)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1053)
at org.apache.catalina.core.StandardHost.start(StandardHost.java:785)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1045)
at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:445)
at org.apache.catalina.core.StandardService.start(StandardService.java:519)
at org.apache.catalina.core.StandardServer.start(StandardServer.java:710)
at org.apache.catalina.startup.Catalina.start(Catalina.java:581)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:616)
at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:289)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:414)
Caused by: java.lang.IllegalArgumentException: addChild: Child name 'Manager' is not unique
at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:781)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:771)
at org.apache.catalina.core.StandardContext.addChild(StandardContext.java:2315)
... 46 more
30.08.2011 09:19:41 org.apache.catalina.startup.ContextConfig applicationWebConfig
SEVERE: Parse error in application web.xml file at jndi:/localhost/manager/WEB-INF/web.xml
java.lang.IllegalArgumentException: addChild: Child name 'Manager' is not unique
at org.apache.tomcat.util.digester.Digester.createSAXException(Digester.java:2806)
at org.apache.tomcat.util.digester.Digester.createSAXException(Digester.java:2832)
at org.apache.tomcat.util.digester.Digester.endElement(Digester.java:1141)
at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.endElement(AbstractSAXParser.java:604)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanEndElement(XMLDocumentFragmentScannerImpl.java:1750)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDriver.next(XMLDocumentFragmentScannerImpl.java:2906)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentScannerImpl.java:624)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:486)
at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:810)
at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:740)
at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:110)
at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1208)
at com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(SAXParserImpl.java:525)
at org.apache.tomcat.util.digester.Digester.parse(Digester.java:1642)
at org.apache.catalina.startup.ContextConfig.applicationWebConfig(ContextConfig.java:365)
at org.apache.catalina.startup.ContextConfig.start(ContextConfig.java:1076)
at org.apache.catalina.startup.ContextConfig.lifecycleEvent(ContextConfig.java:261)
at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:119)
at org.apache.catalina.core.StandardContext.start(StandardContext.java:4540)
at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:791)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:771)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:546)
at org.apache.catalina.startup.HostConfig.deployDescriptor(HostConfig.java:637)
at org.apache.catalina.startup.HostConfig.deployDescriptors(HostConfig.java:563)
at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:498)
at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1277)
at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:321)
at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:119)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1053)
at org.apache.catalina.core.StandardHost.start(StandardHost.java:785)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1045)
at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:445)
at org.apache.catalina.core.StandardService.start(StandardService.java:519)
at org.apache.catalina.core.StandardServer.start(StandardServer.java:710)
at org.apache.catalina.startup.Catalina.start(Catalina.java:581)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:616)
at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:289)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:414)
30.08.2011 09:19:41 org.apache.catalina.startup.ContextConfig applicationWebConfig
SEVERE: Occurred at line 43 column 13
30.08.2011 09:19:41 org.apache.catalina.startup.ContextConfig start
SEVERE: Marking this application unavailable due to previous error(s)
30.08.2011 09:19:41 org.apache.catalina.core.StandardContext start
SEVERE: Error getConfigured
30.08.2011 09:19:41 org.apache.catalina.core.StandardContext start
SEVERE: Context [/manager] startup failed due to previous errors
30.08.2011 09:19:41 org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deploying web application directory healthcheck
30.08.2011 09:19:41 org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deploying web application directory docs
30.08.2011 09:19:41 org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deploying web application directory ROOT
30.08.2011 09:19:41 org.apache.catalina.startup.HostConfig deployDirectory
In this error message it says something about line 43 column 13.
But I have copied the same web.xml to all four instance webapps/manager/WEB-INF/ directories and as I said
on one instance it is running well.
This is the entry in it in this line.
36 <servlet>
37 <servlet-name>Manager</servlet-name>
38 <servlet-class>org.apache.catalina.manager.ManagerServlet</servlet-class>
39 <init-param>
40 <param-name>debug</param-name>
41 <param-value>2</param-value>
42 </init-param>
43 </servlet>
44 <servlet>
45 <servlet-name>HTMLManager</servlet-name>
46 <servlet-class>org.apache.catalina.manager.HTMLManagerServlet</servlet-class>
47 <init-param>
48 <param-name>debug</param-name>
49 <param-value>2</param-value>
50 </init-param>
51 </servlet>
Does anybody have a clue? Or do you need some more info?
Thanks in advance.
Mit freundlichen Grüßen / Yours sincerely
Uwe Hellmann
T-Systems International GmbH
Production CSS
GCU Large Accounts
AC Express & Logistics LT1
Gradestr. 20, 30163 Hannover
+49 511 333 - 1233 (Tel.)
+49 511 333 - 1287 (Fax)
Email: uwe.hellmann@t-systems.com<ma...@t-systems.com>
Internet: http://www.t-systems.com<http://www.t-systems.com/>
T-Systems International GmbH
Aufsichtsrat: René Obermann (Vorsitzender)
Geschäftsführung: Reinhard Clemens (Vorsitzender), Dr. Ferri Abolhassan, Ulrich Meister, Georg Pepping, Hagen Rickmann, Dietmar Wendt, Klaus Werner
Handelsregister: Amtsgericht Frankfurt am Main HRB 55933
Sitz der Gesellschaft: Frankfurt am Main
Notice: This transmittal and/or attachments may be privileged or confidential. If you are not the intended recipient, you are hereby notified that you have received this transmittal in error; any review, dissemination, or copying is strictly prohibited. If you received this transmittal in error, please notify us immediately by reply and immediately delete this message and all its attachments. Thank you.
AW: Problems with manager app under Tomcat 6.0.29
Posted by Uw...@t-systems.com.
thank you very much for your help.
I have found the problem. it was no real tomcat problem.
by accident I had copied the manager web.xml to a wrong destination so tomcat assumed that is has to start another application
with it.
- Uwe
-----Ursprüngliche Nachricht-----
Von: Hellmann, Uwe
Gesendet: Dienstag, 30. August 2011 12:44
An: users@tomcat.apache.org
Betreff: AW: Problems with manager app under Tomcat 6.0.29
there are no entries for <servlet-name>Manager</servlet-name>
currently with the exception of the defined ports in server.xml these tomcats are running with default settings.
-----Ursprüngliche Nachricht-----
Von: Konstantin Kolinko [mailto:knst.kolinko@gmail.com]
Gesendet: Dienstag, 30. August 2011 12:25
An: Tomcat Users List
Betreff: Re: Problems with manager app under Tomcat 6.0.29
2011/8/30 <Uw...@t-systems.com>:
> Thanks for the info, I checked it. There are many entries for
> <servlet-name>Manager</servlet-name>
> in webapps/manager/WEB-INF/web.xml.
And what about conf/web.xml ?
> Von: Konstantin Kolinko [mailto:knst.kolinko@gmail.com]
>
> Check that you do not have <servlet-name>Manager</servlet-name>
> 1. elsewhere in manager/WEB-INF/web.xml 2. in conf/web.xml
>
Best regards,
Konstantin Kolinko
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
AW: Problems with manager app under Tomcat 6.0.29
Posted by Uw...@t-systems.com.
there are no entries for <servlet-name>Manager</servlet-name>
currently with the exception of the defined ports in server.xml these tomcats are running with default settings.
-----Ursprüngliche Nachricht-----
Von: Konstantin Kolinko [mailto:knst.kolinko@gmail.com]
Gesendet: Dienstag, 30. August 2011 12:25
An: Tomcat Users List
Betreff: Re: Problems with manager app under Tomcat 6.0.29
2011/8/30 <Uw...@t-systems.com>:
> Thanks for the info, I checked it. There are many entries for
> <servlet-name>Manager</servlet-name>
> in webapps/manager/WEB-INF/web.xml.
And what about conf/web.xml ?
> Von: Konstantin Kolinko [mailto:knst.kolinko@gmail.com]
>
> Check that you do not have <servlet-name>Manager</servlet-name>
> 1. elsewhere in manager/WEB-INF/web.xml 2. in conf/web.xml
>
Best regards,
Konstantin Kolinko
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Problems with manager app under Tomcat 6.0.29
Posted by Konstantin Kolinko <kn...@gmail.com>.
2011/8/30 <Uw...@t-systems.com>:
> Thanks for the info, I checked it. There are many entries for <servlet-name>Manager</servlet-name>
> in webapps/manager/WEB-INF/web.xml.
And what about conf/web.xml ?
> Von: Konstantin Kolinko [mailto:knst.kolinko@gmail.com]
>
> Check that you do not have <servlet-name>Manager</servlet-name>
> 1. elsewhere in manager/WEB-INF/web.xml
> 2. in conf/web.xml
>
Best regards,
Konstantin Kolinko
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
AW: Problems with manager app under Tomcat 6.0.29
Posted by Uw...@t-systems.com.
Hello
Thanks for the info, I checked it. There are many entries for <servlet-name>Manager</servlet-name>
in webapps/manager/WEB-INF/web.xml.
But I checked in original file from tomcat.apache.org and there it is also more from them. So this could not be the failure
hence it runs under one instance fine. I have posted the complete web.xml file here, maybe I have made mistake while
adding another role?
<display-name>Tomcat Manager Application</display-name>
<description>
A scriptable management web application for the Tomcat Web Server;
Manager lets you view, load/unload/etc particular web applications.
</description>
<!-- Define the Manager Servlet
Change servlet-class to: org.apache.catalina.servlets.HTMLManagerServlet
to get a Servlet with a more intuitive HTML interface, don't change if you
have software that is expected to parse the output from ManagerServlet
since they're not compatible.
-->
<servlet>
<servlet-name>Manager</servlet-name>
<servlet-class>org.apache.catalina.manager.ManagerServlet</servlet-class>
<init-param>
<param-name>debug</param-name>
<param-value>2</param-value>
</init-param>
</servlet>
<servlet>
<servlet-name>HTMLManager</servlet-name>
<servlet-class>org.apache.catalina.manager.HTMLManagerServlet</servlet-class>
<init-param>
<param-name>debug</param-name>
<param-value>2</param-value>
</init-param>
</servlet>
<servlet>
<servlet-name>Status</servlet-name>
<servlet-class>org.apache.catalina.manager.StatusManagerServlet</servlet-class>
<init-param>
<param-name>debug</param-name>
<param-value>0</param-value>
</init-param>
</servlet>
<servlet>
<servlet-name>JMXProxy</servlet-name>
<servlet-class>org.apache.catalina.manager.JMXProxyServlet</servlet-class>
</servlet>
<!-- Define the Manager Servlet Mapping -->
<servlet-mapping>
<servlet-name>Manager</servlet-name>
<url-pattern>/list</url-pattern>
</servlet-mapping>
<servlet-mapping>
<servlet-name>Manager</servlet-name>
<url-pattern>/expire</url-pattern>
</servlet-mapping>
<servlet-mapping>
<servlet-name>Manager</servlet-name>
<url-pattern>/sessions</url-pattern>
</servlet-mapping>
<servlet-mapping>
<servlet-name>Manager</servlet-name>
<url-pattern>/start</url-pattern>
</servlet-mapping>
<servlet-mapping>
<servlet-name>Manager</servlet-name>
<url-pattern>/stop</url-pattern>
</servlet-mapping>
<servlet-mapping>
<servlet-name>Manager</servlet-name>
<url-pattern>/install</url-pattern>
</servlet-mapping>
<servlet-mapping>
<servlet-name>Manager</servlet-name>
<url-pattern>/remove</url-pattern>
</servlet-mapping>
<servlet-mapping>
<servlet-name>Manager</servlet-name>
<url-pattern>/deploy</url-pattern>
</servlet-mapping>
<servlet-mapping>
<servlet-name>Manager</servlet-name>
<url-pattern>/undeploy</url-pattern>
</servlet-mapping>
<servlet-mapping>
<servlet-name>Manager</servlet-name>
<url-pattern>/reload</url-pattern>
</servlet-mapping>
<servlet-mapping>
<servlet-name>Manager</servlet-name>
<url-pattern>/save</url-pattern>
</servlet-mapping>
<servlet-mapping>
<servlet-name>Manager</servlet-name>
<url-pattern>/serverinfo</url-pattern>
</servlet-mapping>
<servlet-mapping>
<servlet-name>Manager</servlet-name>
<url-pattern>/roles</url-pattern>
</servlet-mapping>
<servlet-mapping>
<servlet-name>Manager</servlet-name>
<url-pattern>/resources</url-pattern>
</servlet-mapping>
<servlet-mapping>
<servlet-name>Manager</servlet-name>
<url-pattern>/findleaks</url-pattern>
</servlet-mapping>
<servlet-mapping>
<servlet-name>Status</servlet-name>
<url-pattern>/status/*</url-pattern>
</servlet-mapping>
<servlet-mapping>
<servlet-name>JMXProxy</servlet-name>
<url-pattern>/jmxproxy/*</url-pattern>
</servlet-mapping>
<servlet-mapping>
<servlet-name>HTMLManager</servlet-name>
<url-pattern>/html/*</url-pattern>
</servlet-mapping>
<!-- Define reference to the user database for looking up roles -->
<resource-env-ref>
<description>
Link to the UserDatabase instance from which we request lists of
defined role names. Typically, this will be connected to the global
user database with a ResourceLink element in server.xml or the context
configuration file for the Manager web application.
</description>
<resource-env-ref-name>users</resource-env-ref-name>
<resource-env-ref-type>
org.apache.catalina.UserDatabase
</resource-env-ref-type>
</resource-env-ref>
<!-- Define a Security Constraint on this Application -->
<security-constraint>
<web-resource-collection>
<web-resource-name>HTMLManager and Manager command</web-resource-name>
<url-pattern>/html/*</url-pattern>
<url-pattern>/list</url-pattern>
<url-pattern>/expire</url-pattern>
<url-pattern>/sessions</url-pattern>
<url-pattern>/start</url-pattern>
<url-pattern>/stop</url-pattern>
<url-pattern>/install</url-pattern>
<url-pattern>/remove</url-pattern>
<url-pattern>/deploy</url-pattern>
<url-pattern>/undeploy</url-pattern>
<url-pattern>/reload</url-pattern>
<url-pattern>/save</url-pattern>
<url-pattern>/serverinfo</url-pattern>
<url-pattern>/roles</url-pattern>
<url-pattern>/resources</url-pattern>
<url-pattern>/findleaks</url-pattern>
</web-resource-collection>
<auth-constraint>
<!-- NOTE: This role is not present in the default users file -->
<role-name>manager</role-name>
</auth-constraint>
</security-constraint>
<security-constraint>
<web-resource-collection>
<web-resource-name>JMX proxy</web-resource-name>
<url-pattern>/jmxproxy/*</url-pattern>
</web-resource-collection>
<auth-constraint>
<!-- NOTE: 1. These roles are not present in the default users file
2. The manager role is deprecated, it will be removed in
Tomcat 7.
3. Use the manager-jmx role to take advantage of the new
CSRF protection. Using the manager role or assigning both
the manager-jmx and manager-gui roles to the same user
will bypass the CSRF protection. -->
<role-name>manager-jmx</role-name>
<role-name>manager</role-name>
</auth-constraint>
</security-constraint>
<security-constraint>
<web-resource-collection>
<web-resource-name>Status</web-resource-name>
<url-pattern>/status/*</url-pattern>
</web-resource-collection>
<auth-constraint>
<!-- NOTE: 1. These roles are not present in the default users file
2. The manager role is deprecated, it will be removed in
Tomcat 7. -->
<role-name>manager-jmx</role-name>
<role-name>manager</role-name>
</auth-constraint>
</security-constraint>
<!-- Define the Login Configuration for this Application -->
<login-config>
<auth-method>BASIC</auth-method>
<realm-name>Tomcat Manager Application</realm-name>
</login-config>
<!-- Security roles referenced by this web application -->
<security-role>
<description>
The role that is required to log in to the Manager Application
</description>
<role-name>manager</role-name>
</security-role>
<security-role>
<description>
The role that is required to access the HTML JMX Proxy
</description>
<role-name>manager-jmx</role-name>
</security-role>
<error-page>
<error-code>401</error-code>
<location>/401.jsp</location>
</error-page>
</web-app>
Thanks for the help.
- Uwe
-----Ursprüngliche Nachricht-----
Von: Konstantin Kolinko [mailto:knst.kolinko@gmail.com]
Gesendet: Dienstag, 30. August 2011 11:45
An: Tomcat Users List
Betreff: Re: Problems with manager app under Tomcat 6.0.29
2011/8/30 <Uw...@t-systems.com>:
> java.lang.IllegalArgumentException: addChild: Child name 'Manager' is
>not unique
> at
>org.apache.tomcat.util.digester.Digester.createSAXException(Digester.ja
>va:2806)
>(...)
> 30.08.2011 09:19:41 org.apache.catalina.startup.ContextConfig
>applicationWebConfig
> SEVERE: Occurred at line 43 column 13
>(...)
>
> In this error message it says something about line 43 column 13.
> But I have copied the same web.xml to all four instance
> webapps/manager/WEB-INF/ directories and as I said on one instance it is running well.
> This is the entry in it in this line.
> 36 <servlet>
> 37 <servlet-name>Manager</servlet-name>
> 38
> <servlet-class>org.apache.catalina.manager.ManagerServlet</servlet-cla
> ss>
> 39 <init-param>
> 40 <param-name>debug</param-name>
> 41 <param-value>2</param-value>
> 42 </init-param>
> 43 </servlet>
Check that you do not have <servlet-name>Manager</servlet-name>
1. elsewhere in manager/WEB-INF/web.xml
2. in conf/web.xml
E.g. such error will happen if you try to use <servlet-name>default</servlet-name> in your webapp, because servlet named "default" is defined in conf/web,xml.
I have no problem running several Tomcat + Manager webapp instances on the same host in standard configuration. You configuration must have some differences wrt. standard one.
Best regards,
Konstantin Kolinko
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Problems with manager app under Tomcat 6.0.29
Posted by Konstantin Kolinko <kn...@gmail.com>.
2011/8/30 <Uw...@t-systems.com>:
> java.lang.IllegalArgumentException: addChild: Child name 'Manager' is not unique
> at org.apache.tomcat.util.digester.Digester.createSAXException(Digester.java:2806)
>(...)
> 30.08.2011 09:19:41 org.apache.catalina.startup.ContextConfig applicationWebConfig
> SEVERE: Occurred at line 43 column 13
>(...)
>
> In this error message it says something about line 43 column 13.
> But I have copied the same web.xml to all four instance webapps/manager/WEB-INF/ directories and as I said
> on one instance it is running well.
> This is the entry in it in this line.
> 36 <servlet>
> 37 <servlet-name>Manager</servlet-name>
> 38 <servlet-class>org.apache.catalina.manager.ManagerServlet</servlet-class>
> 39 <init-param>
> 40 <param-name>debug</param-name>
> 41 <param-value>2</param-value>
> 42 </init-param>
> 43 </servlet>
Check that you do not have <servlet-name>Manager</servlet-name>
1. elsewhere in manager/WEB-INF/web.xml
2. in conf/web.xml
E.g. such error will happen if you try to use
<servlet-name>default</servlet-name> in your webapp, because servlet
named "default" is defined in conf/web,xml.
I have no problem running several Tomcat + Manager webapp instances on
the same host in standard configuration. You configuration must have
some differences wrt. standard one.
Best regards,
Konstantin Kolinko
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org