System and method for managing message queues for multinode applications in a transactional middleware machine environment

Patent metadata

Field	Value
Publication number	US-9558048-B2
Application number	US-201213572501-A
Country	US
Kind code	B2
Filing date	Aug 10, 2012
Priority date	Sep 30, 2011
Publication date	Jan 31, 2017
Grant date	Jan 31, 2017

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.

First claim

What is claimed is:

1. A system for managing message queues in a middleware machine environment, comprising:
a middleware machine environment executing on one or more microprocessors;
a message receiver and a daemon process associated therewith on a server node in the middleware machine environment, wherein the message receiver includes a shared memory that maintains one or more message queues therein;
wherein the daemon process operates to
create, in response to a request from a message sender on a client node, a message queue in the shared memory for communicating with the message sender,
create a security token associated with the message sender and sending the security token to the message sender,
accept, from the message sender, a remote direct memory access (RDMA) operation on the shared memory for writing a message directly in the shared memory, responsive to the message sender receiving the security token, and
receive metadata information of the message via the message queue.

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

3. The system according to claim 1 , wherein the daemon process is further configured to send the security token from the server node to the client node via a secured network.

4. The system according to claim 1 , wherein the daemon process is configured to create and reserve a local message queue for local messaging.

5. The system according to claim 4 , wherein the local message queue is created and reserved outside of the shared memory.

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

7. The system according to claim 1 , wherein the message sender is configured to determine whether a message queue is created on the shared memory or a private memory.

8. The system according to claim 1 , wherein the message sender is configured to continue to perform the RDMA operation in the shared memory without waiting for a recovery from an interruption that has occurred on the server node that hosts the shared memory.

9. The system according to claim 1 , wherein the daemon process is configured to create and reserve a local message queue for local messaging.

10. A method for managing message queues in a middleware machine environment, comprising:
providing a shared memory on a message receiver on a sever node executing on one or more microprocessors, wherein the shared memory maintains one or more message queues therein;
creating, via a daemon process associated with the message receiver, a message queue in the shared memory for communicating with a message sender in response to a request from the message sender; and
creating a security token and sending the security token to the message sender;
accepting, from the message sender, a remote direct memory access (RDMA) operation on the shared memory for writing a message directly in the shared memory, responsive to the message sender receiving the security token; and
receiving metadata information of the message via the message queue.

11. The method according to claim 10 , wherein different processes on the message sender operate to use at least one proxy to communicate with the message receiver.

12. The method according to claim 10 , wherein the daemon process is further configured to send the security token from the server node to the client node via a secured network.

13. The method according to claim 10 , further comprising creating and reserving, via the daemon process, a local message queue for local messaging.

14. The method according to claim 13 , wherein the local message queue is created and reserved outside of the shared memory.

15. The method according to claim 13 , a local server process is configured to receive messages from both the local message queue and the at least one message queue in the shared memory.

16. The method according to claim 10 , the message sender is configured to determine whether a message queue is created on the shared memory or a private memory.

17. The method according to claim 10 , wherein the message sender is configured to continue to perform the RDMA operation in the shared memory without waiting for a recovery from an interruption that has occurred on the server node that hosts the shared memory.

18. A non-transitory computer readable storage medium including instructions stored thereon which, when executed by a computer, cause the computer to perform the steps comprising:
providing a shared memory on a message receiver on a sever node executing on one or more microprocessors, wherein the shared memory maintains one or more message queues therein;
creating, via a daemon process associated with the message receiver, a message queue in the shared memory for communicating with a message sender in response to a request from the message sender; and
creating a security token and sending the security token to the message sender;
accepting, from the message sender, a remote direct memory access (RDMA) operation on the shared memory for writing a message directly in the shared memory, responsive to the message sender receiving the security token; and
receiving metadata information of the message via the message queue.

19. The non-transitory computer readable storage medium according to claim 18 , wherein different processes on the message sender operate to use at least one proxy to communicate with the message receiver.

20. The non-transitory computer readable storage medium according to claim 18 , wherein the daemon process is further configured to send the security token from the server node to the client node via a secured network.

Assignees

• Frank Richard
• Little Todd
• Kaimalettu Arun
• Tominna Leonard
• Oracle Int Corp

Inventors

• Frank Richard
• Little Todd
• Kaimalettu Arun
• Tominna Leonard

Classifications

• G06F9/544 Primary

  Buffers; Shared memory; Pipes · CPC title

• G06F9/546

  Message passing systems or structures, e.g. queues · CPC title

• G06F2209/548

  Queue · CPC title