Spymemcached Java Client

TAP operation messages may never be removed from the TAP stream

Details

  • Type: Bug Bug
  • Status: Open Open
  • Priority: Critical Critical
  • Resolution: Unresolved
  • Affects Version/s: None
  • Fix Version/s: None
  • Component/s: None
  • Security Level: Public
  • Labels:
    None

Description

When looking through the TapStream abstraction added, I see it creates an ArrayList of operations (being sent to the server it seems?) but never cleans them up. This would be a reference leak with a long running TAP.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Matt Ingenthron added a comment -
Assigning to Mike just to ask for verification of behavior here. If this is an actual issue, Rags or I can fix it, but I don't fully understand the TapStream abstraction.
Show
Matt Ingenthron added a comment - Assigning to Mike just to ask for verification of behavior here. If this is an actual issue, Rags or I can fix it, but I don't fully understand the TapStream abstraction.
Hide
Permalink
Mike Wiederhold added a comment -
Those are your handles to the tap stream. Those operations need to stay around until the tap stream is finished since their completed() function is only called once the tap stream is finished.
Show
Mike Wiederhold added a comment - Those are your handles to the tap stream. Those operations need to stay around until the tap stream is finished since their completed() function is only called once the tap stream is finished.

People

  • Assignee:
    Unassigned
    Reporter:
    Matt Ingenthron
Vote (0)
Watch (1)

Dates

  • Created:
    Updated: