You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The S3 API uses Boost.Asio to ignore SIGPIPE. However, the iRODS connection pool (if enabled) is created before SIGPIPE is registered. This results in the connection pool not being able to detect and handle broken socket connections.
To fix this issue, we just need to call std::signal(SIGPIPE, SIG_IGN) before the connection pool is created.
The text was updated successfully, but these errors were encountered:
This commit makes it so that the SIGPIPE signal is ignored before any
sockets are created. This change allows the iRODS connection pool to
detect broken sockets and re-establish connections without a restart of
the S3 API.
This commit makes it so that the SIGPIPE signal is ignored before any
sockets are created. This change allows the iRODS connection pool to
detect broken sockets and re-establish connections without a restart of
the S3 API.
Bug Report
The S3 API uses Boost.Asio to ignore SIGPIPE. However, the iRODS connection pool (if enabled) is created before SIGPIPE is registered. This results in the connection pool not being able to detect and handle broken socket connections.
To fix this issue, we just need to call
std::signal(SIGPIPE, SIG_IGN)
before the connection pool is created.The text was updated successfully, but these errors were encountered: