[jboss-jira] [JBoss JIRA] Created: (JBAS-4168) ejb2 sfsb passivate directory inconsistencies
Galder Zamarreno (JIRA)
jira-events at lists.jboss.org
Fri Mar 2 07:25:08 EST 2007
ejb2 sfsb passivate directory inconsistencies
---------------------------------------------
Key: JBAS-4168
URL: http://jira.jboss.com/jira/browse/JBAS-4168
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: EJB2
Affects Versions: JBossAS-4.0.5.GA, JBossAS-4.2.0.CR1
Reporter: Galder Zamarreno
Assigned To: Scott M Stark
Priority: Minor
StatefulSessionFilePersistenceManager's javadoc says that passivated
beans are stored in:
jboss-server-data-dir/storeDirectoryName/ejb-name-unique-id
However, the code actually stores them in the tmp directory:
// Get the system data directory
File dir = ServerConfigLocator.locate().getServerTempDir();
ServerConfigLocator.locate().getServerTempDir() points to
ServerConfig.SERVER_TEMP_DIR jboss.server.temp.dir.
So, the javadoc and the code are insconsistent and secondly, EJB3
SFSB cache is configured to store beans in jboss.server.data.dir
via the cache loader, at least in each JBossCache managed version.
The simple cache set up in EJB3 shows the same incosistency as
in EJB2's StatefulSessionFilePersistenceManager. I'll create a separate
JIRA for it if this one gets approved
I believe we should store the beans in the same place. I can't see a
reason not to do so.
--
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
More information about the jboss-jira
mailing list