On Mon, 28 Jul 2014 10:02:23 GMT, Sönke Ludwig wrote:

There is a ticket with the same error. Maybe the reason is that the server only accepts a maximum of 6 connections? It would definitely be good to implement a limit on the number of parallel connections for ConnectionPool anyway.

It is possible. I'll look into it...

You'd need to catch(Throwable ex), but then it should work. The alternative is to define "versions": ["VibeDebugCatchAll"] in the dub.json. This will cause vibe.d to catch any Throwable and log its contents instead of just killing the process.

Alternatively, you could load up the application in GDB and use break _d_throwc to see where the exception is thrown (assuming that there are not a lot of other exceptions).

Thanks for the suggestions. It seems that the error is in fact in std.logger.

Drasha