jessequ
/
AMQP-CPP
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

handle unlikely error when ssl-handshake could not be started

This commit is contained in:
Emiel Bruijntjes 2018-11-07 23:44:24 +01:00
parent 06dc23190d
commit 34f84e1ab7
1 changed files with 10 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

18
src/linux_tcp/tcpresolver.h
View File

@ -189,26 +189,28 @@ public:
*/
TcpState *proceed(const Monitor &monitor)
{
// do we have a valid socket?
if (_socket >= 0)
// prevent exceptions
try
{
// socket should be connected by now
if (_socket < 0) throw std::runtime_error(_error.data());
// report that the network-layer is connected
_parent->onConnected(this);
// handler callback might have destroyed connection
if (!monitor.valid()) return nullptr;
// if we need a secure connection, we move to the tls handshake
// @todo catch possible exception
if (_secure) return new SslHandshake(this, _hostname, std::move(_buffer));
// if we need a secure connection, we move to the tls handshake (this could throw)
if (_secure) return new SslHandshake(this, std::move(_hostname), std::move(_buffer));
// otherwise we have a valid regular tcp connection
return new TcpConnected(this, std::move(_buffer));
else return new TcpConnected(this, std::move(_buffer));
}
else
catch (const std::runtime_error &error)
{
// report error
_parent->onError(this, _error.data(), false);
_parent->onError(this, error.what(), false);
// handler callback might have destroyed connection
if (!monitor.valid()) return nullptr;