Concurrent handling of exceptions in received aggregate exception structure with supplied exception handlers and marking handled exceptions

• US 8,271,768 B2
• Filed: 11/17/2010
• Issued: 09/18/2012
• Est. Priority Date: 06/25/2007
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Duffy, John Joseph, Callahan, David, Detlefs, David, Morrison, Vance, Grunkemeyer, Brian, Tribble, Eric Dean
• Primary Examiner(s): KIM, KENNETH S
• Application Number:
  US12/948,564
• Publication Number:
  US 20110066834A1
• Time in Patent Office: 671 Days
• Field of Search: None
• US Class Current: 712/244
• CPC Class Codes: G06F 2209/481 Exception handling
• CPC Class Codes: G06F 9/4812 by interrupt, e.g. masked
• CPC Class Codes: G06F 9/52 Program synchronisation; Mutual exclusion, e.g. by means of semaphores

Abstract

Various technologies and techniques are disclosed for providing concurrent exception handling. When one or more exceptions are received from concurrent workers, one or more exception handler functions are supplied. For each respective exception in the exception results, determine if the respective exception is one of a kind of exceptions handled by the one or more exception handler functions. If the respective exception is one of a kind handled by the exception handler functions, then run a particular handler of the exception handler functions and mark the respective exception as handled. Any unhandled exceptions are then processed appropriately. In one implementation, a collection of input data is processed to produce a collection of output results, with the exceptions being interleaved with other output results. In another implementation, a particular exception is selected that represents the multiple exceptions. The selected one particular exception is then thrown.

Claims

1. A computer-readable medium having computer-executable instructions for causing a computer to perform steps, the computer-executable instructions comprising:

first computer-executable instructions that cause the computer to aggregate multiple exceptions into an aggregate exception structure;

second computer-executable instructions that cause the computer to receive exception results comprising the aggregate exception structure;

third computer-executable instructions that cause the computer to supply one or more exception handler functions;

fourth computer-executable instructions that cause the computer to, for each respective exception in the exception results, determine if the respective exception is one of a kind of exceptions handled by the one or more exception handler functions; and

fifth computer-executable instructions that cause the computer to, if the respective exception is one of the kind handled by the exception handler functions, run a particular handler of the exception handler functions and mark the respective exception as handled.

2. The computer-readable medium of claim 1, wherein the exception results are received by catching an aggregate exception object that was thrown.

3. The computer-readable medium of claim 1, wherein the computer-executable instructions further comprise:

sixth computer-executable instructions that cause the computer to, if any unhandled exceptions remain, make note of the remaining unhandled exceptions.

4. The computer-readable medium of claim 3, wherein the computer-executable instructions further comprise:

seventh computer-executable instructions that cause the computer to, if just one unhandled exception remains, rethrow only the one unhandled exception.

5. The computer-readable medium of claim 3, wherein the computer-executable instructions further comprise:

seventh computer-executable instructions that cause the computer to, if more than one unhandled exception remains, construct a new aggregate exception object with just the unhandled exceptions, and rethrow the new aggregate exception object.

6. The computer-readable medium of claim 1, wherein an application programming interface is invoked to supply the one or more exception handler functions.

7. A method for handling multiple exceptions once gathered in the aggregate comprising at least the following steps implemented by at least one computer:

aggregating multiple exceptions into an aggregate exception structure;

receiving exception results comprising the aggregate exception structure;

supplying one or more exception handler functions;

for each respective exception in the exception results, determining if the respective exception is one of a kind of exceptions handled by the one or more exception handler functions; and

if the respective exception is one of the kind handled by the exception handler functions, then running a particular handler of the exception handler functions and marking the respective exception as handled.

8. The method of claim 7, wherein receiving the exception results comprises catching an aggregate exception object that was thrown.

9. The method of claim 7, further comprising:

if any unhandled exceptions remain, then making note of the remaining unhandled exceptions.

10. The method of claim 9, wherein if just one unhandled exception remains, rethrowing only the one unhandled exception.

11. The method of claim 9, wherein if more than one unhandled exception remains, constructing a new aggregate exception object with just the unhandled exceptions, and rethrowing the new aggregate exception object.

12. The method of claim 7, wherein supplying the one or more exception handler functions comprises invoking an application programming interface.

13. A computing device, comprising:

a processing unit; and

storage that stores an application program configured to be executed by the processing unit to

aggregate multiple exceptions into an aggregate exception structure,

receive exception results comprising the aggregate exception structure,

supply one or more exception handler functions,

for each respective exception in the exception results, determine if the respective exception is one of a kind of exceptions handled by the one or more exception handler functions, and

if the respective exception is one of the kind handled by the exception handler functions, run a particular handler of the exception handler functions and mark the respective exception as handled.

14. The computing device of claim 13, wherein the exception results are received by catching an aggregate exception object that was thrown.

15. The computing device of claim 13, wherein the application program is configured to be executed by the processing unit to, if any unhandled exceptions remain, make note of the remaining unhandled exceptions.

16. The computing device of claim 15, wherein the application program is configured to be executed by the processing unit to, if just one unhandled exception remains, rethrow only the one unhandled exception.

17. The computing device of claim 15, wherein the application program is configured to be executed by the processing unit to, if more than one unhandled exception remains, construct a new aggregate exception object with just the unhandled exceptions and rethrow the new aggregate exception object.

18. The computing device of claim 13, wherein an application programming interface is invoked to supply the one or more exception handler functions.