-
Notifications
You must be signed in to change notification settings - Fork 710
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]: <title>The server closing the TCP connection when stopping all services. #825
Comments
Can you point out which requirement in the SOME/IP Spec defines such behaivor ? |
Dear @zhaoxin39913 , please check the below Spec. [PRS_SOMEIP_00709] [PRS_SOMEIP_00710] [PRS_SOMEIP_00711] Rational: |
Hi @AGN-2022 , So the expected behavior is the server only closes the listen socket but keeps established connection sockets after stopping the service, right ? Do you need this only for TC8 certificate ? To my understanding there is no function impact from application PoV. And the Spec also does not define how the server reacts subsequent requests from client after stopping the service but the connection socket is not closed by client. |
Hi @zhaoxin39913 , If you observe pcap log, soon after Frame# 28 (which is Stop-Offer), Frame# 30 is triggering TCP-connection close which is not intended behavior as per Spec. I'm not sure about TC8 certificate. I believe |
vSomeip Version
v3.4.10
Boost Version
1.59
Environment
Ubuntu 20.04
Describe the bug
The TCP connection close request should not get triggered by Server, in this case this is the issue from VSOME/IP stack.
I observed the same behavior in 3.1.20.3 and 3.4.10.
Attached pcap log and Routing manager terminal log: TCP_close_issue_pcap_RM_logs.zip
Reproduction Steps
Steps 3 to 5 can reproduce the issue.
Expected behaviour
The server shall not stop the TCP connection when stopping all services.
Let the client to process control data & shutdown the connection by itself.
Logs and Screenshots
No response
The text was updated successfully, but these errors were encountered: