Details
Description
Each received RPC call addressing a new RPC activity (by using an up to now unused RPC ActivityUUID) will aquire memory to handle the operation.
However, there is no limit implemented in RPC regarding the possible parallel activities. This may lead to memory exhaustion.
Only a fix amount of parallel activities shall be possible to prevent this memory exhaustion. If the maximum amount is reached, the oldest existing activity currently not used shall be re-used.
Attachments
Issue Links
- discovered
-
PSDCERPC-81 RPC Activity timeout requested by local endpoint is not respected
-
- Closed
-
- relates to
-
PSPNS-2917
Upgrade DCERPC to V4.2.0.5
-
- Closed
-
-
PSPNS-2918
update to DCERPC V4.2.1.0
-
- Closed
-
- mentioned in
-
Page Loading...
-
-
-
-
-