-
Notifications
You must be signed in to change notification settings - Fork 687
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG]: tcp_client_endpoint must unset is_sending_ during restart #668
Comments
See linked pull request with a proposed solution. After adding some debug prints, I concluded that it's possible for
This is a problem later in
there's nothing queued, no reason to call It's necessary to clear this flag during |
vSomeip Version
v3.4.10
Boost Version
1.82
Environment
Android and QNX
Describe the bug
I've used 3.1.20, 3.3.8 successfully but starting with 3.4.10 I'm seeing an occasional failure on a two-node network. Each node is running
routingmanagerd
with TCP networkMost of the time the system works properly, but when this happens:
End user observation, because data is only flowing one direction over the TCP socket but not the other, is that:
REMOTE_ERROR
because the packets did not flow in this directionIn this situation we were able to use strace and confirm that nodeB routingmanagerd was not even making a
sendto()
call on the file descriptor of the TCP socket.I have not yet observed this behavior on older vsomeip versions 3.1.20 or 3.3.8, only on the newer 3.4.10. Note the capi and boost versions also vary across these observations.
Reproduction Steps
I reproduce this behavior with:
My two nodes are:
I've already ruled out my custom QNX boost-asio reactor because I've observed this problem on both nodes / both directions. I've seen separately where both nodeA (QNX) and nodeB (Android) each get "stuck" in the same way where routingmanagerd will receive but not transmit. It was helpful to know that two machines running totally different operating system reproduce.
The reproduction rate is very low. I cannot reproduce on-demand on my desk.
Expected behaviour
No response
Logs and Screenshots
No response
The text was updated successfully, but these errors were encountered: