Event locality using queue services

• US 20070101341A1
• Filed: 10/07/2005
• Published: 05/03/2007
• Est. Priority Date: 10/07/2005
• Status: Active Grant

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: Oracle International Corporation (Oracle Corporation)
• Inventors: Meiyyappan, Krishnan, Venkatesan, Ramkumar, Downing, Alan, Stamos, James
• Granted Patent: US 8,196,150 B2
• Time in Patent Office: Days
• US Class Current: 719/314
• CPC Class Codes: G06F 9/542 Event management; Broadcasting; Multicasting; Notifications
• CPC Class Codes: G06F 9/544 Buffers; Shared memory; Pipes

Abstract

An approach for reducing transport of messages between nodes of a multi-node system is presented wherein a message queue is associated with a queue service, and based on which node the message queue resides, one of the nodes is registered as hosting the associated queue service. In response to a client attempting to connect and requesting a particular queue service, the client is caused to connect to the node on which the queue service resides.

Claims

1. A method for a multi-node system, the method comprising:

associating a message queue with a queue service;

based on which node of said multi-node system said message queue resides,

registering a certain node as hosting said queue service;

receiving from a client a connection request that requests the queue service; and

in response to receiving the connection request that requests the queue service,

causing said client to connect to said certain node.

2. The method of claim 1, further comprising a process executing said multi-node system, said process accessing data identifying said certain node as hosting said queue service, and then causing said client to connect to said certain node based upon said data.

3. The method of claim 1, wherein said queue service residing on a first node is migrated to a second node of said multi-node system in response to the failure of said first node, said second node then registering as hosting said queue service.

4. The method of claim 1, wherein said registration comprises modifying data accessible by each of said nodes, said data identifying the node hosting said queue service.

5. The method of claim 1, wherein said client is a publisher of messages.

6. The method of claim 1, wherein said client is a subscriber of messages

7. The method of claim 1, wherein said multi-node system comprises a database system.

8. The method of claim 1, wherein the publisher and subscriber of messages related to a service are on the same instance.

9. The method of claim 1, wherein said message queue comprises a buffered message queue.

10. The method of claim 1, wherein said multi-node system hosts services in addition to said queue service.

11. The method of claim 1, further comprising providing the client a view containing queue names and the service owning the queue.

12. The method of claim 1, wherein each node is utilizing nonpersistent messaging.

13. The method of claim 1, wherein each node is utilizing persistent messaging.

14. The method of claim 1, wherein each node is utilizing pipes.

16. A computer-readable medium carrying one or more sequences of instructions which, when executed by one or more processors, causes the one or more processors to perform the method recited in claim 2.

17. A computer-readable medium carrying one or more sequences of instructions which, when executed by one or more processors, causes the one or more processors to perform the method recited in claim 3.

18. A computer-readable medium carrying one or more sequences of instructions which, when executed by one or more processors, causes the one or more processors to perform the method recited in claim 4.

19. A computer-readable medium carrying one or more sequences of instructions which, when executed by one or more processors, causes the one or more processors to perform the method recited in claim 5.

20. A computer-readable medium carrying one or more sequences of instructions which, when executed by one or more processors, causes the one or more processors to perform the method recited in claim 6.

21. A computer-readable medium carrying one or more sequences of instructions which, when executed by one or more processors, causes the one or more processors to perform the method recited in claim 7.

22. A computer-readable medium carrying one or more sequences of instructions which, when executed by one or more processors, causes the one or more processors to perform the method recited in claim 8.

23. A computer-readable medium carrying one or more sequences of instructions which, when executed by one or more processors, causes the one or more processors to perform the method recited in claim 9.

24. A computer-readable medium carrying one or more sequences of instructions which, when executed by one or more processors, causes the one or more processors to perform the method recited in claim 10.

25. A computer-readable medium carrying one or more sequences of instructions which, when executed by one or more processors, causes the one or more processors to perform the method recited in claim 11.

26. A computer-readable medium carrying one or more sequences of instructions which, when executed by one or more processors, causes the one or more processors to perform the method recited in claim 12.

27. A computer-readable medium carrying one or more sequences of instructions which, when executed by one or more processors, causes the one or more processors to perform the method recited in claim 13.

28. A computer-readable medium carrying one or more sequences of instructions which, when executed by one or more processors, causes the one or more processors to perform the method recited in claim 14.

15. A computer-readable medium carrying one or more sequences of instructions which, when executed by one or more processors, causes the one or more processors to perform the steps of:

associating a message queue with a queue service;

based on which node of said multi-node system said message queue resides,

registering a certain node as hosting said queue service;

receiving from a client a connection request that requests the queue service; and

in response to receiving the connection request that requests the queue service,

causing said client to connect to said certain node.