SYSTEM AND METHOD FOR MANAGING MESSAGE QUEUES FOR MULTINODE APPLICATIONS IN A TRANSACTIONAL MIDDLEWARE MACHINE ENVIRONMENT

• US 20130086199A1
• Filed: 08/10/2012
• Published: 04/04/2013
• Est. Priority Date: 09/30/2011
• Status: Active Grant

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: Oracle International Corporation (Oracle Corporation)
• Inventors: Frank, Richard, Little, Todd, Kaimalettu, Arun, Tominna, Leonard
• Granted Patent: US 9,558,048 B2
• Time in Patent Office: Days
• US Class Current: 709/213
• CPC Class Codes: G06F 2209/548 Queue
• CPC Class Codes: G06F 9/544 Buffers; Shared memory; Pipes
• CPC Class Codes: G06F 9/546 Message passing systems or structures, e.g. queues

Abstract

A middleware machine environment can manage message queues for multimode applications. The middleware machine environment includes a shared memory on a message receiver, wherein the shared memory maintains one or more message queues for the middleware machine environment. The middleware machine environment further includes a daemon process that is capable of creating at least one message queue in the shared memory, when a client requests that the at least one message queue be set up to support sending and receiving messages. Additionally, different processes on a client operate to use at least one proxy to communicate with the message server. Furthermore, the middleware machine environment can protect message queues for multimode applications using a security token created by the daemon process.

Claims

1. A system for managing message queues in a middleware machine environment, comprising:

one or more microprocessors;

a shared memory on a message receiver, wherein the shared memory maintains one or more message queues in the middleware machine environment; and

a daemon process, running on the one or more microprocessors, that is capable of creating at least one message queue in the shared memory, when a client requests that the at least one message queue be set up to support sending and receiving messages.

2. The system according to claim 1, wherein different processes on a client operate to use at least one proxy to communicate with the message server.

3. The system according to claim 1, wherein the daemon process is further capable of creating a security token on a first server node, when a message queue is created in the shared memory on the first server node for communicating with a second server node.

4. The system according to claim 3, wherein the daemon process is further capable of sending the security token from the first server node to the second server node via a first secured network.

5. The system according to claim 4, wherein the daemon process is further capable of allowing the second server node to use the security token to send a message to the message queue in the shared memory.

6. The system according to claim 1, wherein the daemon process is capable of creating and reserving a local message queue for local messaging.

7. The system according to claim 6, wherein the local message queue is outside of the shared memory.

8. The system according to claim 6, wherein a local server process operates to receive messages from both the local message queue and the at least one remote message queue.

9. The system according to claim 1, wherein a client is allowed to determine whether a queue is created on a shared memory or a private memory.

10. The system according to claim 1, wherein a client is allowed to continue to perform write operations in the shared memory on a server machine without waiting for a recovery, when an interruption occurs on the server machine.

11. A method for managing message queues in a middleware machine environment, comprising:

providing a shared memory on a message receiver, wherein the shared memory maintains one or more message queues in the middleware machine environment; and

creating, via a daemon process running on one or more microprocessors, at least one message queue in the shared memory, when a client requests that the at least one message queue be set up to support sending and receiving messages.

12. The method according to claim 11, further comprising allowing different processes on a client to use at least one proxy to communicate with the message server.

13. The method according to claim 11, further comprising creating a security token on a first server node, when a message queue is created in the shared memory on the first server node for communicating with a second server node.

14. The method according to claim 13, further comprising sending the security token from the first server node to the second server node via a first secured network.

15. The method according to claim 14, further comprising allowing the second server node to use the security token to send a message to the message queue in the shared memory.

16. The method according to claim 11, further comprising creating and reserving a local message queue for local messaging.

17. The method according to claim 16, further comprising allowing the local message queue be outside of the shared memory.

18. The method according to claim 16, further comprising allowing a local server process to receive messages from both the local message queue and the at least one remote message queue.

19. The method according to claim 11, further comprising allowing a client to determine whether a queue is created on a shared memory or a private memory.

20. The method according to claim 11, further comprising allowing a client to continue perform write operations in the shared memory on a server machine without waiting for a recovery, when an interruption occurs on the server machine.