wthttp server may terminate after uncaught exception
Specific issue was seen from: void Connection::handleWriteResponse(ReplyPtr reply, const asio_error_code& e, std::size_t bytes_transferred) called from a boost call back function.
Code review shows that must have been from TcpConnection::startAsyncWriteResponse() or SslConnection.
Apparently, an unhandled exception during a boost asio callback causes the process to terminate by abort (as if unhandled exception is thrown from the main thread?). Therefore I suggest adding many more try/catch blocks just to be safe.
No data to display