title: Reading message from chronicle queue does not move the current index to the next cycle automatically
body: <p>Reading message from chronicle queue does not move the current index to the next cycle automatically. I get the following logs messages:
  697917 [SCHEDULER#4] INFO net.openhft.chronicle.queue.impl.single.SingleChronicleQueueExcerpts - Rolled 2 times to find the next cycle file. This can occur if you appenders have not written anything for a while, leaving the cycle files with a gap.</p>
  
  <p>What does this means?</p>
  
  <p>My queue files are : 20160824.cq4 20160826.cq4 20160829.cq4 20160830.cq4. The 20160825.cq4 file does not exist, because there was no data added to the queue.</p>