Uploaded image for project: 'EJB 3.0'
  1. EJB 3.0
  2. EJBTHREE-948

FamilyClusterInfo not properly scoped

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • AS 4.2.0 GA
    • AS 4.2.0 GA
    • None
    • None

      StatefulClusterProxyFactory and StatelessClusterProxyFactory are using Container.getEjbName() to identify beans. This is inadequate as the ejb name need not be unique across deployments. Different deployments with the same name will overwrite each others' FamilyClusterInfo.

      Should probably use the OID. EJB2 uses the container's JMX ObjectName, which is basically the same as the EJB3 OID.

              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: