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/370015 /git.openstack. org/cgit/ openstack/ fuel-library/ commit/ ?id=8318d705655 6337f17f596edad 9d7eed48ec3ca5
Committed: https:/
Submitter: Jenkins
Branch: stable/mitaka
commit 8318d7056556337 f17f596edad9d7e ed48ec3ca5
Author: Georgy Kibardin <email address hidden>
Date: Tue Sep 13 18:43:45 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: Ieec889828d1dd2 654ee760e7d5676 efd14c7c348
Closes-Bug: #1613246
Closes-Bug: #1298262