Fix reconnect logic so only successful connections are accepted

NettyTcpClient.createReconnectListener currently accepts a connection
regardless of whether or not it connected successfully. This leads to
the Consumer<TcpConnection> registered with the Stream being driven
multiple times and with TcpConnections that are not connected.

This commit updates NettyTcpClient.createReconnectListener so that
only successful connections are accepted.

Fixes #162
Merge pull request #163 from wilkinsona/only-accept-successful-connections

Fix reconnect logic so only successful connections are accepted
Bump Disruptor version to 3.2.0.
Support multiple Consumers by creating an efficient composition of multiple Consumers down to a single Consumer. Added a test for multiple Consumers to make sure all are called once for each event.
Changes to how multiple Consumers are handled.
Tweak Processor batch processing to handle batch sizes larger than the available ringbuffer size.
Fixes #164 tweaked time incrementing code to fix a race condition