Table of Contents

Param next attribute not working correctly

Affected versions

  • DataMiner Main Release versions from 10.1.0 [CU15]/10.2.0 [CU3] onwards

  • DataMiner Feature Release versions from 10.2.3 onwards

Cause

Because of an internal lock, if the "next" attribute is used in a Param element in a protocol, all items are added to the polling queue with the needed delay, but they are then all processed at once. The delay is only added after the last parameter of the group, before the group that is polled next.

Fix

No fix is available yet.

Issue description

When the "next" attribute is used in a Param element in a protocol to delay the polling of the next parameter in a group, this delay is not applied correctly.

Propose changes