CMP Discussion;

This needs more information - which test scripts?

The CTT reuse its session - if the CTT did not activate it then the session should be reused by the server - so we are not understanding the problem.

Are you implying that a number of scripts do not close session that are complete?

Yes, it happens for instance in
Base Info Server Capabilities/011.js MaxNodesPerWrite

There is a WriteRequest with 51 elements, which exceeds our array limit,
the server response is ERR BadEncodingLimitExceeded,
and the secure channel is closed by the stack,
but the session is still open, and now the CTT opens a new session.

And in Base Info Server Capabilities/015.js MaxNodesPerBrowse
just with a Browse Request.

At that point both sessions in the server are occupied,
and need to time out before they can be re-used.

All script should be reviewed to ensure they honor the limit reported by the server, i.e. we should not attempt to write more values then the array limit is set for in a single write.

If a secure channel is closed - but we did not close it or expect it to be closed - we should attempt to recover the session - we should also fail or generate a warning on the test that had the secure channel closure to ensure it is investigated (why did the channel close)