Skip to content
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]: The proxy subscription status is incorrect #857

Open
yanxiaochun1005 opened this issue Feb 28, 2025 · 2 comments
Open

[BUG]: The proxy subscription status is incorrect #857

yanxiaochun1005 opened this issue Feb 28, 2025 · 2 comments
Labels

Comments

@yanxiaochun1005
Copy link

vSomeip Version

V3.4.10

Boost Version

1.7.4

Environment

Ubuntu 22.04

Describe the bug

The proxy mode is used for communication. When the TTL is triggered, the process of canceling and subscriping is carried out. At this time, it is found that the subscription status of the routing management module on the host is inconsistent with that on the proxy side.

Reproduction Steps

No response

Expected behaviour

No response

Logs and Screenshots

No response

@yanxiaochun1005
Copy link
Author

My current modification policy is that the subscription message will be routed to the agent, without judging whether the current subscription is ok.
I wonder if there are any other problems with the above strategy.

@continue1913
Copy link

continue1913 commented Mar 1, 2025

Image
When system load is high, the sub from external app expired, and at the moment, host process sub,stop sub message, send these thress message to proxy, after sent, the proxy send back unsub ack, suback, unsub ack, and now proxy recored no remote sub, the host recored one remote sub and acked, there for the proxy wouldn't send event message to external app,until anyone of them restart。 We want to delete the code "clients_.erase(its_client);" in function "remote_subscription::update" to resolve this problem, is it ok ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants