Bug 474844 - EC2E can't handle bad messages
Summary: EC2E can't handle bad messages
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise MRG
Classification: Red Hat
Component: grid
Version: 1.0
Hardware: All
OS: Linux
high
high
Target Milestone: 1.1
: ---
Assignee: Robert Rati
QA Contact: Jeff Needle
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-12-05 16:02 UTC by Robert Rati
Modified: 2009-02-04 16:04 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-02-04 16:04:56 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2009:0036 0 normal SHIPPED_LIVE Red Hat Enterprise MRG Grid 1.1 Release 2009-02-04 16:03:49 UTC

Description Robert Rati 2008-12-05 16:02:11 UTC 
Description of problem:
Bad/corrupted messages in the SQS queues cause the route hooks to stop processing messages.  Need to skip bad messages and continue processing.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:
Comment 1 Robert Rati 2008-12-10 13:58:08 UTC 
The hooks and daemon would fail to handle a bad message when attempting to unpickle it.  The message is now discarded and processing continues.  Fixed in:
condor-ec2-enhanced-hooks-1.0-6
condor-ec2-enhanced-1.0-5
Comment 4 errata-xmlrpc 2009-02-04 16:04:56 UTC 
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHBA-2009-0036.html
Note You need to log in before you can comment on or make changes to this bug.