Opened 15 years ago
Last modified 15 years ago
#146 new defect
does TubConnectorClientFactory stick around too long?
Reported by: | Brian Warner | Owned by: | |
---|---|---|---|
Priority: | major | Milestone: | undecided |
Component: | unknown | Version: | 0.4.1 |
Keywords: | Cc: |
Description
While investigating the incidents in tahoe#899 (I'll attach one of them here), I noticed that TubConnectorClientFactory
appears to be sticking around until the winning connection has been closed, rather than going away after the winner has finished negotiating.
I don't think this has any negative effects, but it's not how I intended it to work, so I need to either fix it to work as intended, or walk through and make sure that this unexpected behavior isn't causing problems.
In the attached incident, grep for "hndn3", and pay attention to the "Stopping factory" lines, in particular in event number 16234.
Attachments (1)
Change History (2)
Changed 15 years ago by
Attachment: | incident-2010-01-14-071855-w4y74lq.flog.bz2 added |
---|
comment:1 Changed 15 years ago by
Summary: | does TubConnectorClientFactory sticks around too long? → does TubConnectorClientFactory stick around too long? |
---|