Bug 55836 - Failed to unregister MBean
Summary: Failed to unregister MBean
Status: RESOLVED INVALID
Alias: None
Product: Tomcat 7
Classification: Unclassified
Component: Catalina (show other bugs)
Version: 7.0.47
Hardware: Other Linux
: P2 normal (vote)
Target Milestone: ---
Assignee: Tomcat Developers Mailing List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-12-02 15:52 UTC by Ugo Ducharme
Modified: 2013-12-03 13:45 UTC (History)
0 users


Attachments
Example server.xml that causes the problem. (2.63 KB, text/xml)
2013-12-02 15:52 UTC, Ugo Ducharme 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Ugo Ducharme 2013-12-02 15:52:51 UTC 
Created attachment 31086 [details]
Example server.xml that causes the problem.

I needed to have my web services on a different port than or applicative port. To do so, I added a new service in the server.xml file and all works fine except that when I shutdown Tomcat, I get several warnings with this exception:

WARNING: Failed to unregister MBean with name [Catalina:type=Service] during component destruction
javax.management.InstanceNotFoundException: Catalina:type=Service
        at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.getMBean(Unknown Source)
        at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.exclusiveUnregisterMBean(Unknown Source)
        at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.unregisterMBean(Unknown Source)
        at com.sun.jmx.mbeanserver.JmxMBeanServer.unregisterMBean(Unknown Source)
        at org.apache.catalina.util.LifecycleMBeanBase.unregister(LifecycleMBeanBase.java:194)
        at org.apache.catalina.util.LifecycleMBeanBase.destroyInternal(LifecycleMBeanBase.java:73)
        at org.apache.catalina.core.StandardService.destroyInternal(StandardService.java:596)
        at org.apache.catalina.util.LifecycleBase.destroy(LifecycleBase.java:304)
        at org.apache.catalina.core.StandardServer.destroyInternal(StandardServer.java:822)
        at org.apache.catalina.util.LifecycleBase.destroy(LifecycleBase.java:304)
        at org.apache.catalina.startup.Catalina.stop(Catalina.java:743)
        at org.apache.catalina.startup.Catalina.start(Catalina.java:704)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
        at java.lang.reflect.Method.invoke(Unknown Source)
        at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:322)
        at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:450)
Comment 1 Tatsuya Bessho 2013-12-03 04:19:50 UTC 
Two Engines have been named same "Catalina".
Doc said "When using multiple Service elements in the same Server, each Engine MUST be assigned a unique name.".
http://tomcat.apache.org/tomcat-7.0-doc/config/engine.html#Attributes
Comment 2 Ugo Ducharme 2013-12-03 13:45:03 UTC 
Ok, thank you. I'll go and resolve the bug.