Bug 1563534 - Nuage Provider uses qpid_proton gem version without heartbeating
Summary: Nuage Provider uses qpid_proton gem version without heartbeating
Keywords:
Status: ON_QA
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Providers
Version: 5.9.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: GA
: 5.10.0
Assignee: Gregor Berginc
QA Contact: Gregor Berginc
URL:
Whiteboard:
Depends On:
Blocks: 1565142
TreeView+ depends on / blocked
 
Reported: 2018-04-04 06:37 UTC by mplesko
Modified: 2020-09-21 03:14 UTC (History)
6 users (show)

Fixed In Version: 5.10.0.0
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1565142 (view as bug list)
Environment:
Last Closed:
Category: ---
Cloudforms Team: ---
Target Upstream Version:


Attachments (Terms of Use)

Description mplesko 2018-04-04 06:37:11 UTC
Description of problem:
Currently, Nuage provider relies on qpid_proton gem 0.19.0 which implements no client heartbeating mechanism hence connection is being closed every 2-3 minutes. As of today (https://issues.apache.org/jira/browse/PROTON-1806), there is qpid_proton gem version 0.22.0 available with this functionality implemented, so Nuage Provider should start using it.

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


How reproducible:
Always

Steps to Reproduce:
1. Add Nuage Provider with eventing enabled
2. Observe AMQP traffic in Wireshark (filter: "tcp && tcp.port == 5672")
3.

Actual results:
Nothing is being sent when there are no events

Expected results:
Client must send empty heartbeat packages so that ActiveMQ doesn't take us for dead.

Additional info:


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