Resilient messaging infrastructure

• US 10,051,080 B2
• Filed: 11/18/2016
• Issued: 08/14/2018
• Est. Priority Date: 08/07/2012
• Status: Active Grant

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Plant, Laurence J.
• Primary Examiner(s): MADAMBA, GLENFORD J
• Application Number:
  US15/355,885
• Publication Number:
  US 20170070592A1
• Time in Patent Office: 634 Days
• Field of Search: 709203
• CPC Class Codes: H04L 51/23 Reliability checks, e.g. acknowledgments or fault reporting
• CPC Class Codes: H04L 67/00 Network arrangements or protocols for supporting network services or applications user-to-user messaging H04L51/00; network arrangements, protocols or services for supporting real-time applications in data packet communications networks H04L65/00
• CPC Class Codes: H04L 67/01 Protocols
• CPC Class Codes: H04L 67/1091 Interfacing with client-server systems or between P2P systems
• CPC Class Codes: H04L 67/59 Providing operational support to end devices by off-loading in the network or by emulation, e.g. when they are unavailable

Abstract

A first message resilience client device receives a message and a request to deliver the message, on behalf of a remote client/server-based client application that originated the message, to a client/server-based server application that provides outgoing client/server messaging services to the remote client/server-based client application that originated the message. In response to determining that the connection to the server device that executes the client/server-based server application is not currently possible with any available connection, the message is stored locally for one of later delivery to the client/server-based server application and propagation of the message to another message resilience client device on behalf of the remote client/server-based client application.

Claims

1. A method, comprising:

receiving, at a first message resilience client device from a second message resilience client device, a message and a request to deliver the message on behalf of a remote client/server-based client application that originated the message to a client/server-based server application that is executed by a server device and that provides outgoing client/server messaging services to the remote client/server-based client application that originated the message;

storing, in response to determining that delivery of the message as requested on behalf of the remote client/server-based client application to the server device that executes the client/server-based server application is not currently possible via any available connection, the message locally for one of later delivery to the client/server-based server application and propagation of the message with the request to deliver the message to at least one other message resilience client device on behalf of the remote client/server-based client application;

detecting that a local client/server-based client application has originated a local message to send to a locally-targeted client/server-based server application that is executed by a locally-targeted server device and that provides outgoing client/server messaging services to the local client/server-based client application that originated the local message;

determining that a connection to the locally-targeted server device that executes the locally-targeted client/server-based server application is not currently available;

determining that a connection to the at least one other message resilience client device is available;

sending, to the at least one other message resilience client device, the local message and a request to deliver the local message on behalf of the local client/server-based client application to the locally-targeted client/server-based server application that provides the outgoing client/server messaging services to the local client/server-based client application that originated the local message;

determining whether message presence information that identifies the local message exists within a message presence database and indicates whether the local message has already been delivered to the locally-targeted client/server-based server application;

in response to determining that the local message has already been delivered;

notifying the local client/server-based client application that the local message has been successfully delivered; and

one of;

deleting the message presence information that identifies the local message from the message presence database; and

updating the message presence information to indicate a time duration for storage of the message presence information by the message presence database; and

in response to determining that the local message has not already been delivered;

sending, in response to determining that a connection to the locally-targeted server device that executes the locally-targeted client/server-based server application is currently available, the local message to the locally-targeted client/server-based server application that provides the outgoing client/server messaging services to the local client/server-based client application; and

creating the message presence information that identifies the local message within the message presence database, that indicates that the local message has been delivered to the locally-targeted client/server-based server application, and that indicates the time duration for storage of the message presence information by the message presence database.

2. The method of claim 1, further comprising, in response to determining that the delivery of the message as requested on behalf of the remote client/server-based client application to the server device that executes the client/server-based server application is currently possible via at least one available connection:

determining whether message presence information that identifies the message exists within the message presence database and indicates whether the message has already been delivered to the client/server-based server application that provides the outgoing client/server messaging services to the remote client/server-based client application that originated the message; and

in response to determining that the message presence information that identifies the message exists within the message presence database and indicates that the message has not already been delivered;

sending the message to the client/server-based server application on behalf of the remote client/server-based client application; and

updating the message presence information to indicate that the first message resilience client device delivered the message to the client/server-based server application on behalf of the remote client/server-based client application.

3. The method of claim 1, further comprising:

determining whether message presence information that identifies the message exists within the message presence database;

in response to determining that the message presence information that identifies the message does not exist within the message presence database;

creating message presence information within the message presence database that identifies the message and message propagation information within the created message presence information that indicates to other message resilience client devices that the first message resilience client device is operating as a message resilience proxy client device for the second message resilience client device to attempt to deliver the message to the client/server-based server application on behalf of the remote client/server-based client application; and

in response to determining that the message presence information that identifies the message exists within the message presence database;

creating message propagation information within the message presence information that indicates to the other message resilience client devices that the first message resilience client device is operating as the message resilience proxy client device for the second message resilience client device to attempt to deliver the message to the client/server-based server application on behalf of the remote client/server-based client application.

4. The method of claim 1, further comprising:

determining whether an alternative connection to any other message resilience client device is available; and

propagating, to at least one other message resilience client device to which the alternative connection is determined to be available, the message and the request to deliver the message to the client/server-based server application on behalf of the remote client/server-based client application.

5. The method of claim 4, further comprising:

determining whether message presence information that identifies the message exists within the message presence database;

in response to determining that the message presence information that identifies the message does not exist within the message presence database;

creating message presence information within the message presence database that identifies the message and message propagation information within the created message presence information that identifies each other message resilience client device to which the message and the request to deliver the message is propagated; and

in response to determining that the message presence information that identifies the message exists within the message presence database;

creating message propagation information within the message presence information that identifies each other message resilience client device to which the message and the request to deliver the message is propagated.

6. A system, comprising:

a memory; and

a processor programmed to;

receive, at a first message resilience client device from a second message resilience client device, a message and a request to deliver the message on behalf of a remote client/server-based client application that originated the message to a client/server-based server application that is executed by a server device and that provides outgoing client/server messaging services to the remote client/server-based client application that originated the message;

store, in response to determining that delivery of the message as requested on behalf of the remote client/server-based client application to the server device that executes the client/server-based server application is not currently possible via any available connection, the message locally in the memory for one of later delivery to the client/server-based server application and propagation of the message with the request to deliver the message to at least one other message resilience client device on behalf of the remote client/server-based client application;

detect that a local client/server-based client application has originated a local message to send to a locally-targeted client/server-based server application that is executed by a locally-targeted server device and that provides outgoing client/server messaging services to the local client/server-based client application that originated the local message;

determine that a connection to the locally-targeted server device that executes the locally-targeted client/server-based server application is not currently available;

determine that a connection to the at least one other message resilience client device is available;

send, to the at least one other message resilience client device, the local message and a request to deliver the local message on behalf of the local client/server-based client application to the locally-targeted client/server-based server application that provides the outgoing client/server messaging services to the local client/server-based client application that originated the local message;

determine whether message presence information that identifies the local message exists within a message presence database and indicates whether the local message has already been delivered to the locally-targeted client/server-based server application;

in response to determining that the local message has already been delivered;

notify the local client/server-based client application that the local message has been successfully delivered; and

one of;

delete the message presence information that identifies the local message from the message presence database; and

update the message presence information to indicate a time duration for storage of the message presence information by the message presence database; and

in response to determining that the local message has not already been delivered;

send, in response to determining that a connection to the locally-targeted server device that executes the locally-targeted client/server-based server application is currently available, the local message to the locally-targeted client/server-based server application that provides the outgoing client/server messaging services to the local client/server-based client application; and

create the message presence information that identifies the local message within the message presence database, that indicates that the local message has been delivered to the locally-targeted client/server-based server application, and that indicates the time duration for storage of the message presence information by the message presence database.

7. The system of claim 6, where the processor is further programmed to, in response to determining that the delivery of the message as requested on behalf of the remote client/server-based client application to the server device that executes the client/server-based server application is currently possible via at least one available connection:

determine whether message presence information that identifies the message exists within the message presence database and indicates whether the message has already been delivered to the client/server-based server application that provides the outgoing client/server messaging services to the remote client/server-based client application that originated the message; and

in response to determining that the message presence information that identifies the message exists within the message presence database and indicates that the message has not already been delivered;

send the message to the client/server-based server application on behalf of the remote client/server-based client application; and

update the message presence information to indicate that the first message resilience client device delivered the message to the client/server-based server application on behalf of the remote client/server-based client application.

8. The system of claim 6, where the processor is further programmed to:

determine whether message presence information that identifies the message exists within the message presence database;

in response to determining that the message presence information that identifies the message does not exist within the message presence database;

create message presence information within the message presence database that identifies the message and message propagation information within the created message presence information that indicates to other message resilience client devices that the first message resilience client device is operating as a message resilience proxy client device for the second message resilience client device to attempt to deliver the message to the client/server-based server application on behalf of the remote client/server-based client application; and

in response to determining that the message presence information that identifies the message exists within the message presence database;

create message propagation information within the message presence information that indicates to the other message resilience client devices that the first message resilience client device is operating as the message resilience proxy client device for the second message resilience client device to attempt to deliver the message to the client/server-based server application on behalf of the remote client/server-based client application.

9. The system of claim 6, where the processor is further programmed to:

determine whether an alternative connection to any other message resilience client device is available; and

propagate, to at least one other message resilience client device to which the alternative connection is determined to be available, the message and the request to deliver the message to the client/server-based server application on behalf of the remote client/server-based client application.

10. The system of claim 9, where the processor is further programmed to:

determine whether message presence information that identifies the message exists within the message presence database;

in response to determining that the message presence information that identifies the message does not exist within the message presence database;

create message presence information within the message presence database that identifies the message and message propagation information within the created message presence information that identifies each other message resilience client device to which the message and the request to deliver the message is propagated; and

in response to determining that the message presence information that identifies the message exists within the message presence database;

create message propagation information within the message presence information that identifies each other message resilience client device to which the message and the request to deliver the message is propagated.

11. A computer program product, comprising:

a non-transitory computer readable storage medium having computer readable program code embodied therewith, where the computer readable program code when executed on a computer causes the computer to;

receive, at a first message resilience client device from a second message resilience client device, a message and a request to deliver the message on behalf of a remote client/server-based client application that originated the message to a client/server-based server application that is executed by a server device and that provides outgoing client/server messaging services to the remote client/server-based client application that originated the message;

store, in response to determining that delivery of the message as requested on behalf of the remote client/server-based client application to the server device that executes the client/server-based server application is not currently possible via any available connection, the message locally for one of later delivery to the client/server-based server application and propagation of the message with the request to deliver the message to at least one other message resilience client device on behalf of the remote client/server-based client application;

detect that a local client/server-based client application has originated a local message to send to a locally-targeted client/server-based server application that is executed by a locally-targeted server device and that provides outgoing client/server messaging services to the local client/server-based client application that originated the local message;

determine that a connection to the locally-targeted server device that executes the locally-targeted client/server-based server application is not currently available;

determine that a connection to the at least one other message resilience client device is available;

send, to the at least one other message resilience client device, the local message and a request to deliver the local message on behalf of the local client/server-based client application to the locally-targeted client/server-based server application that provides the outgoing client/server messaging services to the local client/server-based client application that originated the local message;

determine whether message presence information that identifies the local message exists within a message presence database and indicates whether the local message has already been delivered to the locally-targeted client/server-based server application;

in response to determining that the local message has already been delivered;

notify the local client/server-based client application that the local message has been successfully delivered; and

one of;

delete the message presence information that identifies the local message from the message presence database; and

update the message presence information to indicate a time duration for storage of the message presence information by the message presence database; and

in response to determining that the local message has not already been delivered;

send, in response to determining that a connection to the locally-targeted server device that executes the locally-targeted client/server-based server application is currently available, the local message to the locally-targeted client/server-based server application that provides the outgoing client/server messaging services to the local client/server-based client application; and

create the message presence information that identifies the local message within the message presence database, that indicates that the local message has been delivered to the locally-targeted client/server-based server application, and that indicates the time duration for storage of the message presence information by the message presence database.

12. The computer program product of claim 11, where the computer readable program code when executed on the computer further causes the computer to, in response to determining that the delivery of the message as requested on behalf of the remote client/server-based client application to the server device that executes the client/server-based server application is currently possible via at least one available connection:

determine whether message presence information that identifies the message exists within the message presence database and indicates whether the message has already been delivered to the client/server-based server application that provides the outgoing client/server messaging services to the remote client/server-based client application that originated the message; and

in response to determining that the message presence information that identifies the message exists within the message presence database and indicates that the message has not already been delivered;

send the message to the client/server-based server application on behalf of the remote client/server-based client application; and

update the message presence information to indicate that the first message resilience client device delivered the message to the client/server-based server application on behalf of the remote client/server-based client application.

13. The computer program product of claim 11, where the computer readable program code when executed on the computer further causes the computer to:

determine whether message presence information that identifies the message exists within the message presence database;

in response to determining that the message presence information that identifies the message does not exist within the message presence database;

create message presence information within the message presence database that identifies the message and message propagation information within the created message presence information that indicates to other message resilience client devices that the first message resilience client device is operating as a message resilience proxy client device for the second message resilience client device to attempt to deliver the message to the client/server-based server application on behalf of the remote client/server-based client application; and

in response to determining that the message presence information that identifies the message exists within the message presence database;

create message propagation information within the message presence information that indicates to the other message resilience client devices that the first message resilience client device is operating as the message resilience proxy client device for the second message resilience client device to attempt to deliver the message to the client/server-based server application on behalf of the remote client/server-based client application.

14. The computer program product of claim 11, where the computer readable program code when executed on the computer further causes the computer to:

determine whether an alternative connection to any other message resilience client device is available; and

propagate, to at least one other message resilience client device to which the alternative connection is determined to be available, the message and the request to deliver the message to the client/server-based server application on behalf of the remote client/server-based client application.

15. The computer program product of claim 14, where the computer readable program code when executed on the computer further causes the computer to:

determine whether message presence information that identifies the message exists within the message presence database;

in response to determining that the message presence information that identifies the message does not exist within the message presence database;

create message presence information within the message presence database that identifies the message and message propagation information within the created message presence information that identifies each other message resilience client device to which the message and the request to deliver the message is propagated; and

in response to determining that the message presence information that identifies the message exists within the message presence database;

create message propagation information within the message presence information that identifies each other message resilience client device to which the message and the request to deliver the message is propagated.