Bug 489000 - Message body test in carod fails when body is not set
Message body test in carod fails when body is not set
Product: Red Hat Enterprise MRG
Classification: Red Hat
Component: grid (Show other bugs)
All Linux
urgent Severity urgent
: 1.1.1
: ---
Assigned To: Robert Rati
Martin Kudlej
Depends On:
  Show dependency treegraph
Reported: 2009-03-06 12:16 EST by Matthew Farrellee
Modified: 2009-04-21 12:17 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2009-04-21 12:17:19 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2009:0434 normal SHIPPED_LIVE Red Hat Enterprise MRG Messaging and Grid Version 1.1.1 2009-04-21 12:15:50 EDT

  None (edit)
Description Matthew Farrellee 2009-03-06 12:16:15 EST

When sending a message from C++ that does not have a body set, e.g.

   Message message;
   message.getMessageProperties().setReplyTo(ReplyTo("amq.direct", response_queue_key));
   message.getHeaders().setInt("JobUniverse", 5);
   session.messageTransfer(arg::content=message, arg::destination="amq.direct");

carod incorrectly thinks there is a message body.

From carod:
      if saved_work.AMQP_msg.body != '':

needs to be:
      if saved_work.AMQP_msg.body != '' and saved_work.AMQP_msg.body != None:
Comment 1 Robert Rati 2009-03-06 15:03:31 EST
The AMQP message body is checked against None now.

Fixed in:
Comment 3 Martin Kudlej 2009-03-27 09:55:19 EDT
I cannot reproduce this. Submitting from c++ client doesn't work with emtpy body or with non-empty body. Client is from blog http://spinningmatt.wordpress.com/bucket/llcpp/ and settings are acording http://www.redhat.com/docs/en-US/Red_Hat_Enterprise_MRG/1.1/html/Grid_User_Guide/chap-Grid_User_Guide-Low_latency_scheduling.html

I found in /var/lib/condor/log/StartLog
Warning, hook /usr/libexec/condor/hooks/hook_fetch_work.py (pid 7385) printed to stderr: Traceback (most recent call last):
  File "/usr/libexec/condor/hooks/hook_fetch_work.py", line 73, in ?
  File "/usr/libexec/condor/hooks/hook_fetch_work.py", line 62, in main
    decoded = pickle.loads(reply)
  File "/usr/lib/python2.4/pickle.py", line 1394, in loads
    return Unpickler(file).load()
  File "/usr/lib/python2.4/pickle.py", line 872, in load
  File "/usr/lib/python2.4/pickle.py", line 894, in load_eof
    raise EOFError

Is this warning a symptom of this bug or is it another bug?

Comment 4 Robert Rati 2009-03-27 14:04:13 EDT
No, that message is not related to this BZ.  That message is an indication that carod was stopped when work was being fetched and the hook got garbage.
Comment 5 Martin Kudlej 2009-04-01 09:13:31 EDT
Tested on rhel 5.3/4.7 and i386/x86_64 on condor-low-latency-1.0-12 and condor-job-hooks-common-1.0-5...OK

Comment 7 errata-xmlrpc 2009-04-21 12:17:19 EDT
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.


Note You need to log in before you can comment on or make changes to this bug.