bean undeployment in server (as5/jboss mc) shutdown

[emmartins]

I have a bean that is injected with the RealTransactionManager from JBoss AS5, and a second bean that is injected with the first one, and when I shutdown the server the RealTransactionManager is removed from the first bean before the second one undeploy completes, how can I avoid that behavior? I tried to add a for RealTransactionManager in the second one but it doesn't do any good...

This is the beans xml:

<?xml version="1.0" encoding="UTF-8"?>

<deployment xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="urn:jboss:bean-deployer:2.0">

 <bean name="Mobicents.JAINSLEE.TransactionManagerMBean"
 class="org.mobicents.slee.runtime.transaction.SleeTransactionManagerImpl">
 <!-- jboss as tx manager bean -->
 <property name="transactionManager"><inject bean="RealTransactionManager"/></property>
 </bean>

 <bean name="Mobicents.JAINSLEE.SleeManagement"
 class="org.mobicents.slee.container.management.jmx.SleeManagementMBeanImpl">
 <annotation>@org.jboss.aop.microcontainer.aspects.jmx.JMX(name="slee:service=SleeManagement",exposedInterface=org.mobicents.slee.container.management.jmx.SleeManagementMBeanImplMBean.class, registerDirectly=true)</annotation>
 <property name="sleeTransactionManager"><inject bean="Mobicents.JAINSLEE.TransactionManagerMBean"/></property>
 </bean>


 <!-- ... -->

</deployment>

Thanks in advance :)

-- Eduardo

[alesj]

I very much doubt that's the case,
since that would mean MC doesn't work at the core - plain bean dependency order. :-)
Transitive dependencies should not break it.

What exactly does it mean "before the second one undeploy completes"?

[emmartins]

The second is also an StandardMBean and the undeployment is the execution of stop(), which is invoked...

[alesj]

Here is a mock test, which of course works. ;-)
- http://anonsvn.jboss.org/repos/jbossas/projects/microcontainer/trunk/kernel/src/test/java/org/jboss/test/kernel/deployment/test/TransitiveBeansTestCase.java
- http://anonsvn.jboss.org/repos/jbossas/projects/microcontainer/trunk/kernel/src/test/resources/org/jboss/test/kernel/deployment/test/TransitiveBeansTestCase.xml
- http://anonsvn.jboss.org/repos/jbossas/projects/microcontainer/trunk/kernel/src/test/java/org/jboss/test/kernel/deployment/support/FirstBean.java

[alesj]

"alesj" wrote:

What exactly does it mean "before the second one undeploy completes"?

I'm just asking since the dependent beans are not completely uninstalled.
They are just unwinded to a state just before the dependent state.
e.g. property injection happens at Configured
when uninstalling, removing that injection, the bean will be left in Configured-1 state = Instantiated

[emmartins]

so when should this bean run the shutdown code currently in StandardMBean.stop() so the other it depends is still full functional? :)

[alesj]

"emmartins" wrote:
so when should this bean run the shutdown code currently in StandardMBean.stop() so the other it depends is still full functional? :)

I don't understand what you mean?
You're probably missin ',' before "in"?

"emmartins" wrote:
so when should this bean run the shutdown code currently

Dunno, it's your service. ;-)

The lifecycle: instantiated - configured - create/destroy - start/stop
Injection --> configured

"emmartins" wrote:
in StandardMBean.stop() so the other it depends is still full functional?

The order of undeploy is:
- undeploy my dependencies
- undeploy me
Hence the "the other it depends" should be still fully finctional (installed).

See AbstractController::uninstallContext.
And re-check the mock test, I did some small modifications.

[emmartins]

My bad, I missed the async execution in another thread of part of the shutdown code, which means the undeployer thread was proceding with the server shutdown.

Thanks Ales :-)

-- Eduardo