Bug 1302774 - IPv6 RabbitMQ connection shows periodic Exception in the reader loop: AMQ::Protocol::EmptyResponseError: Empty response received from the server
IPv6 RabbitMQ connection shows periodic Exception in the reader loop: AMQ::Pr...
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Providers (Show other bugs)
Unspecified Unspecified
high Severity high
: GA
: 5.5.3
Assigned To: Ladislav Smola
Ola Pavlenko
: ZStream
Depends On: 1302362
  Show dependency treegraph
Reported: 2016-01-28 10:24 EST by Chris Pelland
Modified: 2017-08-29 23:49 EDT (History)
11 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 1302362
Last Closed: 2016-04-13 14:42:07 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Comment 2 CFME Bot 2016-03-11 09:59:24 EST
New commit detected on cfme/5.5.z:

commit 5bac7f3bb74c7fc6108fa2a5913ab67eae2b1ee4
Merge: 8171111 bffc540
Author:     Greg Blomquist <gblomqui@redhat.com>
AuthorDate: Fri Mar 11 09:40:14 2016 -0500
Commit:     Greg Blomquist <gblomqui@redhat.com>
CommitDate: Fri Mar 11 09:40:14 2016 -0500

    Merge branch 'bz1302774' into '5.5.z'
    Make AMQP heartbeat configurable
    By default bunny takes the setting from the AMQP settings. If
    this setting is too low (like 1s) it might fail to give response
    in time, causing reconnect.
    Fixes BZ:
    Clean cherry-pick of:
    Fixes 5.5.z BZ
    See merge request !837

 app/models/manageiq/providers/openstack/event_catcher_mixin.rb | 7 ++++---
 config/vmdb.tmpl.yml                                           | 2 ++
 gems/pending/openstack/amqp/openstack_rabbit_event_monitor.rb  | 3 ++-
 gems/pending/openstack/openstack_event_monitor.rb              | 1 +
 4 files changed, 9 insertions(+), 4 deletions(-)
Comment 5 errata-xmlrpc 2016-04-13 14:42:07 EDT
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.


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