EsConnection.subscribe catchup exhibits multiple problems

During startup of my application yesterday I had the following output to stdout. I subscribe to the allstream so it is processing for about a minute before it reaches the live events state.

My interpretation of the the log output is:

The library is requesting so large batches that it triggers internal timeouts.
An actor then apparently finishes receiving its events but cannot send it anywhere.
It cannot send it anywhere so it prints it all (about 10 MB !) to stdout.

All of the points above seem a bit problematic to me. Do you agree ?

I am using 'com.geteventstore:eventstore-client_2.11:2.2.0'.

The logged ouput is:


[INFO] [06/13/2016 16:34:26.978] [EventStoreActorSystem-akka.actor.default-dispatcher-4] [akka://EventStoreActorSystem/user/$a] Connected to #####
[WARN] [06/13/2016 16:35:10.767] [EventStoreActorSystem-akka.actor.default-dispatcher-13] [akka://EventStoreActorSystem/user/$a] Connection lost to #####: no heartbeat within 2 seconds
[INFO] [06/13/2016 16:35:11.056] [EventStoreActorSystem-akka.actor.default-dispatcher-2] [akka://EventStoreActorSystem/user/$a] Connected to #####
[INFO] [06/13/2016 16:35:11.746] [EventStoreActorSystem-akka.actor.default-dispatcher-3] [akka://EventStoreActorSystem/user/$a] closing connection to #####
[WARN] [06/13/2016 16:35:13.197] [EventStoreActorSystem-akka.actor.default-dispatcher-9] [akka://EventStoreActorSystem/user/$a] Connection lost to #####: connection actor died
[INFO] [06/13/2016 16:35:13.494] [EventStoreActorSystem-akka.actor.default-dispatcher-9] [akka://EventStoreActorSystem/user/$a] Connected to #####
[WARN] [06/13/2016 16:35:13.544] [EventStoreActorSystem-akka.actor.default-dispatcher-3] [akka://EventStoreActorSystem/user/$a] Connection lost to #####: peer closed
[INFO] [06/13/2016 16:35:13.842] [EventStoreActorSystem-akka.actor.default-dispatcher-13] [akka://EventStoreActorSystem/user/$a] Connected to #####
[WARN] [06/13/2016 16:35:16.550] [EventStoreActorSystem-akka.actor.default-dispatcher-9] [akka://EventStoreActorSystem/user/$a] Cannot deliver ReadAllEventsCompleted(List(IndexedEvent(EventRecord(SystemStream($stats-0.0.0.0:2113),EventNumber(13324),EventData($statsCollected,43f1f344-701f-d37a-5d16-66cc39e72f94,Content({
....
10 MB of logs here
....
},ContentType.Json),Content(ByteString(),ContentType.Json)),Some(2016-06-04T07:12:35.566+02:00)),Position(292328028))),Position(281767231),Position(292349164),Forward), client not found for correlationId: 76e3beeb-93c2-48b8-9611-59c37b362ed8
[WARN] [06/13/2016 16:35:16.556] [EventStoreActorSystem-akka.actor.default-dispatcher-9] [akka://EventStoreActorSystem/user/$a] Connection lost to #####: peer closed
[INFO] [06/13/2016 16:35:16.563] [EventStoreActorSystem-akka.actor.default-dispatcher-4] [akka://EventStoreActorSystem/user/$a/$d] Message [eventstore.pipeline.TcpPipelineHandler$Init$Command] from Actor[akka://EventStoreActorSystem/user/$a#-761697866] to Actor[akka://EventStoreActorSystem/user/$a/$d#-201202823] was not delivered. [1] dead letters encountered. This logging can be turned off or adjusted with configuration settings 'akka.log-dead-letters' and 'akka.log-dead-letters-during-shutdown'.
[INFO] [06/13/2016 16:35:16.850] [EventStoreActorSystem-akka.actor.default-dispatcher-9] [akka://EventStoreActorSystem/user/$a] Connected to #####

EventStore / EventStore.JVM

EsConnection.subscribe catchup exhibits multiple problems #55