AmazonMQ Dead connection not clean up

Hi there,

I have an amazonMQ with the broker connection limit of 100. Normally, I use open connection and it only use 37 connection.

But in the meantime, I see there are an increment in the connection, I though that because my pods are down, so the system connect with the new pods. Unfortunately, the dead connection is still there although the doc for amazonmq, there is a note: Check your client-side logs for further details. The broker will clean up inactive TCP connections after 600000 ms, and free up the connection socket.

Here is the screenshot of Cloudwatch for my ActiveMQ connection https://i.ibb.co/MMzg8sB/Image-from-i-OS.jpg

Here is my policy entry configuration:

<policyEntry gcInactiveDestinations="true" inactiveTimoutBeforeGC="60000" topic="&gt;">
  <!--
  The constantPendingMessageLimitStrategy is used to prevent
  slow topic consumers to block producers and affect other consumers
  by limiting the number of messages that are retained

  For more information, see: http://activemq.apache.org/slow-consumer-handling.html
  -->
  <pendingMessageLimitStrategy>
    <constantPendingMessageLimitStrategy limit="1000"/>
  </pendingMessageLimitStrategy>
</policyEntry>