OutgoingRunner consumes 100% cpu

Bug #966531 reported by Mark Sapiro on 2012-03-27
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
GNU Mailman
Medium
Mark Sapiro

Bug Description

If OutgoingRunner's attempt to connect to the outgoing SMTP server results in socket.error, OutgoingRunner requeues the message and continues processing without delay resulting in continuously looping over the queue until the socket.error is somehow resolved.

Mark Sapiro (msapiro) on 2012-03-27
Changed in mailman:
status: In Progress → Fix Committed
Bernard (unowned60) on 2012-03-28
Changed in mailman:
status: Fix Committed → Invalid
Mark Sapiro (msapiro) on 2012-03-28
Changed in mailman:
status: Invalid → Fix Committed
Bernard (unowned60) wrote :

Mark Sapiro,

for my error, I am asking for leniency, some too crumbersome!!
thanks!
Bernard

Bernard (unowned60) on 2012-03-28
Changed in mailman:
status: Fix Committed → Confirmed
Mark Sapiro (msapiro) on 2012-03-28
Changed in mailman:
status: Confirmed → Fix Committed
Bernard (unowned60) on 2012-03-28
Changed in mailman:
status: Fix Committed → Confirmed
Mark Sapiro (msapiro) on 2012-03-28
Changed in mailman:
status: Confirmed → Fix Committed
Mark Sapiro (msapiro) on 2012-06-15
Changed in mailman:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers