[PSDCERPC-81] RPC Activity timeout requested by local endpoint is not respected - Hilscher Ticket

Details

Type: Bug
Status: Closed
Priority: Minor
Resolution: Fixed
Affects Version/s: None
Fix Version/s: V4.2.0.5, V4.2.1.0
Component/s: Task
Labels:
None

Account:
SPC Components (SPCCOMPONENTS)

Description

When the receiver of an RPC Call sets the timeout of the activity, in several situations this is not respected by RPC implementation and unexected value is used.

The following scenarios are affected:

Timeout is expected to be "infinite". Instead timeout of 5 seconds is used
Timeout is expected to be shorter than 5 seconds. Instead timeout of 5 seconds is used.

Attachments

Issue Links

discovered by

PSDCERPC-80 missing limit for parallel RPC activities may lead to memory exhaustion

Closed

relates to

PSPNS-2923 Cyclic connection can not be established any more after several connection establishments

Closed

PSPNS-2917 Upgrade DCERPC to V4.2.0.5

Closed

PSPNS-2918 update to DCERPC V4.2.1.0

Closed

mentioned in: Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...

(5 mentioned in)

Expenses

Activity

Status Description

People

Reporter:

Benjamin Meyer

Votes:

0 Vote for this issue

Watchers:

0 Start watching this issue

Dates

Created:

2020-06-05 14:37

Updated:

2021-05-18 13:34

Resolved:

2020-06-15 14:54