]
Brian Stansberry closed EJBTHREE-948.
-------------------------------------
Resolution: Done
FamilyClusterInfo not properly scoped
-------------------------------------
Key: EJBTHREE-948
URL:
http://jira.jboss.com/jira/browse/EJBTHREE-948
Project: EJB 3.0
Issue Type: Bug
Affects Versions: AS 4.2.0 CR2
Reporter: Brian Stansberry
Assigned To: Brian Stansberry
Fix For: AS 4.2.0 GA
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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: