Just wanted to add an alternate solution to this for the folks that run into this bug while searching. If you make the ASA send active resets instead of silently dropping the connections out of their table, your environment should stabilize. Something along the lines of the following, plus any appropriate adjustments for port/policy-map based upon your individual environment:
class-map rabbit-hop
match port tcp eq 5672
policy-map global_policy
class rabbit-hop
set connection timeout idle 12:00:00 reset
Just wanted to add an alternate solution to this for the folks that run into this bug while searching. If you make the ASA send active resets instead of silently dropping the connections out of their table, your environment should stabilize. Something along the lines of the following, plus any appropriate adjustments for port/policy-map based upon your individual environment:
class-map rabbit-hop
match port tcp eq 5672
policy-map global_policy
class rabbit-hop
set connection timeout idle 12:00:00 reset