I get test suite failures for TC 7 right now. I'm not sure whether it is
because I changed my testing environment, but the failure seems to be
pretty special, namely a NullPointerException in
MBeanUtils.createObjectName() line 532.
I added some logging and the reason is, that the host returned by
Container host = context.getParent();
is null.
Feb 17, 2011 11:56:48 AM org.apache.catalina.deploy.NamingResources
destroyInternal
WARNING: namingResources.mbeanDestroyFail
java.lang.NullPointerException
at
org.apache.catalina.mbeans.MBeanUtils.createObjectName(MBeanUtils.java:532)
at
org.apache.catalina.mbeans.MBeanUtils.destroyMBean(MBeanUtils.java:1154)
at
org.apache.catalina.deploy.NamingResources.destroyInternal(NamingResources.java:976)
at
org.apache.catalina.util.LifecycleBase.destroy(LifecycleBase.java:277)
at
org.apache.catalina.core.StandardContext.destroyInternal(StandardContext.java:5484)
at
org.apache.catalina.util.LifecycleBase.destroy(LifecycleBase.java:277)
at
org.apache.catalina.core.ContainerBase.removeChild(ContainerBase.java:969)
at
org.apache.catalina.core.ContainerBase.destroyInternal(ContainerBase.java:1108)
at
org.apache.catalina.util.LifecycleBase.destroy(LifecycleBase.java:277)
at
org.apache.catalina.core.ContainerBase.removeChild(ContainerBase.java:969)
at
org.apache.catalina.core.ContainerBase.destroyInternal(ContainerBase.java:1108)
at
org.apache.catalina.util.LifecycleBase.destroy(LifecycleBase.java:277)
at
org.apache.catalina.core.StandardService.destroyInternal(StandardService.java:593)
at
org.apache.catalina.util.LifecycleBase.destroy(LifecycleBase.java:277)
at
org.apache.catalina.core.StandardServer.destroyInternal(StandardServer.java:788)
at
org.apache.catalina.util.LifecycleBase.destroy(LifecycleBase.java:277)
at org.apache.catalina.startup.Tomcat.destroy(Tomcat.java:323)
The MBean name for the first failure is
Catalina:type=Environment,resourcetype=Context,context=/examples,host=NULL,name=name3
(I replaced host.getName() with "NULL" when host is null) but there are
many such failures during the test run. Not sure, but because it always
seems to happen on destroy, it might be a lifecycle issue?
Regards,
Rainer
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org