StatefulTreeCache does not properly segregate deployments --------------------------------------------------------- Key: EJBTHREE-946 URL: http://jira.jboss.com/jira/browse/EJBTHREE-946 Project: EJB 3.0 Issue Type: Bug Components: Clustering Affects Versions: AS 4.2.0 CR2 Reporter: Brian Stansberry Assigned To: Brian Stansberry Fix For: AS 4.2.0 GA StatefulTreeCache is using Container.getEjbName() as the first element in a bean node's Fqn. This is insufficient as that's not unique across deployments. If you deploy 2 jars and both have an ejb named Foo, when one of the jars is undeployed, the /Foo region is removed from the cache, which is unacceptable. StatefulSessionFilePersistenceManager solves this by adding a UID to name of the directory where it stores files, but that is inadequate for clustered beans, since all nodes in the cluster need to arrive at the same Fqn. Likely solution is to prefix the ejb name with something built up a la StatefulContainer.getDeployment().getScopedKernelName(), i.e. [ear=xyz.ear,]jar=abc.jar,StatefulBean -- 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