1. Simulator and Java API: Added logic to handle connection Id
verification/assignment when there are other exceptions also being raised in the request message. Such as cluster version mismatch scenario. 2. Simulator: by default, the connection Id is checked and logged as warning messages if does not match. The flag wil be reset when drive code with this feature is released and enforced. 3. Simulator: uses "next available unique timestamp" (type long) for connection Ids to be more consistent with the drive behavior.
Loading
Please sign in to comment