Uploaded image for project: 'Application Server 3  4  5 and 6'
  1. Application Server 3 4 5 and 6
  2. JBAS-4724

DRM lifecycle must be controlled by ClusterPartition

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • JBossAS-5.0.0.Beta3
    • JBossAS-5.0.0.Beta2
    • Clustering
    • None

      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.

            bstansbe@redhat.com Brian Stansberry
            bstansbe@redhat.com Brian Stansberry
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: