-
Notifications
You must be signed in to change notification settings - Fork 699
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]: Compliance issue that offer the same serviceID-instanceID with different major versions is not supported #809
Comments
Hi @KareemLMR Yes, I set the major version in offer_service() API and the minor version keeps the default version: |
Hello @zhaoxin39913 And add a log to this if condition marked by the red arrow: |
Hi @KareemLMR, I have made below changes per as your request:
And after change I have triggered "notify-sample" to offer the second service instance 0x1234/0x5678 with version 0xA (There is already a service instance 0x1234/0x5678 with version 0x12 offered by another device within the same network). And from the wireshark we can see that the first time notify-sample was successful to offer the service 0x1234/0x5678 version 0xA, but after call stop_offer() and then start_offer() in "notify-sample", it failed to offer the service again. Below are full log messages from notify-sample:
|
Ok, I see the log you added appeared. That's good. I saw what I wanted to see. Let me try a change at my side and send it to you to try when it is successful. |
Thanks @KareemLMR. I think here we should allow to offer the second same service instance if its major verion is different from the existing same service instance in the network. |
vSomeip Version
v3.4.10
Boost Version
1.7.6
Environment
Ubuntu 20.04
Describe the bug
Hi vsomeip experts,
To follow up #797. I have tested PRS_SOMEIPSD_00512 in SOME/IP SD Spec and confirmed that offering the same serviceID-instanceID with different major versions within the same VLAN is not supported in current vsomeip library.
In my test, I have set up two devices running different vsomeip applications. device A offers service 0x1234/0x5678 with majvor version 0xA, deviceB offers service 0x1234/0x5678 with major version 0xB. After device A has offered the service, next when device B offers the same service with version 0xB, it always reports below error message:
[error] routing_manager_impl::handle_local_offer_service: rejecting service registration. Application: 0201 is trying to offer [1234.5678.11.0] already offered ..
And from the wireshark I confirmed that the service 0x1234/0x5678/0xB is not offered. It seems like a missing feature that vsomeip stack need to support PRS_SOMEIPSD_00512 (Supporting multiple versions of the same service),
Reproduction Steps
100% reproduced.
Expected behaviour
vsomeip stack need to support PRS_SOMEIPSD_00512 (Supporting multiple versions of the same service)
Logs and Screenshots
[error] routing_manager_impl::handle_local_offer_service: rejecting service registration. Application: 0201 is trying to offer [1234.5678.11.0] already offered
The text was updated successfully, but these errors were encountered: