[ 
https://issues.apache.org/jira/browse/IGNITE-27914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dmitrii Zabotlin updated IGNITE-27914:
--------------------------------------
    Description: 
The Platform C++ ODBC Tests. DEB package (Ubuntu 22.04 Linux container) 
sometimes fail with exit code 141

The reason of this failure might be related to the SIGPIPE signal from the 
socket in case the another side of the connection is already closed when we 
trying to write into the socket. In any case we do not need to use SIGPIPE from 
the socket as long as we checking return code.

For linux it can be disabled with the MSG_NOSIGNAL option in send function.
For MacOS it can be disabled with the SO_NOSIGPIPE options for setsockopt 
function.

  was:The Platform C++ ODBC Tests. DEB package (Ubuntu 22.04 Linux container) 
sometimes fail with exit code 141


> C++3.0: Ignore SIGPIPE and use MSG_NOSIGNAL for sockets in client
> -----------------------------------------------------------------
>
>                 Key: IGNITE-27914
>                 URL: https://issues.apache.org/jira/browse/IGNITE-27914
>             Project: Ignite
>          Issue Type: Bug
>          Components: odbc, platforms ai3
>    Affects Versions: 3.1
>            Reporter: Vadim Pakhnushev
>            Assignee: Dmitrii Zabotlin
>            Priority: Major
>              Labels: ignite-3
>             Fix For: 3.2
>
>          Time Spent: 1h
>  Remaining Estimate: 0h
>
> The Platform C++ ODBC Tests. DEB package (Ubuntu 22.04 Linux container) 
> sometimes fail with exit code 141
> The reason of this failure might be related to the SIGPIPE signal from the 
> socket in case the another side of the connection is already closed when we 
> trying to write into the socket. In any case we do not need to use SIGPIPE 
> from the socket as long as we checking return code.
> For linux it can be disabled with the MSG_NOSIGNAL option in send function.
> For MacOS it can be disabled with the SO_NOSIGPIPE options for setsockopt 
> function.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to