[JBoss-dev] jboss-head status

[Scott M Stark]

So this problem is due to conflicting attempts to manage the mbean 
instance and the mbean service state. What happens is that the 
EjbModules in the first redeployment are removed as mbeans, which puts 
the ServiceMBeanSupport into an UNREGISTERED state, and the EjbModule 
fails to remove such mbeans from the ServiceController:

        // If the container was registered with the mbeanserver, remove it
        if (conState != UNREGISTERED)
        {
            try
            {
               serviceController.remove(jmxName);
            }
            catch (Throwable e)
            {
               log.error("unexpected exception removing Container: " + 
jmxName, e);
            } // end of try-catch
         }

On the deployment part, the ServiceController still has the previous 
ServiceContext and does not believe that the Create state change 
requires anything to be done:

2006-08-24 12:40:41,466 TRACE 
[org.jboss.kernel.plugins.dependency.AbstractKernelController] No change 
required toState=Create 
name=jboss.j2ee:jndiName=cmp2/simple/Simple,service=EJB state=Create 
mode=Manual requiredState=Create

Not sure if this is a problem with the jmx state mgmt or how the 
remaining ServiceControllerContext is in a create state after it was 
uninstalled:

2006-08-24 12:39:23,254 TRACE 
[org.jboss.kernel.plugins.dependency.AbstractKernelController] Change 
toState=Create name=jboss.j2ee:jndiName=cmp2/simple/Simple,service=EJB 
state=Installed mode=Manual requiredState=Installed
2006-08-24 12:39:23,254 TRACE 
[org.jboss.kernel.plugins.dependency.AbstractKernelController] 
Uninstalling jboss.j2ee:jndiName=cmp2/simple/Simple,service=EJB from 
Installed
2006-08-24 12:39:23,254 TRACE 
[org.jboss.kernel.plugins.dependency.AbstractKernelController] 
Uninstalling jboss.j2ee:jndiName=cmp2/simple/Simple,service=EJB from Start


Scott M Stark wrote:
> An example redeployment scenario that is consistently showing NPEs is 
> redeploying the testsuite/output/lib/cts.jar. On every other 
> deployment the JDBCStoreManager.start is throwing an NPE because it is 
> being started without being created. When this happens the EjbModule 
> is started with only a couple of its nested mbeans being in the 
> Created state:
>