- Found an issue with AsyncAdaptingServlet:
  * When using async-supported we use the AsyncAdaptingServlet and its AsyncRequestResponse class
  * Upon an incoming request we get the AsyncContext and set the timeout as follows:

            long heartbeatTimeout = configuration.getAttributeAsLong("heartbeatTimeout", ConfigurationServlet.DefaultHeartbeatTimeout);
            asyncContext.setTimeout(heartbeatTimeout * 2);

  * If I'm not mistaken, this ends up to be a constant 30 seconds
  * Meaning it will automatically timeout after 30 seconds and sends some default request (which I don't know the details of)
  * As we're using the Adaptive Heartbeat, these 30 seconds won't be enough
  * ThreadBlockingRequestResponse does have an additional timeout mechanism as well, but it's set to 600 seconds
- As the ICEpush mechanism itself in any environment times out using a <noop /> response after 3 * heartbeatTimeout or after configured maxHeartbeatInterval, the AsyncRequestResponse's AsyncContext.setTimeout(timeout) and ThreadBlockingRequestResponse's Semaphore.tryAcquire(timeout, TimeUnit) should exceed the 3 * heartbeatTimeout or configured maxHeartbeatInterval