MANAGING FAILOVER OF J2EE COMPLIANT MIDDLEWARE IN A HIGH AVAILABILITY SYSTEM
First Claim
1. A system for managing a high availability cluster during failover, comprising:
- 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;
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;
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, 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.
0 Assignments
0 Petitions
Accused Products
Abstract
A method, system, and program for managing failover of J2EE compliant middleware in a high availability system are provided. 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.
93 Citations
33 Claims
-
1. A system for managing a high availability cluster during failover, comprising:
-
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;
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;
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, 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. - View Dependent Claims (2, 5, 6, 7, 8, 10, 11)
-
-
3. (canceled)
-
4. (canceled)
-
9. (canceled)
-
12. (canceled)
-
13. (canceled)
-
14. (canceled)
-
15. 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 turn off power to said primary node, remounting said data replication partition for access by said secondary node, 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. - View Dependent Claims (16, 19, 20, 21, 22, 23)
-
-
17. (canceled)
-
18. (canceled)
-
24. (canceled)
-
25. A computer program product, residing on a 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 turn off power to said primary node, remounting said data replication partition for access by said secondary node, 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. - View Dependent Claims (26, 28, 30, 32)
-
-
27. (canceled)
-
29. (canceled)
-
31. (canceled)
-
33. (canceled)
Specification