[jboss-jira] [JBoss JIRA] Commented: (JBJMX-101) failed to redeploy MBean dependent web module
[ http://jira.jboss.com/jira/browse/JBJMX-101?page=comments#action_12347641 ]
David Wade commented on JBJMX-101:
----------------------------------
Actually I think this is a bug.
If a web application is declared in the jboss-web.xml as depending on a data source (or
some other service) and that data source is updated causing it to undeploy and redeploy,
the web applications that have declared dependence on that datasource should be undeployed
when the data source is undeployed and then redeployed after the datasource is redeployed.
i.e. the web application should not just be stopped and restarted but should be
undeployed and redeployed.
The undeploying of the web application does result in it being unavailable for a short
period, but this infinitely better than leaving it in a non working state due to a stale
resource ref. It seems to me that this half the reason for the dependency declaration
in the first place.
Further, am sure this used to work with SAR's & HAR's
failed to redeploy MBean dependent web module
---------------------------------------------
Key: JBJMX-101
URL: http://jira.jboss.com/jira/browse/JBJMX-101
Project: JBoss JMX
Issue Type: Bug
Affects Versions: JBossAS-4.0.0
Environment: JBossAS 4.0.4.GA
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_09-b01)
Reporter: Maxim Gordienko
Environment: Sar module containing MBean
content of META-INF/jboss-service.xml
--- CUT ---
<?xml version="1.0" encoding="UTF-8"?>
<server>
<mbean code="dot.com.DummyKPBossService"
name="dot.com:service=DummyService">
</mbean>
</server>
--- END CUT ---
War module dependant on MBean from Sar
content of WEB-INF/jboss-web.xml
--- CUT ---
<?xml version="1.0" encoding="UTF-8"?>
<jboss-web>
<depends>dot.com:service=DummyService"</depends>
</jboss-web>
--- END CUT ---
upon redeployment Sar module JBoss tries to redeploy War module but fail with NPE:
java.lang.NullPointerException
at org.jboss.web.WebModule.startModule(WebModule.java:82)
at org.jboss.web.WebModule.startService(WebModule.java:61)
at
org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
at
org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
.......
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira