Stomp heartbeat handling is quite poorly designed. It happens in a
separate thread which sleeps, then tries to read a heartbeat if reading
mutex is acquired by message receiving thread it fails and increases
lock failure count. Upon reaching the limit (in our packets it is 2 by
default) it forcibly closes the connetion causing reconnect. Setting the
value to 0 turns the feature off.
Reviewed: https:/ /review. openstack. org/370025 /git.openstack. org/cgit/ openstack/ fuel-agent/ commit/ ?id=898bcca7522 4ad82fa98a85b77 651faaf554e2b6
Committed: https:/
Submitter: Jenkins
Branch: stable/mitaka
commit 898bcca75224ad8 2fa98a85b77651f aaf554e2b6
Author: Georgy Kibardin <email address hidden>
Date: Tue Sep 13 14:08:34 2016 +0300
Ignore heartbeats lock fails
Stomp heartbeat handling is quite poorly designed. It happens in a
separate thread which sleeps, then tries to read a heartbeat if reading
mutex is acquired by message receiving thread it fails and increases
lock failure count. Upon reaching the limit (in our packets it is 2 by
default) it forcibly closes the connetion causing reconnect. Setting the
value to 0 turns the feature off.
Change-Id: I2187ce69508c53 0073582c542c963 014acc5123a 3cc35e521ab99bb 7f94d8b54a)
Closes-Bug: #1613246
Closes-Bug: #1298262
(cherry picked from commit b50241a7b243f55