Managing failover of J2EE compliant middleware in a high availability system

• US 7,634,683 B2
• Filed: 04/18/2007
• Issued: 12/15/2009
• Est. Priority Date: 01/20/2004
• Status: Expired due to Fees

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: De La Cruz, Francisco, Paolini, Michael A., Sethuraman, Radhakrishnan, Rothert, Douglas Scott
• Primary Examiner(s): GUYTON, PHILIP A
• Application Number:
  US11/736,685
• Publication Number:
  US 20070245167A1
• Time in Patent Office: 972 Days
• Field of Search: 714/4, 714/5, 714/6, 714/7, 714/11, 714/24
• US Class Current: 714/4.1
• CPC Class Codes: G06F 11/2025 using centralised failover control functionality
• CPC Class Codes: G06F 11/2028 eliminating a faulty processor or activating a spare

Abstract

A primary node and a secondary node each run the same J2EE compliant middleware stack comprising layers including a load balancer, a web server, a web application server, a message control server, a monitoring server, and a database control server. In the primary node, all layers are active. In the secondary node, part of the layers are active and part of the layers are in standby. A data replication partition shared between the primary node and the secondary node includes persistent resource data accessible to a selection of the layers of the primary node. A heartbeat controller monitors each node, including the middleware stack, and upon detection of a failure, controls transfer of the services provided by the primary node to the secondary node by transferring virtual IP addresses from the primary node to the secondary node, remounting the data replication partition for access by the secondary node, and activating the standby layers which require access to the data in the data replication partition.

Claims

1. A method for managing a high availability cluster during failover, comprising:

controlling a primary node running a middleware stack for supporting web applications, wherein a plurality of layers of said middleware stack are active, wherein said primary node is assigned a virtual IP address to which requests are directed;

controlling a secondary node running a redundant middleware stack mirroring said plurality of layers of said middleware stack of said primary node, wherein a first selection of said plurality of layers of said redundant middleware stack are active and a second selection of said plurality of layers of said redundant middleware stack are in standby;

managing a data replication partition shared between said primary node and said secondary node with data accessible to a selection of said plurality of layers of said active middleware stack, wherein said selection of said plurality of layers of said active middleware stack correspond to said second selection of said plurality of layers of said redundant middleware stack in standby; and

responsive to detecting a failure at said primary node, transferring said virtual IP address from said primary node to said secondary node, turning off power to said primary node, remounting said data replication partition for access by said secondary node, and activating said second selection of said plurality of layers of said redundant middleware stack which require access to said data within said data replication partition.

2. The method according to claim 1 for managing a high availability cluster, further comprising:

controlling said middleware stack and said redundant middleware stack to support J2EE compliant web applications.

3. The method according to claim 1 for managing a high availability cluster, further comprising:

enabling a web application server active on said secondary node before failover points to access a messaging server and a database control server from said middleware stack of said primary node.

4. The method according to claim 1 for managing a high availability cluster, further comprising:

launching a message queue and a relational database in said data replication partition.

5. The method according to claim 1 for managing a high availability cluster, further comprising:

responsive to detecting said failure at said primary node, for sending a shutoff command to turn off power to said primary node.

6. The method according to claim 1 for managing a high availability cluster, further comprising:

monitoring a status of a plurality of services provided by said middleware stack;

responsive to detecting a failure of a particular service from among said plurality of services, restarting another instance of said particular service at said primary node with a particular persistent identifier.

7. The method according to claim 1 for managing a high availability cluster, further comprising:

sending heartbeat requests between said primary node and said secondary node; and

responsive to not receive a return of a heartbeat request, detecting a failure in the non-responsive node.

8. A system for managing a high availability cluster during failover, comprising:

a primary node comprising at least one computer system running a middleware stack for supporting web applications,

wherein a plurality of layers of said middleware stack are active, wherein said primary node is assigned a virtual IP address to which requests are directed;

a secondary node comprising said at least one computer system running a redundant middleware stack mirroring said plurality of layers of said middleware stack of said primary node, wherein a first selection of said plurality of layers of said redundant middleware stack are active and a second selection of said plurality of layers of said redundant middleware stack are in standby;

a data replication partition shared between said primary node and said secondary node with data accessible to a selection of said plurality of layers of said active middleware stack, wherein said selection of said plurality of layers of said active middleware stack correspond to said second selection of said plurality of layers of said redundant middleware stack in standby; and

a heartbeat monitor for detecting a failure at said primary node, wherein in response to detecting said failure at said primary node, said heartbeat monitor transfers said virtual IP address from said primary node to said secondary node, said heartbeat monitor turn off power to said primary node, said heartbeat monitor remounts said data replication partition for access by said secondary node, and said heartbeat monitor activates said second selection of said plurality of layers of said redundant middleware stack requiring access to said data within said data replication partition.

9. The system according to claim 8 for managing a high availability cluster, wherein said middleware stack and said redundant middleware stack support J2EE compliant web applications.

10. The system according to claim 8 for managing a high availability cluster, wherein a web application server active on said secondary node before failover points to a virtual IP address of a messaging server and a database control server from said middleware stack of said primary node.

11. The system according to claim 10 for managing a high availability cluster, wherein responsive to detecting said failure at said primary node, said heartbeat monitor takes over said virtual IP address and configures said second selection of said plurality of layers of said redundant middleware stack with said virtual IP address on startup.

12. The system according to claim 8 for managing a high availability cluster, wherein a message queue and a relational database are launched in said data replication partition.

13. The system according to claim 8 for managing a high availability cluster, wherein said data replication partition is a Data Replication Block Device.

14. The system according to claim 8 for managing a high availability cluster, further comprising:

a service monitoring daemon for monitoring a status of a plurality of services provided by said middleware stack, wherein responsive to detecting a failure of a particular service from among said plurality of services, said service monitoring daemon restarts another instance of said particular service at said primary node with a particular process identifier.

15. The system according to claim 8 for managing a high availability cluster, further comprising:

a cross-over cable connected between said primary node and said secondary node via network adapters; and

said heartbeat monitor for sending heartbeat requests via said cross-over cable, wherein in response to not receive a return of a heartbeat request, said heartbeat monitor detects a failure in the non-responsive node.

16. A computer program product, residing on a volatile or nonvolatile computer readable medium, for managing a high availability cluster during failover, comprising:

means for controlling a primary node running a middleware stack for supporting web applications, wherein a plurality of layers of said middleware stack are active, wherein said primary node is assigned a virtual IP address to which requests are directed;

means for controlling a secondary node running a redundant middleware stack mirroring said plurality of layers of said middleware stack of said primary node, wherein a first selection of said plurality of layers of said redundant middleware stack are active and a second selection of said plurality of layers of said redundant middleware stack are in standby;

means for managing a data replication partition shared between said primary node and said secondary node with data accessible to a selection of said plurality of layers of said active middleware stack, wherein said selection of said plurality of layers of said active middleware stack correspond to said second selection of said plurality of layers of said redundant middleware stack in standby; and

means, responsive to detecting a failure at said primary node, transferring said virtual IP address from said primary node to said secondary node, for turning off power to said primary node, remounting said data replication partition for access by said secondary node, and activating said second selection of said plurality of layers of said redundant middleware stack which require access to said data in said data replication partition.

17. The computer program product according to claim 16 for managing a high availability cluster, furthering comprising:

means for controlling said middleware stack and said redundant middleware stack to support J2EE compliant web applications.

18. The computer program product according to claim 16 for managing a high availability cluster, further comprising:

means for enabling a web application server active on said secondary node before failover points to access a messaging server and a database control server from said middleware stack of said primary node.

19. The computer program product according to claim 16 for managing a high availability cluster, further comprising:

means, responsive to detecting said failure at said primary node, for sending a shutoff command to turn off power to said primary node.

20. The computer program product according to claim 16 for managing a high availability cluster, further comprising:

means for sending heartbeat requests between said primary node and said secondary node; and

means, responsive to not receive a return of a heartbeat request, for detecting a failure in the non-responsive node.