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

ejb2 sfsb passivate directory inconsistencies

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Obsolete
    • Icon: Minor Minor
    • No Release
    • JBossAS-4.0.5.GA, JBossAS-4.2.0.CR1
    • EJB2
    • None
    • Low

      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.

              starksm64 Scott Stark (Inactive)
              rh-ee-galder Galder ZamarreƱo
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: