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

Separately track dirty status of ClusteredSession meta-data and only replicate if needed

    Details

    • Estimated Difficulty:
      Medium

      Description

      The dirty status of a ClusteredSession's attributes and meta-data should be tracked separately. The meta-data should only be replicated if made dirty. Changing the accessed time does not make the meta-data dirty.

      This will allow much less frequent replication of the meta-data. Particularly useful in the case of ATTRIBUTE and FIELD granularity.

      The internal isOutdated member should be changed to a long. An outdated check consists of comparing the long to the lastAccessedTime. If the outdated field is later than the lastAccessedTime, the session is outdated. setOutdated(true) sets the outdated member to System.currentTimeMillis(); setOutdated(false) sets it to 0.

      For 5.0.0, the behavior of SessionBasedClusteredSession can be changed as well. In writeExternal, we will write a boolean indicating whether the metadata is included. Cannot do this in 4.0.x because this will break serializable compatibility.

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                brian.stansberry Brian Stansberry
                Reporter:
                brian.stansberry Brian Stansberry
              • Votes:
                0 Vote for this issue
                Watchers:
                0 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Time Tracking

                  Estimated:
                  Original Estimate - 1 day
                  1d
                  Remaining:
                  Remaining Estimate - 1 day
                  1d
                  Logged:
                  Time Spent - Not Specified
                  Not Specified