Analyze DefaultAccessLogReceiver and come up with strategy of dealing with possible OOME on overflowing pendingMessages field. Verify its to blow up.

NOTE:

• possibly work in group of 2
• write happen in IO thread supplied, this can be crucial in testing/verifying
  TODO:
• overflow warning on certain threshold being breached. Note that pendingMessages.size is a costly operation and thus cant be used here
• come up with strategy to deal with second threshold, add POC implementation