Project

General

Profile

Bug #7970

wthttp server may terminate after uncaught exception

Added by Koen Deforche 6 months ago.

Status:
New
Priority:
Normal
Assignee:
-
Target version:
-
Start date:
01/11/2021
Due date:
% Done:

0%

Estimated time:

Description

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

Also available in: Atom PDF