Project

General

Profile

Actions

Bug #3977

closed

Bug #3877: Transaction list grows without bound on parsers that use unidirectional transactions

SNMP: Better handling of unidirectional transactions

Added by Jason Ish about 2 years ago. Updated almost 2 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Target version:
Affected Versions:
Effort:
Difficulty:
Label:
Needs backport to 4.1, Needs backport to 5.0

Description

Parsers that create a transaction per message can end up in a state where transactions are never being cleaned up. This will happen when only "to_client" traffic is seen, and appears to only affect UDP protocols. Without any "to_server" traffic, the transaction cleanup routine never considers these transactions for cleanup.


Related issues 1 (0 open1 closed)

Copied to Bug #4007: SNMP: Better handling of unidirectional transactions (5.0.x)ClosedJason IshActions
Actions #1

Updated by Jason Ish about 2 years ago

  • Status changed from New to In Review
Actions #2

Updated by Jason Ish about 2 years ago

  • Label Needs backport to 4.1, Needs backport to 5.0 added
Actions #3

Updated by Jason Ish about 2 years ago

  • Subject changed from Better handling of unidirectional transactions to SNMP: Better handling of unidirectional transactions
  • Parent task set to #3877

Tracking ticket for better handling of transactions specifically for SNMP. See parent ticket for details.

Actions #4

Updated by Jason Ish almost 2 years ago

  • Copied to Bug #4007: SNMP: Better handling of unidirectional transactions (5.0.x) added
Actions #5

Updated by Victor Julien almost 2 years ago

  • Status changed from In Review to Closed
Actions #6

Updated by Victor Julien almost 2 years ago

  • Private changed from Yes to No
Actions

Also available in: Atom PDF