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

Matching Required and Provided Assemblies on Calls breaks on multiple instance of one component. #84

Open
stiesssh opened this issue Aug 21, 2024 · 0 comments · May be fixed by #85
Open
Assignees

Comments

@stiesssh
Copy link
Collaborator

stiesssh commented Aug 21, 2024

Example Model:

The relevant aspect is that two of the assemblies are instance of the same basic component.

image

Problem when simulation the example model.

Currently, when interpreting calls (entry level system call, external call or infrastructure call), we match only for the provided and required roles. In case of multiple matchees we take the first one.

In case of the example model above, the assemblies BasicComponent3-1 and BasicComponent3-2 have identical roles, as roles are defined on a component level.
Thus, when calling either of the component BasicComponent3-1 and BasicComponent3-2, that call might get directe to the other one.
When i tested it, i always ende up at BasicComponent3-2, even when accordng to the model BasicComponent3-1 should haven been called.

This is probably a left over from when we loadbalancer were not represented in the PCM models. Back then we had to kind of "ignore" the actual connectors and do the loadbalancing programatically.
But now we can do better.

Possible Solution.

Also match the assemblies. The Information is all there in the connectors (see screenshot below) but we don't use it.

image

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

Successfully merging a pull request may close this issue.

1 participant