Again we do not see a problem - client handle are not looked at on a server - if a client want s to set three variable in a subscription to the same client handle - it is ok - maybe the server is reporting three different temperature sensors - but all report the current air temperature - the client might subscribe for all three with the same client handle - since they will go to the same display of current temperature - maybe not the best logic, but it is not the servers job to evaluate why.

The described CTT test case fails with an error, when cleaning up test case by deleting previously created monitored items: "Delete MonitoredItems.Response.Results[0]=BadMonitoredItemIdInvalid(0x80420000), but Good". The proprietary OPC UA library that we use to implement our server logs a warning, when client handles are duplicated "Removing MonitoredItem "1521318008" with duplicate ClientHandle "116" from Subscription "3260890069". Assuming retry of a failed creation request." When preventing duplicated monitored items, log of OPC UA lib do not show described warning and test passes. I will ask the maintainer of the lib to give me a comment.