Management of connections in a messaging environment

US9419930B2 · US · B2

Patent metadata
FieldValue
Publication numberUS-9419930-B2
Application numberUS-201313929929-A
CountryUS
Kind codeB2
Filing dateJun 28, 2013
Priority dateJun 28, 2013
Publication dateAug 16, 2016
Grant dateAug 16, 2016

How to read this patent

A practical reading order for non-experts. Skip the full description unless you need deep technical detail.

  1. Title

    What the patent document calls the invention.

  2. Abstract

    A short plain-language summary of the technical disclosure.

  3. Assignees and inventors

    Who owns or filed the patent and who is credited as inventor.

  4. Key dates

    Filing, priority, publication, and grant dates set the timeline.

  5. First independent claim

    The legal scope of protection — read this for what is actually claimed.

  6. CPC / IPC classifications

    Technology tags used to group this patent with similar filings.

  7. Citations and related patents

    Prior art links and similar publications in this corpus.

Abstract

Official abstract text for this publication.

A method, system, and/or computer program product manages message connections in a computer infrastructure. A processor connects a client to a messaging component over a connection. Identification information of a destination message queue that the client intends to communicate to the messaging component is provided, and a reference of the destination message queue is received. Based on the received reference, a respective messaging component that has the destination message queue localized is identified.

First claim

Opening claim text (preview).

What is claimed is: 1. A computer system comprising: a hardware processor, a computer readable memory, and a non-transitory computer readable storage medium; first program instructions to connect a client to a first messaging component over a connection, wherein the first messaging component is implemented on a first computer; second program instructions to provide identification information of a destination message queue that the client intends to communicate to, wherein the destination message queue is used in a point to point messaging system, wherein the destination message queue is located on a second messaging component on a second computer, and wherein the second messaging component has been selected by a workload management component in the first messaging component in the first computer to store the destination message queue; third program instructions to receive a reference of the destination message queue, wherein the reference identifies the second messaging component upon which the destination message queue is located; fourth program instructions to identify, based on the reference, the second messaging component that has the destination message queue localized thereon; and fifth program instructions to, in response to determining that the destination message queue is not located in the first messaging component, use the reference to route the connection from the client to the second messaging component that has the destination message queue localized thereon, wherein a session connection between the client and the second messaging component that has the destination message queue localized thereon is transparently routed to the second messaging component by using the connection from the client to the first computer as a proxy connection to the second computer and the second messaging component; and wherein the first, second, third, fourth, and fifth program instructions are stored on the non-transitory computer readable storage medium for execution by the hardware processor via the computer readable memory. 2. The computer system of claim 1 , further comprising: sixth program instructions to compare the reference of the destination message queue and a connection reference of the connection to determine if the destination message queue is localized at a messaging component to which the client is connected; and wherein the sixth program instructions are stored on the non-transitory computer readable storage medium for execution by the hardware processor via the computer readable memory. 3. The computer system of claim 1 , further comprising: distributing, by workload management components on the first computer and the second computer, a communication session workload between the first messaging component and the second messaging component. 4. The computer system of claim 1 , wherein the connection between the client and the first messaging component is via a Java Message Service Application Program Interface (JVS API), wherein the connection represents an open TCP/IP socket between the client and the first messaging component. 5. The computer system of claim 1 , further comprising: sixth program instructions to create at least one session using the connection; seventh program instructions to create a message producer and a message consumer for a communication session; eighth program instructions to specify the destination message queue for the communication session; and ninth program instructions to provide the identification information of the destination message queue for the communication session to the messaging component to which the client is connected; and wherein the fifth, sixth, seventh, and eighth program instructions are stored on the non-transitory computer readable storage medium for execution by the hardware processor via the computer readable memory. 6. The computer system of claim 1 , wherein the reference is determined from a routing table comprising information about the first and second messaging components. 7. The system of claim 5 , wherein a plurality of messaging components of the communication session are interconnected via a bus. 8. A computer program product for identifying a messaging component having a destination message queue localized in a messaging environment, the computer program product comprising a non-transitory computer readable storage medium having program code embodied therewith, the program code readable and executable by a processor to perform a method comprising: connecting a client to a first messaging component over a connection, wherein the first messaging component is implemented on a first computer; providing identification information of a destination message queue that the client intends to communicate to, wherein the destination message queue is used in a point to point messaging system, wherein the destination message queue is located on a second messaging component on a second computer, and wherein the second messaging component has been selected by a workload management component in the first messaging component in the first computer to store the destination message queue; receiving a reference of the destination message queue, wherein the reference identifies the second messaging component upon which the destination message queue is located; identifying, based on the reference, the second messaging component that has the destination message queue localized thereon; and in response to determining that the destination message queue is not located in the first messaging component, using the reference to route the connection from the client to the second messaging component that has the destination message queue localized thereon, wherein a session connection between the client and the second messaging component that has the destination message queue localized thereon is transparently routed to the second messaging component by using the connection from the client to the first computer as a proxy connection to the second computer and the second messaging component. 9. The computer program product of claim 8 , wherein said identifying, based on the reference, of the second messaging component that has the destination message queue localized comprises comparing the reference of the destination message queue and a connection reference of the connection to determine if the destination message queue is localized at a messaging component to which the client is connected. 10. The computer program product of claim 8 , wherein the method further comprises: distributing, by workload management components on the first computer and the second computer, a workload between the first messaging component and the second messaging component. 11. The computer program product of claim 10 , wherein the connection between the client and the first messaging component is via a Java Message Service Application Program Interface (JVS API), wherein the connection represents an open TCP/IP socket between the client and the first messaging component. 12. The computer program product of claim 8 , wherein the method further comprises: creating at least one session using the connection; creating a message producer and a message consumer for a communication session; specifying the destination message queue for the communication session; and providing the identification information of the destination message queue for the communication session to the messaging component to which the client is connected. 13. The computer program product of claim 8 , wherein the reference is determined from a routing table comprising information about the first and second messaging components.

Assignees

Inventors

Classifications

  • H04L51/22Primary

    Electricity · mapped topic

  • Electricity · mapped topic

  • H04L51/42Primary

    Mailbox-related aspects, e.g. synchronisation of mailboxes · CPC title

  • using selective forwarding · CPC title

Patent family

Related publications grouped by family.

External sources

Frequently asked questions

Answers are generated from the same data shown on this page.

What does patent US9419930B2 cover?
A method, system, and/or computer program product manages message connections in a computer infrastructure. A processor connects a client to a messaging component over a connection. Identification information of a destination message queue that the client intends to communicate to the messaging component is provided, and a reference of the destination message queue is received. Based on the rec…
Who is the assignee on this patent?
IBM
What technology area does this patent fall under?
Primary CPC classification H04L51/22. Mapped technology areas include Electricity.
When was this patent published?
Publication date Tue Aug 16 2016 00:00:00 GMT+0000 (Coordinated Universal Time) (B2). Legal status and post-grant events are not shown on this page.
What related patents are in patentsdb?
We list 2 related publications on this page (citations in our corpus or others sharing the same primary CPC).