View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
000870310000-004: ServicesSpecpublic2023-02-16 03:112023-08-21 16:00
ReporterRandy Armstrong Assigned ToMatthias Damm  
PrioritynormalSeverityminorReproducibilityhave not tried
Status closedResolutionfixed 
Product Version1.05.02 
Target Version1.05.03 RC1Fixed in Version1.05.03 RC1 
Summary0008703: Add Bad_ServerTooBusy Error Code
Description

Servers need to be able to throttle write/call operations which consume resources.

The Bad_ServerTooBusy allows the server to reject any individual operation because it does not currently have the resources needed to process it. Clients know that they can try again later.

Servers may reject entire Call/Write requests if they return this error as a service level error.

This provides a clean solution to problem uncovered at PWN2OWN 2023 where calling ConditionRefresh over and over resulted in a crash.

TagsNo tags attached.
Commit Version
Fix Due Date

Activities

Matthias Damm

2023-02-20 22:40

developer   ~0018777

Added status code to Table 182 – Common Service Result Codes

Bad_ServerTooBusy
The Server does not have the resources to process the request at this time.
This can be caused by a general overload of the Server or by too many outstanding requests for the calling Client.

Jim Luth

2023-02-28 17:06

administrator   ~0018811

Agreed to changes edited in Web Meeting.

Issue History

Date Modified Username Field Change
2023-02-16 03:11 Randy Armstrong New Issue
2023-02-20 22:40 Matthias Damm Assigned To => Matthias Damm
2023-02-20 22:40 Matthias Damm Status new => resolved
2023-02-20 22:40 Matthias Damm Resolution open => fixed
2023-02-20 22:40 Matthias Damm Fixed in Version => 1.05.03 RC1
2023-02-20 22:40 Matthias Damm Note Added: 0018777
2023-02-28 17:06 Jim Luth Status resolved => closed
2023-02-28 17:06 Jim Luth Note Added: 0018811