-
Type: Bug
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Internal Client
-
None
-
Fully Compatible
-
ALL
-
v6.3
-
Service Arch 2023-02-20, Service Arch 2023-03-06, Service Arch 2023-03-20
-
105
We have tripwire assertions in the server that internal-only exceptions should not escape back to the client. This is an important check to have, but it is not technically correct in the case of DBDirectClient.
DBDirectClient enters the service entry point using an OperationContext which doesn't belong to the command itself. This means if the thread using the DBDirectClient is interrupted with some internal exception that the interruptor knows will be handled by their thread, from the point of view of the service entry point, this exception "has escaped to the client", but in fact it has only escaped to the internal thread.
- is caused by
-
SERVER-49040 Avoid transmission of internal-only errors
- Closed