System and method for providing highly available processing of asynchronous requests using distributed request and response queues and a service processor

• US 7,953,787 B2
• Filed: 03/02/2009
• Issued: 05/31/2011
• Est. Priority Date: 05/02/2002
• Status: Active Grant

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: Oracle International Corporation (Oracle Corporation)
• Inventors: Upton, Mitch, Potter, Timothy A., Golding, Christa
• Primary Examiner(s): BAROT, BHARAT
• Application Number:
  US12/396,375
• Publication Number:
  US 20090164571A1
• Time in Patent Office: 820 Days
• Field of Search: 709201-203, 709217-219, 709225-226
• US Class Current: 709/201
• CPC Class Codes: H04L 67/10 in which an application is distributed across nodes in the network software deployment G06F8/60; multiprogramming arrangements G06F9/46
• CPC Class Codes: H04L 69/329 in the application layer [OSI layer 7]
• CPC Class Codes: H04L 69/40 for recovering from a failure of a protocol instance or entity, e.g. service redundancy protocols, protocol state redundancy or protocol service redirection management of faults, events, alarms or notifications in data switching networks H04L41/06
• CPC Class Codes: Y10S 707/99952 Coherency, e.g. same view to multiple users
• CPC Class Codes: Y10S 707/99953 Recoverability

Abstract

Highly-available processing of an asynchronous request can be accomplished in a single transaction. A distributed request queue receives a service request from a client application or application view client. A service processor is deployed on each node of a cluster containing the distributed request queue. A service processor pulls the service request from the request queue and invokes the service for the request, such as to an enterprise information system. If that service processor fails, another service processor in the cluster can service the request. The service processor receives a service response from the invoked service and forwards the service response to a distributed response queue. The distributed response queue holds the service response until the response is retrieved for the client application.

Claims

1. A system comprising:

a client that invokes an asynchronous service by supplying a request document that defines the asynchronous service invocation and a response listener to handle a response to the asynchronous service invocation;

a distributed input queue including multiple physical queues, wherein upon receiving the request document, a service request object is instantiated based on the request document and placed in the distributed input queue, wherein the service request object identifies a destination to which the response listener is pinned;

a service processor to pull the service request object from the distributed input queue and invoke the service, wherein the service processor receives a response to the service invocation;

a distributed output queue to receive and store the response from the service processor, the distributed output queue including more than one physical queue, wherein the service processor uses the identification in the service request object to determine the physical queue to receive the response.

2. A system according to claim 1, further comprising:

an enterprise information system containing the service invoked by the first service processor.

3. A system according to claim 1, wherein the service processor is packaged as a message-driven Enterprise JAVABean.

4. A system according to claim 1, further comprising:

an application view client for sending the service request to the distributed input queue and retrieving the response from the distributed output queue on behalf of the client.

5. A system according to claim 4, wherein the application view client generates failure recovery semantics for the client.

6. A system according to claim 4, wherein the distributed output queue is adapted to store the response until the response is retrieved by the application view client.

7. A system according to claim 4, wherein the application view is determines whether any responses are waiting in the distributed output queue for the client.

8. A system according to claim 4, further comprising:

a client identifier for identifying the client application, the client identifier used to process the service request and response for the client.

9. A system according to claim 1, further including a second service processor that is deployed on a different node in a cluster.

10. A method for highly available processing of asynchronous requests, said method comprising:

receiving, from a client, a request document that defines an asynchronous service invocation and a response listener to handle a response to the asynchronous service invocation;

instantiating a service request object based on the request document and storing the service request object into a distributed input queue that includes multiple physical queues, wherein the service request object identifies a destination to which the response listener is pinned;

pulling, by a service processor, the service request object from the distributed input queue and invoking the service by the service processor, wherein the service processor receives a response to the service invocation;

receiving the response from the service processor and storing the response into a distributed output queue, the distributed output queue including more than one physical queue, wherein the service processor uses the identification in the service request object to determine the physical queue to receive the response.

11. The method of claim 10, further comprising:

invoking, by the service processor, an enterprise information system (EIS).

12. The method of claim 10, wherein the service processor is packaged as a message-driven Enterprise JAVABean.

13. The method of claim 10, further comprising:

sending, by an application view client, the service request to the distributed input queue and retrieving the response from the distributed output queue on behalf of the client.

14. The method of claim 13, wherein the application view client generates failure recovery semantics for the client.

15. The method of claim 13, wherein the distributed output queue stores the response until the response is retrieved by the application view client.

16. The method of claim 13, wherein the application view is determines whether any responses are waiting in the distributed output queue for the client.

17. The method of claim 10, further comprising:

supplying a client identifier for identifying the client, the client identifier used to process the service request and response for the client.

18. The method of claim 10, further including providing a second service processor that is deployed on a different node in a cluster.