You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The relevant aspect is that two of the assemblies are instance of the same basic component.
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.
The text was updated successfully, but these errors were encountered:
Example Model:
The relevant aspect is that two of the assemblies are instance of the same basic component.
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.
The text was updated successfully, but these errors were encountered: