-
Bug
-
Resolution: Done
-
Major
-
26.1.3.Final
-
None
Working on a JBoss 5 to Wildfly 26.1.3 migration and seeing some difference in MBean behavior during shutdown.
With JBoss 5, MBean stop methods are called first then deregistered from server.
With Wildfly 26.1.3, all MBeans are being deregistered, then stop methods called.
This causes InstanceNotFoundExceptions if there are dependencies between MBeans as they are no longer available to make calls to.
Is this behavior standard or is this a bug in Wildfly?
I don't see any documentation of this change. The only thing documented is the service pattern and the create, start, stop, and destroy methods.
- is duplicated by
-
WFLY-19285 Race condition between service mbean deregistration and stop/destroy of dependent mbeans
- Resolved