vsomeip
vsomeip copied to clipboard
COVESA
[BUG]Vsomeip-3.5.1 Client UDP Port Closed, Server Still Sending Events
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
Uploading tcpdump_20241014200558.zip…
@FishPickBeans cannot open the tcpdump
- The above is the tcpdump released by Vsomeip 3.5.1, but we have already removed tcpdump and are only releasing images now!
- 172.168.2.30 is the server-side, 172.168.2.80 is the client-side, UDP transmission!
- The image shows that the server sends an Event with a two second cycle, but the client process has been killed and there is no 1-second interval to SUB!
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! thank you!
Hello, I have seen this issue as well. It seems that if the client exits and does not send a StopSubscribe the server keeps publishing the Event even after the UDP socket has been closed.
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.
Hello @duartenfonseca ,
See attachment. It has packet capture, json configuration, and test code that replicates the issue.
Both client and service are running on Linux (on two different machines). Event is published over UDP.
which version do you use?
Sorry forgot to answer this, but this was using vsomeip version 3.5.1.
