Method and apparatus for routing messages to processes in a computer system

• US 5,367,681 A
• Filed: 11/02/1993
• Issued: 11/22/1994
• Est. Priority Date: 12/14/1990
• Status: Expired due to Term

• Current Assignee: Sun Microsystems Incorporated (Oracle Corporation)
• Original Assignee: Sun Microsystems Incorporated (Oracle Corporation)
• Inventors: Hare, Dwight F., Shaio, Sami, Pearl, Amy, Nguyen, Tin A., McAllister, Richard F., Foss, Carolyn L.
• Primary Examiner(s): Kriess, Kevin A.
• Assistant Examiner(s): Backenstose, J. H. B. Hall
• Application Number:
  US08/147,019
• Time in Patent Office: 385 Days
• Field of Search: 395/650, 395/700, 364/DIG. 1, 364/DIG. 2
• US Class Current: 719/314
• CPC Class Codes: G06F 9/542 Event management; Broadcasting; Multicasting; Notifications
• CPC Class Codes: G06F 9/546 Message passing systems or structures, e.g. queues

Abstract

A method and apparatus for interprocess message switching between a sender process and a plurality of receiver processes is disclosed. Messages supported comprise request and notice messages. Receiver processes supported comprise handler processes and observer processes. Request messages may be observed as well as handled, and notice messages may be handled as well as observed. Handler and observer processes may be non-executing as well as executing. Sender processes do not need to specify the identity of the receiver processes. The sender process and the receiver processes may be executed on the same computer or on two or more computers in a network.

Claims

1. A method for interprocess message routing in a computer system, said computer system comprising a sender process and a plurality of receiver processes, said plurality of receiver processes comprising handler processes and observer processes, said method comprising the steps of:

registering each of said receiver processes with a routing apparatus in said computer system that performs interprocess message routing such that said receiver processes become registered receiver processes, said step of registering comprising

registering a signaling way for each receiver process, said signaling way describing how said receiver process is to be signaled,

registering at least one message pattern for each of said receiver processes, said message patterns describing at least one message which said registering receiver process is to receive;

sending at least one message from said sender process to said routing apparatus, said message sent by said sender process comprises at least one message attribute, one of said message attributes comprising a message class of "Request" or a message class of "Notice", message having a message class of "Request" requiring a reply, a message having a message class of "Notice" not requiring a reply;

selecting a set of said registered receiver processes to receive said message from said routing apparatus by matching said message against said message patterns registered by said receiver processes, said step of selecting a set of said registered receiver processes comprises said routing apparatus selecting at most one handler process to handle said received message and any number of observer processes;

queuing, in said routing apparatus, copies of said message with said set of receiver processes;

signaling said set of registered receiver processes from said routing apparatus regarding the availability of said queued copies of said message, said step of signaling performed by said routing apparatus using said signaling way given by said selected registered receiver process; and

sending said queued copies of said message from said routing apparatus to each of said set of registered receiver processes upon request of each of said set of registered receiver processes.

2. The method for interprocess message routing in a computer system as set forth in claim 1, wherein said step of registering at least one message pattern for each of said receiver processes comprises registering a plurality of message attributes describing messages which said registering receiver process are to receive.

3. The method for interprocess message routing in a computer system as set forth in claim 1, wherein said step of registering at least one message pattern for each of said receiver processes further comprises registering a program type identifier for each of said receiver processes, said program type identifiers identifying programs being executed by said registering receiver processes, said routing apparatus generating and registering said message patterns for each of said registering receiver processes using message signatures contained within a program type definition comprising matching program type identifiers, said program type definitions being stored in a file coupled to said routing apparatus.

4. The method for interprocess message routing in a computer system as set forth in claim 3, wherein each of said stored program type definitions further comprises a set of program start up parameters and at least one message signature, each of said message signatures comprising one of said message pattern and a message disposition attribute.

5. The method for interprocess message routing in a computer system as set forth in claim 4, wherein said step of registering said receiver processes further comprises deregistering a receiver process when said receiver process requests a deregistration.

6. The method for interprocess message routing in a computer system as claimed in claim 2, wherein said message attributes in said message comprises a message identifier for said received message, said message identifier comprising a sender computer identifier, a sender process identifier, and a sender process specific message identifier.

7. The method for interprocess message routing in a computer system as claimed in claim 1, wherein said message attributes in said message further comprise a message state attribute, each of said message states being one of a plurality of message states comprising a state of "Created", a state of "Sent", a state of "Handled", a state of "Started", a state of "Failed" and a state of "Queued".

8. The method for interprocess message routing in a computer system as claimed in claim 1, wherein said message attributes in said message further comprise a program type identifier for said sender process.

9. The method for interprocess message routing in a computer system as claimed in claim 1, wherein said message attributes in said message further comprise a program type identifier for a handler process.

10. The method for interprocess message routing in a computer system as claimed in claim 1, wherein said message attributes in said message further comprise a message disposition attribute, each of said message dispositions being one of a plurality of message dispositions comprising a disposition of "Queue", a disposition of "Start", and a disposition of "Discard", said disposition of "Discard" being the defaulted disposition if no disposition is specified.

11. The method for interprocess message routing in a computer system as set forth in claim 1, wherein said selecting of at most one handler process and any number of observer processes comprises selecting non-executing as well as executing handler and observer processes.

12. The method for interprocess message routing in a computer system as set forth in claim 1, wherein said step of selecting said registered receiver processes further comprises the steps of,

matching said message attributes in said message sent by said sender process against said message attributes in said message patterns contained in message signatures, said message signatures being contained in program type definitions, said program type definitions being stored in files coupled to said routing apparatus;

and

matching program type identifiers contained in said stored program type definitions having said matching message attributes, by said routing apparatus, against program type identifiers of programs being executed by said registered receiver processes.

13. The method for interprocess message routing in a computer system as set forth in claim 12, wherein said step of selecting said registered receiver processes further comprises the step of choosing one handler process by said routing apparatus, said one handler process being chosen by ranking said matching message attributes of said matching message patterns and said matching message signatures, said one handler process further being chosen arbitrarily, if said rankings of said matching message attributes are tied.

14. The method for interprocess message routing in a computer system as set forth in claim 1, wherein said step of queuing copies of said message with selected receiver processes comprises queuing copies of said message into at least one undelivered messages queue, by said routing apparatus, for subsequent retrieval by said selected receiver processes.

15. The method for interprocess message routing in a computer system as claimed in claim 14, wherein said step of queuing copies of said message with selected receiver processes further comprises queuing copies of said message with selected receiver processes into at least one program pending messages queue by said routing apparatus, for subsequent retrieval by said selected receiver processes,

said message with selected receiver processes having copies queued into said program pending messages queues comprise said message comprising message attributes matching against message signatures, said matching message signatures further comprising message disposition attributes equaling "Queue", and being contained in program type definitions identifying programs not being executed by said registered receiver processes.

16. The method for interprocess message routing in a computer system as claimed in claim 1, wherein said step of sending said queued messages comprises dequeuing said queued messages from messages queues and sending said dequeued messages by said routing apparatus to said selected receiver processes using a system message sending services.

17. The method for interprocess message routing in a computer system as claimed in claim 1, wherein said method further comprises the step of discarding said message with message class attributes equaling "Notice" and no selected receiver processes, said received "Notice" messages with no selected receiver processes comprise said received "Notice" messages having message attributes non-matching against registered message patterns and non-matching against message signatures contained in program type definitions, said program type definitions being stored in files couples to said routing apparatus.

18. The method for interprocess message routing in a computer system as claimed in claim 17, wherein said received "Notice" messages with no selected receiver processes further comprise said received "Notice" messages having said message attributes matching against said message signatures, said matching message signatures further comprising message dispositions equaling "Discard", and being contained in said program types identifying programs not being executed by said registered receiver processes.

19. The method for interprocess message routing in a computer system as claimed in claim 1, wherein said method further comprises the steps of

registering said sender process with said routing apparatus;

and

replying from said handler process to said sender process when said message has a message class attributes equaling "Request".

20. The method for interprocess message routing in a computer system as claimed in claim 19, wherein said step of registering said sender process comprises registering a signaling way for said sender process, said signaling way describing how said registering sender process is to be signaled regarding the availability of a queued reply message.

21. The method for interprocess message routing in a computer system as set forth in claim 19, wherein said step of replying to said sender process comprises replying to a "Request" message with no selected handler process, said "Request" message with no selected handler process comprise said received "Request" message having message attributes non-matching against registered message patterns and non-matching against message signatures contained in program type definitions, said program type definitions being stored in files coupled to said routing apparatus.

22. The method for interprocess message routing in a computer system as claimed in claim 21, wherein said "Request" message with no selected handler process further comprise said "Request" message having said message attributes matching against said message signatures, said matching message signatures further comprising message dispositions equaling "Discard", and being contained in said program types identifying programs not being executed by said registered receiver processes.

23. The method for interprocess message routing in a computer system as claimed in claim 19, wherein said step of replying from said handler process to said sender process comprises the steps of,

generating a reply message for each said "Request" message;

selecting said registered receiver processes to receive said reply messages;

queuing said reply messages to at least one undelivered messages queue, for subsequent retrieval by said sender process and said selected receiver processes;

signaling said sender process and said selected receiver processes regarding the availability of said queued reply messages; and

sending said queued reply messages to said signaled receiver processes upon request.

24. The method for interprocess message routing in a computer system as set forth in claim 23, wherein said step of generating reply messages comprises updating message attributes of it "Request" messages with no selected handler process by said routing apparatus, said message attributes being updated comprising message state attributes being updated to "Failed".

25. The method for interprocess message routing in a computer system as set forth in claim 24, wherein said step of generating reply messages further comprises updating message attributes of said "Request" messages with selected handler process by said routing apparatus, said message attributes being updated according to results received from said handler processes, said message attributes being updated comprising message state attributes being updated to one of a plurality of message states comprising a state of "Handled" and a state of "Failed".

26. The method for interprocess message routing in a computer system as set forth in claim 25, wherein said step of generating reply messages further comprises the steps of,

queuing another copy of each of said "Request" messages with selected handler processes, pending receipt of said results from said handler processes;

and

dequeuing said results pending "Request" messages upon receipt of said results from said handler processes for said step of updating.

27. The method for interprocess message routing in a computer system as set forth in claim 26, wherein said step of queuing copies of said "Request" messages comprises queuing said copies in at least one result pending messages queue by said routing apparatus.

28. An apparatus for message routing between a sender process and a plurality of receiver processes, said plurality of receiver processes comprising handler processes and observer processes, said apparatus comprising:

a first registering means for registering said receiver processes with said apparatus, said first registering means comprising a first interface for receiving registrations, said first registering means registering a signaling way describing how said receiver process is to be signaled and at least one message pattern for each of said receiver processes, said message pattern describing at least one message which said registering receiver process is to receive;

receiving means, said receiving means comprising a second interface for receiving at least one message sent by said sender process, said message comprising at least one message attribute, one of said message attributes in some of said received messages comprising a message class attribute, said message class attribute comprising a message class of "Request" or a message class of "Notice", a message having a message class "Request" requiring a reply, a message having a message class "Notice" not requiring a reply;

first selecting means for selecting a set of said registered receiver processes to receive said message sent by said sender process, said first selecting means comprising a first matching means, said first matching means selecting a set of said registered receiver processes to receive said message sent by said sender process by matching said message against said first set of message attributes in said message patterns registered by said receiver processes, said set of said registered receiver processes comprising at most one handler process to handle said message and any number of observer processes;

first queuing means coupled to said first selecting means, for queuing said message with said set of receiver processes;

first signaling means coupled to said first queuing means and said first registering means, for signaling said set of receiver processes regarding availability of said queued messages, said first signaling means using said signaling way given by said set of registered receiver process; and

first delivering means for delivering said queued messages to each of said set of said selected registered receiver processes which request delivery of said message, said first delivering means comprising a third interface for receiving said delivery request.

29. The apparatus for message routing between a sender process and a plurality of processes as set forth in claim 28, wherein said first registering means for registering said receiver processes further comprises a first processing means coupled to said first interface for processing one of said received registrations comprising a program type identifier, said program type identifier identifying programs being executed by said registering receiver processes, said first processing means generating and registering said message patterns for said registering receiver processes, using message signatures contained within program type definitions comprising matching program type identifiers, and storing said generated message patterns into said tables, said program type definitions being stored in files accessible to said first processing means.

30. The apparatus for message routing between a sender process and a plurality of processes as set forth in claim 29, wherein each of said stored program type definitions further comprises a set of start up parameters and at least one message signature, each of said message signatures comprising a message pattern and a message disposition attribute.

31. The apparatus for interprocess message routing between a sender process and a plurality of receiver processes as set forth in claim 28, wherein said message attributes in each of said received messages comprise an identifier for said received message, each of said message identifier comprising a sender computer identifier, a sender process identifier and a sender process specific message identifier.

32. The apparatus for interprocess message routing between a sender process and a plurality of receiver processes as set forth in claim 28, wherein said message attributes in some of said received messages further comprise a message state attribute, each of said message states being one of a plurality of message states comprising a state of "Created", a state of "Sent", a state of "Handled", a state of "Started", a state of "Failed" and a state of "Queued".

33. The apparatus for interprocess message routing between a sender process and a plurality of receiver processes as set forth in claim 28, wherein said message attributes in some of said received messages further comprise a message operation attribute and a message argument attribute.

34. The apparatus for interprocess message routing between a sender process and a plurality of receiver processes as set forth in claim 28, wherein said message attributes in some of said received messages further comprise a program type identifier for said sender process.

35. The apparatus for interprocess message routing between a sender process and a plurality of receiver processes as set forth in claim 28, wherein said message attributes in some of said received messages further comprise a program type identifier for said handler process.

36. The apparatus for interprocess message routing between a sender process and a plurality of receiver processes as set forth in claim 28, wherein said message attributes in some of said received messages further comprise a message disposition attribute, each of said message dispositions being one of a plurality of message dispositions comprising a disposition of "Queue", a disposition of "Start", and a disposition of "Discard", said disposition of "Discard" being the defaulted disposition if no disposition is specified.

37. The apparatus for interprocess message routing between a sender process and a plurality of receiver processes as set forth in claim 28, wherein said first selecting means for selecting said registered receiver processes selects at most one handler process and any number of observer processes.

38. The apparatus for interprocess message routing between a sender process and a plurality of receiver processes as set forth in claim 37, wherein said selecting of at most one handler process and any number of observer processes comprises selecting non-executing as well as executing handler and observer processes.

39. The apparatus for interprocess message routing between a sender process and a plurality of receiver processes as set forth in claim 28, wherein said first selecting means for selecting said registered receiver processes further comprises,

second matching means coupled to said first matching means for matching said message attributes in said received messages, against said message attributes in said message patterns contained in message signatures, said message signatures being contained in program type definitions, said program type definitions being stored in files accessible to said second matching means;

and

third matching means coupled to said second matching means for matching program type identifiers contained in said stored program type definitions having said matching message attributes, against program type identifiers of programs being executed by said registered receiver processes, said program type identifiers of programs being stored in said tables and accessible to said third matching means.

40. The apparatus for interprocess message routing between a sender process and a plurality of receiver processes as set forth in claim 39, wherein said first selecting means for selecting said registered receiver processes further comprises a choosing means coupled to said third matching means for choosing one handler process, said one handler process being chosen by ranking said matching message attributes of said matching message patterns and said matching message signatures, said one handler process further being chosen arbitrarily, if said rankings of said matching message attributes are tied.

41. The apparatus for interprocess message routing between a sender process and a plurality of receiver processes as set forth in claim 40, wherein said first selecting means for selecting said registered receiver processes further comprises a starting means coupled to said choosing means for starting said selected receiver processes, said receiver processes being started comprise said receiver processes executing said programs identified by said stored program type definitions with said matching message signatures, said programs not being executed by other registered receiver processes, and said matching message signatures comprising message disposition attributes of "Start".

42. The apparatus for interprocess message routing between a sender process and a plurality of receiver processes as set forth in claim 28, wherein said first queuing means for queuing copies of said received messages with selected receiver processes queues copies of said received messages into at least one process pending messages queue, for subsequent retrieval by said selected receiver processes,

said received messages with selected receiver processes having copies queued into said program pending messages queues comprise said received messages comprising message attributes matching against message signatures, said matching message signatures further comprising message disposition attributes equaling "Queue", and being contained in program type definitions identifying programs not being executed by said registered receiver processes.

43. The apparatus for interprocess message routing between a sender process and a plurality of receiver processes as set forth in claim 28, wherein said first delivering means for delivering said queued messages for said selected receiver processes dequeues said queued messages from messages queues and sends said dequeued messages to said selected receiver processes, using system message sending services.

44. The apparatus for interprocess message routing between a sender process and a plurality of receiver processes as set forth in claim 28, wherein said first queuing means further discards said received messages with message class attributes equaling "Notice" and no selected receiver processes, said received "Notice" messages with no selected receiver processes comprise said received "Notice" messages having message attributes non-matching against registered message patterns and non-matching against message signatures contained in program type definitions.

45. The apparatus for interprocess message routing between a sender process and a plurality of receiver processes as set forth in claim 44, wherein said received "Notice" messages with no selected receiver processes further comprise said received "Notice" messages having said message attributes matching against said message signatures, said matching message signatures further comprising message dispositions equaling "Discard", and being contained in said program types identifying programs not being executed by said registered receiver processes.

46. The apparatus for interprocess message routing between a sender process and a plurality of receiver processes as set forth in claim 28, wherein said apparatus further comprises

second registering means for registering said sender process, said second registering means registering a signaling way describing how said sender process is to be signaled, said second registering means comprising a fourth interface for receiving registrations from said sender process;

and

replying means coupled to said first selecting means for replying to said received messages with a message class attributes equaling "Request".

47. The apparatus for interprocess message routing between a sender process and a plurality of receiver processes as set forth in claim 46, wherein said replying means for replying to said received "Request" messages replies to said "Request" messages with no selected handler process.

48. The apparatus for interprocess message routing between a sender process and a plurality of receiver processes as set forth in claim 47, wherein said received "Request" messages with no selected handler process comprise said received "Request" messages having message attributes non-matching against registered message patterns and non-matching against message signatures contained in program type definitions.

49. The apparatus for interprocess message routing between a sender process and a plurality of receiver processes as set forth in claim 48, wherein said received "Request" messages with no selected handler process further comprise said received "Request" messages having said message attributes matching against said message signatures, said matching message signatures further comprising message dispositions equaling "Discard", and being contained in said program types identifying programs not being executed by said registered receiver processes.

50. The apparatus for interprocess message routing between a sender process and a plurality of receiver processes as set forth in claim 47, wherein said replying means for replying to said received "Request" messages further replies to said "Request" messages with selected handler process.

51. The apparatus for interprocess message routing between a sender process and a plurality of receiver processes as set forth in claim 46, wherein said replying means for replying to said received "Request" messages comprises,

generating means coupled to said first selecting means for generating reply messages to said received "Request" messages;

second selecting means coupled to said generating means for selecting said registered received processes to receive said reply messages;

second queuing means coupled to said second selecting means for queuing said reply messages to at least one undelivered messages queue, for subsequent retrieval by said sender process and said selected receiver processes;

second signaling means coupled to said second queuing means for signaling said sender process and said selected receiver processes regarding the availability of said queued reply messages; and

second delivering means for delivering said queued reply messages upon request of said signaled processes, to said requesting receiver processes, said second delivering means comprising an fifth interface for receiving said delivery requests.

52. The apparatus for interprocess message routing between a sender process and a plurality of receiver processes as set forth in claim 51, wherein said generating means for generating reply messages comprises an updating means coupled to said first selecting means for updating message attributes of said received "Request" messages with no selected handler process, said message attributes being updated comprising message state attributes being updated to "Failed".

53. The apparatus for interprocess message routing between a sender process and a plurality of receiver processes as set forth in claim 52, wherein said updating means further dequeues said received "Request" messages with selected handler process from result pending messages queues, and updates message attributes of said received "Request" messages with selected handler process, said updating means comprising a sixth interface for receiving results from said handler processes, and having access to said result pending messages queues, said message attributes being updated according to said results, said message attributes being updated comprising message state attributes being updated to one of a plurality of message states comprising a state of "Handled" and a state of "Failed".

54. The apparatus for interprocess message routing between a sender process and a plurality of receiver processes as set forth in claim 53, wherein said generating means for generating reply messages further comprises a third queuing means coupled to said first selecting means for queuing another copy of each of said received "Request" messages with selected handler processes, pending receipt of said results from said handler processes.

55. The apparatus for interprocess message routing between a sender process and a plurality of receiver processes as set forth in claim 54, wherein said third queuing means for queuing copies of said received "Request" messages with selected handler processes queues said copies in at least one result pending messages queue, said third queuing means comprising said first queuing means.