-
Notifications
You must be signed in to change notification settings - Fork 713
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]Vsomeip-3.5.1 Client UDP Port Closed, Server Still Sending Events #781
Comments
@FishPickBeans cannot open the tcpdump |
We speculate that after the client was killed, the server did not clear the client's last SUB information, resulting in continuous sending of events! Sorry, we chose vsomeip3.4.10 and this issue did not occur! |
Hello, If the client sends the StopSubscribe before exiting, the service stops publishing the event as expected. The TTL setting in the service discovery should kick in when the client exits and it stops sending the Subscribe. I can provide logs/packet capture if necessary. It is pretty easy to replicate. |
hi @anthonypayne-GM, which version do you use? please provide your pcap's, and how you got that reproduction. |
vSomeip Version
v3.5.1
Boost Version
1.84
Environment
Linux
Describe the bug
Linux use Vsomeip-3.5.1 code, Steps:
Firstly, client subscribe server's event-group successed.(vsomip_server.json noly support UDP)
Secondly, client reboot, But server still sending client's sub event.
Reproduction Steps
Linux use Vsomeip-3.5.1 code, Steps:
Firstly, client subscribe server's event-group successed.(vsomip_server.json noly support UDP)
Secondly, client reboot, But server still sending client's sub event.
Thirdly, tcpdump parse by wireshark.
Expected behaviour
after client reboot, server should stop sending before client's sub event.
Logs and Screenshots
vsomeip-3.5.1 log.txt
The text was updated successfully, but these errors were encountered: