METHOD, SYSTEM AND MACHINE ACCESSIBLE MEDIUM OF A RECONNECT MECHANISM IN A DISTRIBUTED SYSTEM (CLUSTER-WIDE RECONNECT MECHANISM)

• US 20090172463A1
• Filed: 12/28/2007
• Published: 07/02/2009
• Est. Priority Date: 04/30/2007
• Status: Active Grant

• Current Assignee: SAP SE
• Original Assignee: SAP AG (SAP SE)
• Inventors: Matov, Peter K., Tankov, Nikolai D., Gatev, Andrei A.
• Granted Patent: US 7,937,611 B2
• Time in Patent Office: Days
• US Class Current: 714/4
• CPC Class Codes: G06F 11/1443 Transmit or communication errors

Abstract

A method, system and machine accessible medium for validating a plurality of connections to a backend in a distributed system. A connection request requiring access to a backend is processed at a first node of a distributed system. The access to the backend enabled through a connection from a plurality of connections on the first node. The plurality of connections on the first node is validated in response to a connection request failure. A plurality of connections on a second node is validated in response to the connection request failure.

Claims

1. A method comprising:

processing a connection request at a first server of a distributed computer system;

validating a plurality of connections providing access to a backend at the first server responsive to a connection request failure; and

triggering validation of a plurality of connections at a second server of the distributed computer system responsive to the connection request failure.

2. The method of claim 1 wherein processing a connection request comprises:

receiving a request by an application to access the backend; and

routing the request through a connection from the plurality of connections providing access to the backend at the first server.

3. The method of claim 1, wherein validating the plurality of connections at the first server comprises:

identifying all invalid connections providing access to the backend; and

destroying the identified invalid connections.

4. The method of claim 3 further comprising:

checking for existing valid connections providing access to the backend; and

creating a valid connection providing access to the backend when no valid connection exists and the backend is accessible.

5. The method of claim 1, wherein triggering validation of the plurality of connections at the second server comprises:

sending a message to the second server, the message indicative of a connection request failure on the first server.

6. The method of claim 1, wherein triggering validation of the plurality of connections at the second server comprises:

checking for existing valid connections providing access to the backend; and

sending a message to the second server when there is no valid connection, the message indicative of no existing valid connection providing access to the backend on the first server.

7. A system comprising:

an application at a server node in a distributed computer system to process connection requests;

a backend;

a plurality of connections to provide access to the backend responsive to the connection requests; and

a connectivity interface to validate the connections responsive to a connection request failure and to trigger connections validation at a second server node.

8. The system of claim 7 further comprising:

a connection handler to logically link the connections with the backend.

9. The system of claim 7 further comprising:

a plurality of sockets, each socket to link a connection with the backend on a system platform level; and

an event trigger to trigger an event indicative for a connection request failure.

10. The system of claim 7 further comprising:

a connection pool to provide a plurality of connections to a backend.

11. The system of claim 7 wherein the connectivity interface comprises:

a listener to receive the event indicative for a connection failure; and

a connection pool manager to create a connection pool.

12. The system of claim 11 further comprising:

a communicator to send a message to the second node indicative for the received event.

13. A machine readable medium having instructions stored therein which when executed cause a machine to perform a set of operations comprising:

processing a connection request at a first server of a distributed computer system;

validating a plurality of connections providing access to a backend at the first server responsive to a connection request failure; and

triggering validation of a plurality of connections at a second server of the distributed computer system responsive to the connection request failure.

14. The machine readable medium of claim 13 wherein processing a connection request comprises:

receiving a request by an application to access the backend; and

routing the request through a connection from the plurality of connections providing access to the backend at the first server.

15. The machine readable medium of claim 13, wherein validating the plurality of connections at the first server comprises:

identifying all invalid connections providing access to the backend; and

destroying the identified invalid connections.

16. The machine readable medium of claim 15, having further instructions stored therein which when executed cause a machine to perform a set of operations further comprising:

checking for existing valid connections providing access to the backend; and

creating a valid connection providing access to the backend when no valid connection exists and the backend is accessible.

17. The machine readable medium of claim 13, wherein triggering validation of the plurality of connections at the second server comprises:

sending a message to the second server, the message indicative of a connection request failure on the first server.

18. The machine readable medium of claim 13, wherein triggering validation of the plurality of connections at the second server comprises:

checking for existing valid connections providing access to the backend; and

sending a message to the second server when there is no valid connection, the message indicative of no existing valid connection providing access to the backend on the first server.