It usually means the last handler in the pipeline did not handle the exception. ! java.net.SocketException: Connection reset Checking the operations outcomes it seems CosmosDB queries are working as ...