Details

    • Type: Bug
    • Status: Resolved (View Workflow)
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: 13.1
    • Component/s: Infinispan
    • Labels:
      None
    • Sprint:
      DV Sprint 58
    • Story Points:
      1

      Description

      Adding transactional logic to infinispan highlights several problems with marshaller registration. The first is that all connections are working off of a shared context and each registering a marshaller for the same class type - this is not thread safe.

      The other issue specific to transactions is that some operations are delayed or redone at commit time - which is called after the connection is closed potentially in a different thread and thus the marshaller provider has been removed. Given the interplay of threads using a thread local won't work.

      Potentially a transaction aware thread pool or the use of something like our execution context keep alive may be needed.

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                shawkins Steven Hawkins
                Reporter:
                shawkins Steven Hawkins
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Time Tracking

                  Estimated:
                  Original Estimate - 6 hours Original Estimate - 6 hours
                  6h
                  Remaining:
                  Remaining Estimate - 0 minutes
                  0m
                  Logged:
                  Time Spent - 7 hours
                  7h