System and method for management of requests

• US 7,653,905 B1
• Filed: 02/11/2005
• Issued: 01/26/2010
• Est. Priority Date: 09/08/2004
• Status: Active Grant

• Current Assignee: Liberty Peak Ventures, LLC (Dominion Harbor Enterprises, LLC)
• Original Assignee: American Express Travel Related Services Company, Inc. (American Express Company)
• Inventors: Lingamneni, Krishna K.
• Primary Examiner(s): Sough, Hyung S
• Assistant Examiner(s): Wu, Qing-Yuan
• Application Number:
  US10/906,279
• Time in Patent Office: 1,810 Days
• Field of Search: 719313-314, 718100-101, 718/104
• US Class Current: 718/100
• CPC Class Codes: G06F 2209/5018 Thread allocation
• CPC Class Codes: G06F 9/4843 by program, e.g. task dispatcher, supervisor, operating system
• CPC Class Codes: G06F 9/546 Message passing systems or structures, e.g. queues

Abstract

The present invention provides an online messaging architecture configured to process incoming request messages and provide reply messages in an efficient manner. The invention reduces processing overhead within a mainframe computing environment were individual requests are treated as individual transactions by instead storing requests within a queue, spawning necessary processes according to the queue and processing multiple transactions in a pseudo batch manner.

Claims

1. A method performed by a server computer for facilitating management of a request from a user computer, said method comprising:

receiving, by said server computer, said request from said user computer;

storing said request into a first queue;

generating a trigger message in response to said request;

storing said trigger message in a second queue;

retrieving business logic corresponding at least in part to said request;

storing a message corresponding to said request into a thread count queue, a number of messages stored in said thread count queue corresponding to a number of threads that have begun executing;

determining a number of executing threads using said thread count queue;

retrieving said request from said first queue;

determining a number of threads to execute said request;

spawning new threads to process said request based upon said number of executing threads and said number of threads to execute said request;

tracking said number of executing threads with respect to said thread count queue to prevent over spawning;

formatting a reply message corresponding to said request, wherein said formatting is based upon said business logic; and

storing said reply message into a third queue.

2. The method of claim 1, further including spawning new threads to process said request based on a pre-defined equation.

3. The method of claim 1, further including validating an identity of a user based upon authentication credentials imbedded in said request.

4. The method of claim 1, where said formatting further includes processing errors occurring during said formatting of said reply message.

5. The method of claim 1, wherein said first queue, second queue and third queue are located in the same queue.

6. A computer-readable storage medium storing thereon a set of instructions executable by a general purpose computer configured to perform a method for facilitating management of a request from a user computer, said method comprising:

receiving a request from said user computer;

storing said request into a first queue;

generating a trigger message in response to said request;

storing said trigger message in a second queue;

retrieving business logic corresponding at least in part to said request;

storing a message corresponding to said request into a thread count queue, a number of messages stored in said thread count queue corresponding to a number of threads that have begun executing;

determining a number of executing threads using said thread count queue;

retrieving said request from said first queue;

determining a number of threads to execute said request;

spawning new threads to process said request based upon said number of executing threads and said number of threads to execute said request;

tracking said number of executing threads with respect to said thread count queue to prevent over spawning;

formatting a reply message corresponding to said request, wherein said formatting is based upon said business logic; and

storing said reply message into a third queue.