DRM lifecycle must be controlled by ClusterPartition ---------------------------------------------------- Key: JBAS-4724 URL: http://jira.jboss.com/jira/browse/JBAS-4724 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Clustering Affects Versions: JBossAS-5.0.0.Beta2 Reporter: Brian Stansberry Assigned To: Brian Stansberry Fix For: JBossAS-5.0.0.Beta3 DistributedReplicantManagerImpl can't expose lifecycle methods to the microcontainer. Instead the DRM needs to be injected into ClusterPartition before it's create() phase, and ClusterPartition should take DRM through its lifecycle. Otherwise you can get into a situation where services like HAJNDI depend on ClusterPartition and start before DRM. If this happens and they invoke on an unstarted DRM, the deployment will block (forever). Avoiding that problem requires adding a dependency on DRM, which is way too fragile. DRM is really a subcomponent of ClusterPartition and should be managed that way. -- 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