Vivien Delage
2013-09-17 15:50:05 UTC
Hello everyone,
We are using Asio on Windows with Visual C++ 2008 in a Windows 7 64 bit build. We recently did a test run with the latest Asio version from Boost 1.54 and experienced some unexpected behavior that does not occur with our current 1.53-based setup.
In particular, calls to async_read would fail out of the blue with an EOF error, even when using the local loopback connection. We observed that the connection was really closed in the system, so it does not seem to be an issue of Asio reporting a disconnect when there is none. It rather seems that the connection is just lost randomly for no apparent reason.
We also saw async_write callbacks returning with no error code but with a number of bytes written equal to 0.
Our typical setup:
We have a cluster of X nodes, all acting as peers, everyone being connected to everyone else.
We use a two way communication between them: every node initiates an async_read waiting for data to be send from its peer. In the meantime it can send data himself on the same socket through an async_write.
We never close any sockets manually or shut down any nodes, the connections just seem to fail by themselves.
We are quite puzzled by this behavior which is currently preventing us from doing the upgrade to 1.54. If you could provide some insight on what might be going wrong here, we would be very grateful.
Best regards,
VIVIEN DELAGE
Senior software engineer / Quantum
___________________________
RTT AG
Rosenheimer Straße 145
81671 München
Germany
www.rtt.ag
Realtime Technology Aktiengesellschaft, Munich, Germany
Commercial Registry: 125910; Amtsgericht Muenchen
Board: Ludwig A. Fuchs / Roberto Schettler
Chairman of the Supervisory Board: Dr. Marcus Englert
Diese E-Mail enthaelt vertrauliche und/oder rechtlich geschuetzte
Informationen. Wenn Sie nicht der richtige Adressat sind oder diese
E-Mail irrtuemlich erhalten haben, informieren Sie bitte sofort den Absender
und vernichten Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte
Weitergabe dieser Mail ist nicht gestattet.
This e-mail may contain confidential and/or privileged information. If
you are not the intended recipient (or have received this e-mail in error)
please notify the sender immediately and destroy this e-mail. Any
unauthorized copying, disclosure or distribution of the material in
this e-mail is strictly forbidden.
We are using Asio on Windows with Visual C++ 2008 in a Windows 7 64 bit build. We recently did a test run with the latest Asio version from Boost 1.54 and experienced some unexpected behavior that does not occur with our current 1.53-based setup.
In particular, calls to async_read would fail out of the blue with an EOF error, even when using the local loopback connection. We observed that the connection was really closed in the system, so it does not seem to be an issue of Asio reporting a disconnect when there is none. It rather seems that the connection is just lost randomly for no apparent reason.
We also saw async_write callbacks returning with no error code but with a number of bytes written equal to 0.
Our typical setup:
We have a cluster of X nodes, all acting as peers, everyone being connected to everyone else.
We use a two way communication between them: every node initiates an async_read waiting for data to be send from its peer. In the meantime it can send data himself on the same socket through an async_write.
We never close any sockets manually or shut down any nodes, the connections just seem to fail by themselves.
We are quite puzzled by this behavior which is currently preventing us from doing the upgrade to 1.54. If you could provide some insight on what might be going wrong here, we would be very grateful.
Best regards,
VIVIEN DELAGE
Senior software engineer / Quantum
___________________________
RTT AG
Rosenheimer Straße 145
81671 München
Germany
www.rtt.ag
Realtime Technology Aktiengesellschaft, Munich, Germany
Commercial Registry: 125910; Amtsgericht Muenchen
Board: Ludwig A. Fuchs / Roberto Schettler
Chairman of the Supervisory Board: Dr. Marcus Englert
Diese E-Mail enthaelt vertrauliche und/oder rechtlich geschuetzte
Informationen. Wenn Sie nicht der richtige Adressat sind oder diese
E-Mail irrtuemlich erhalten haben, informieren Sie bitte sofort den Absender
und vernichten Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte
Weitergabe dieser Mail ist nicht gestattet.
This e-mail may contain confidential and/or privileged information. If
you are not the intended recipient (or have received this e-mail in error)
please notify the sender immediately and destroy this e-mail. Any
unauthorized copying, disclosure or distribution of the material in
this e-mail is strictly forbidden.