Uploaded image for project: 'Infinispan'
  1. Infinispan
  2. ISPN-10169

Hot Rod iteration state is kept around forever if IterationEnd is not invoked

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Major Major
    • None
    • 9.4.12.Final, 10.0.0.Final
    • Hot Rod, Server

      The DefaultIterationManager keeps a map of iterationstate for each active client iteration. Unfortunately, if the client does invoke the end operation, these states can linger forever. We should:

      • reap iterationstates when the channel that created them is closed
      • reap iterationstates which have been inactive for a long time

              ttarrant@redhat.com Tristan Tarrant
              ttarrant@redhat.com Tristan Tarrant
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: