tpcall sequence number may duplicate
|Priority:||Normal (Code 4)||Due date:|
The situation might cause in some hypothetical error scenarios, where at timeout conditions or tpcancel() and having tpcalls() in different threads at very high performance (1000s of calls per second), might cause request/reply mismatch.
#1 Updated by Madars about 1 year ago
- Description updated (diff)
Fixed tpcall()/tpconnect() to use unique internal sequence numbers. Note that these identifiers are internal one (they are not call descriptors).
Available from Enduro/X release 7.5.38+, 8.0.1+.
#2 Updated by Madars about 1 year ago
- Status changed from New to Resolved
- % Done changed from 0 to 100
#3 Updated by Madars about 1 year ago
- Status changed from Resolved to Closed