Uploaded image for project: 'JBoss Cache'
  1. JBoss Cache
  2. JBCACHE-772

State transfer not handled properly in case of reconnect

    Details

    • Type: Bug
    • Status: Open (View Workflow)
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: 1.2.4, 1.2.4SP1, 1.2.4SP2, 1.3.0.GA, 1.3.0.SP1, 1.3.0.SP2, 1.3.0.SP3, 1.4.0.GA, 1.4.0.SP1
    • Fix Version/s: 3.3.0.GA
    • Component/s: Clustering
    • Labels:
    • Estimated Difficulty:
      High

      Description

      In createService(), TreeCache set Channel.AUTO_GET_STATE to true. This should only be done if the cache is configured to do an initial state transfer.

      That's easy to fix. What's harder to fix is what to do when region-based marshalling is in effect. Probably, something like the following:

      1) In viewAccepted, monitor for the case where a view is issue that doesn't include the current node. Set a flag and ??? (throw exceptions when attempts are made to use the cache???)
      2) When another view is accepted that once again includes the current node, iterate through the various marshalling regions, inactivating and then reactivating them (reactivation will cause a partial state transfer).

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

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

                  Dates

                  • Created:
                    Updated: