Customer configured JMS Audit Logging using RabbitMQ by configuring RabbitMQ as a JNDI Resource managed by Tomcat. While testing a RabbitMQ cluster setting, the cluster became unavailable and allowed connections without allowing sending/receive for a short time. The Audit Handler did not reconnect to RabbitMQ this seems to be related to OPENAM-12308. Customer found that enabling batch mode allowed the AM to automatically reconnect if the remote broker reboots, this then locks up AM. The AM hang is possibly due to this thread "http-nio-10.32.40.82-8443-exec-60" #1152 daemon prio=5 os_prio=0 tid=0x00007fcd44261800 nid=0x1acd waiting on condition [0x00007fccfff09000] see the attached thread dump.