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
I have deployed IDS-testbed, which is using version 8.0.2 for the connector, and implemented the N times usage policy allowing just two data downloads.
I have performed a contract agreement between the connectors and I get the datalink to download the data.
At this point, I have used de tool Jmeter to perform load testing against the connector.
It has been requested the data multiple times in a small period of time.
I have been able to download the data more than the defined usage policy implementation. It should just give me two data downloads and actually I have been able to download it more times (six downloads) as it is detailed in the image below.
The rule implementation is not working correctly under load testing.
I guess that the reason for this behavior could be that it is not counting the number of successful downloads, and it gives to the consumer more than the admitted ArtifactResponeMessage.
In the following image is my understanding of the behavior and a procedure proposal that could fix this issue.
The text was updated successfully, but these errors were encountered:
I have deployed IDS-testbed, which is using version 8.0.2 for the connector, and implemented the N times usage policy allowing just two data downloads.
I have performed a contract agreement between the connectors and I get the datalink to download the data.
At this point, I have used de tool Jmeter to perform load testing against the connector.
It has been requested the data multiple times in a small period of time.
I have been able to download the data more than the defined usage policy implementation. It should just give me two data downloads and actually I have been able to download it more times (six downloads) as it is detailed in the image below.
The rule implementation is not working correctly under load testing.
I guess that the reason for this behavior could be that it is not counting the number of successful downloads, and it gives to the consumer more than the admitted ArtifactResponeMessage.
In the following image is my understanding of the behavior and a procedure proposal that could fix this issue.
The text was updated successfully, but these errors were encountered: