Message handling multiplexer

• US 9,548,949 B2
• Filed: 12/17/2013
• Issued: 01/17/2017
• Est. Priority Date: 05/29/2007
• Status: Active Grant

• Current Assignee: Red Hat, Inc. (International Business Machines Corporation)
• Original Assignee: Red Hat, Inc. (International Business Machines Corporation)
• Inventors: Ban, Bela, Blagojevic, Vladimir
• Primary Examiner(s): Harold, Marsha D Banks
• Assistant Examiner(s): WYLLIE, CHRISTOPHER T
• Application Number:
  US14/109,133
• Publication Number:
  US 20140105220A1
• Time in Patent Office: 1,127 Days
• Field of Search: None
• US Class Current: 1/1
• CPC Class Codes: H04L 12/1881 with schedule organisation, e.g. priority, sequence management
• CPC Class Codes: H04L 49/90 Buffering arrangements

Abstract

A method and apparatus for processing message is described. In one embodiment, an application programming interface is configured for receiving and sending messages. A multiplexer receives messages from different servers. A service name is coupled to each message with the corresponding destination service. A single shared channel is formed. The messages are processed over the single shared channel.

Claims

1. A method comprising:

receiving messages from a plurality of servers by a processing device executing a multiplexer, wherein the multiplexer comprises a concurrent transport protocol stack;

coupling, by the processing device executing the multiplexer, a service name to each message with a corresponding destination service;

maintaining, by the processing device executing the multiplexer, a set of queues, one queue per service name;

adding, by the processing device executing the multiplexer, a message to a corresponding queue in view of the service name of the corresponding queue, to form a single shared channel;

maintaining, by the processing device executing the multiplexer, an out-of-band thread pool and a regular thread pool of the concurrent transport protocol stack, wherein the out-of-band thread pool and the regular thread pool are coupled to receive the messages from the set of queues;

dispatching the messages marked as out-of-band from a sender to a thread of the out-of-bound thread pool; and

dispatching all other messages from the sender to a thread of the regular thread pool.

2. The method of claim 1 further comprising:

multiplexing the messages onto the single shared channel; and

sending the messages over the single shared channel.

3. The method of claim 1 further comprising:

determining the service name for each message from the single shared channel; and

channeling each message to the corresponding destination service based on the service name of each message.

4. The method of claim 1 further comprising concurrently dispatching messages to different services from a same server using the concurrent transport protocol stack.

5. The method of claim 4 further comprising processing one thread of the concurrent stack for messages to a same service from the same server.

6. The method of claim 1 wherein receiving messages comprise packets with concurrent transport protocol stack, wherein the concurrent transport protocol stack comprises at least one of a multicast receiver thread, a unicast receiver thread, or a connection table.

7. The method of claim 1 further comprising sending the messages up the concurrent transport protocol stack to a corresponding channel of a channel layer of the multiplexer, from the channel layer to a building block layer of the multiplexer, the building block layer layered on top of the channel layer, and from the building block layer to an application programming interface of the multiplexer, the application programming interface layered on top of the building block.

8. A non-transitory machine-accessible storage medium comprising data that, when accessed by a processing device, cause the processing device to:

receive messages from a plurality of servers by the processing device executing a multiplexer, wherein the multiplexer comprises a concurrent transport protocol stack;

couple, by the processing device executing the multiplexer, a service name to each message with a corresponding destination service;

maintain, by the processing device executing the multiplexer, a set of queues, one queue per service name;

add, by the processing device executing the multiplexer, a message to a corresponding queue in view of the service name of the corresponding queue, to form a single shared channel;

maintain, by the processing device executing the multiplexer, an out-of-band thread pool and a regular thread pool of the concurrent transport protocol stack, wherein the out-of-band thread pool and the regular thread pool are coupled to receive the messages from the set of queues;

dispatch the messages marked as out-of-band from a sender to a thread of the out-of-bound thread pool; and

dispatch all other messages from the sender to a thread of the regular thread pool.

9. The non-transitory machine-accessible storage medium of claim 8 wherein the data that, when accessed by the processing device, further causes the processing device to:

multiplex the messages onto the single shared channel; and

send the messages over the single shared channel.

10. The non-transitory machine-accessible storage medium of claim 8 wherein the data that, when accessed by the processing device, further causes the processing device to:

determine the service name for each message from the single shared channel; and

channel each message to the corresponding destination service in view of the service name of each message.

11. The non-transitory machine-accessible storage medium of claim 8 wherein the data that, when accessed by the processing device, further causes the processing device to dispatch concurrently messages to different services from a same server using the concurrent transport protocol stack.

12. The non-transitory machine-accessible storage medium of claim 11 wherein the data that, when accessed by the processing device, further causes the processing device to process one thread of the concurrent stack for messages to a same service from the same server.

13. The non-transitory machine-accessible storage medium of claim 8 wherein the messages comprise packets with the concurrent transport protocol stack, wherein the concurrent transport protocol stack comprises at least one of a multicast receiver thread, a unicast receiver thread, or a connection table.

14. The non-transitory machine-accessible storage medium of claim 8 wherein the data that, when accessed by the processing device, further causes the processing device to send the messages up the concurrent transport protocol stack to a corresponding channel of a channel layer, a building block layered on top of the channel layer, and an application programming interface layered on top of the building block.

15. A method comprising:

maintaining, by a processing device executing a multiplexer, a set of queues, one queue per service name;

maintaining, by the processing device executing the multiplexer, a thread pool, wherein the thread pool is coupled to receive messages from the set of queues, wherein the thread pool comprises a regular thread pool and an out-of-bound thread pool;

receiving messages from a plurality of servers by the processing device executing the multiplexer;

associating, by the processing device executing the multiplexer, a service name to each message with a corresponding destination service;

adding, by the processing device executing the multiplexer, a message to a corresponding queue in view of the service name of the corresponding queue;

forming a single shared channel by the multiplexer; and

processing the messages from the set of queues with the thread pool over the single shared channel, wherein processing the messages comprises;

forming one thread from the regular thread pool for the messages from a sender, and

forming one thread from the out-of-band thread pool for the messages marked as out of band from the sender, wherein the messages processed with the one thread from the out-of-band thread pool are processed before the messages processed with the one thread from the regular thread pool.

16. The method of claim 15 further comprising:

multiplex the messages onto the single shared channel; and

sending the messages over the single shared channel.

17. The method of claim 15 further comprising:

determining, by the processing device executing the multiplexer, the service name for each message from the single shared channel; and

channeling each message to the corresponding destination service in view of the service name of each message.

18. The method of claim 15 further comprising concurrently dispatching, by the thread pool, the messages to different services from a same server.

19. The method of claim 15 wherein the processing the messages further comprises processing the messages to a same service from a same server using one thread.

20. The method of claim 15 wherein receiving messages comprise packets with concurrent transport protocol stack, wherein the concurrent transport protocol stack comprises at least one of a multicast receiver thread, a unicast receiver thread, or a connection table.