title: ELK with RabbitMQ forwarding logs using NLog fails
body: <p>I have the following setup: a ELK stack on CentOS server with RB with mirrored Queue. Publishers are using Nlog-HAF-Rabbitmq appender to forward logs to RabbitMQ nodes behind load balancer.
  One publisher is a web application which hosted on IIS. Sometimes, it stops logging to ELK stack post-recycle which happens early in morning.</p>
  
  <p>Here are my findings:</p>
  
  <ol>
  <li>I logged Nlog internal logs to identify if any connection failure.</li>
  <li>while recycling we have Warning on Event viewer on WAS
  A process serving application pool  exceeded time limits during shut down. The process id.
  A worker process serving application pool  failed to stop a listener channel for protocol 'http' in the allotted time.  The data field contains the error number.</li>
  </ol>
  
  <p>IIS shutdown time limit 3 seconds (default)<br>
  IIS start up time limit 3 seconds (default)</p>
  
  <p>Based information above, what could be the reason?</p>