Details

    • Type: Sub-task
    • Status: Resolved (View Workflow)
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: 1.4.1.SP6
    • Fix Version/s: 1.4.1.SP6
    • Component/s: None
    • Labels:
      None

      Description

      The fix for JBCACHE-1192 has introduced a couple of problems that are manifesting themselves in numerous errors in the test suite:

      1) _gravitateData changes the value of skipDataGravitation for the Option associated with the call, but then doesn't restore the correct value to that instance of Option.

      2) _gravitateData calls get(Fqn), and that call actually results in the instance of Option that is associated with the thread being changed (see impl of get(Fqn). But, _gravitateData does not restore the original Option to the thread. Maybe not a problem if _gravitateData is called remotely, since there is no meaningful Option associated with the thread. But _gravitateData can now also be called by DataGravitationInterceptor.localBackupGet, and in that case there very well could be a meaningful Option associated with the thread, and it needs to be restored before _gravitateData returns.

      I'll attach a possible patch in a minute.

        Gliffy Diagrams

          Attachments

            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:
                  Resolved: