IP Library Granted Patent US 7,634,684
Granted Patent B2
US 7,634,684 · App. 11/754,619 · Granted Dec 15, 2009

Intelligent configuration for restarting failed application server instances

View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 7,634,684
App. No.
11/754,619
Granted
Dec 15, 2009
Kind
B2
Abstract

An improved solution for intelligent configuration for restarting failed application server instances is provided. In an embodiment of the invention, a method for restarting a failed application server instance includes: receiving a notice of a failure of an application server instance; obtaining a cause of the failure; automatically applying at least one configuration change to the application server instance based on the cause; and recovering the application server instance.

Claims (43)

1. A method for restarting a failed application server instance, the method comprising:

receiving a notice of a failure of an application server instance;

obtaining a cause of the failure;

automatically applying at least one configuration change to the application server instance based on the cause; and

recovering the application server instance.

2. The method of claim 1 , wherein the at least one configuration change is specified by a predefined rule.

3. The method of claim 2 , wherein the predefined rule comprises determining if the failure is a recurring failure.

4. The method of claim 1 , wherein the instance comprises a portion of a Java Virtual Machine (JVM).

5. The method of claim 1 , further comprising applying the at least one configuration change to at least one of: a non-failed instance or a new instance of a server.

6. The method of claim 5 , the applying further comprising shutting down and restarting the non-failed instance server.

7. The method of claim 1 , wherein the cause comprises insufficient Java 2 Enterprise Edition (J2EE) server resources.

8. The method of claim 7 , wherein the insufficient J2EE server resources comprise at least one selected from a group consisting of: insufficient memory available to a Java Virtual Machine (JVM), insufficient connections in a Java Database Connectivity (JDBC) connection pool, insufficient connection in a web container pool, and insufficient threads in an object request broker (ORB).

9. The method of claim 1 , further comprising applying the at least one configuration change to an added server.

10. The method of claim 1 , the recovering including restarting the server.

11. The method of claim 1 , further comprising detecting the failure at the application server instance.

12. The method of claim 1 , wherein the application server is part of a server farm, and the automatically applying including applying the at least one configuration change to at least one server in the server farm.

13. A system for restarting a failed application server instance, the system comprising:

a system for receiving a notice of a failure of an application server instance;

a system for obtaining a cause of the failure;

a system for automatically applying at least one configuration change to the application server instance based on the cause; and

a system for recovering the application server instance.

14. The system of claim 13 , wherein the at least one configuration change is specified by a predefined rule.

15. The system of claim 14 , wherein the predefined rule comprises determining if the failure is a recurring failure.

16. The system of claim 13 , wherein the instance comprises a portion of a Java Virtual Machine (JVM).

17. The system of claim 13 , further comprising a system for applying the at least one configuration change to at least one of: a non-failed instance or a new instance of a server.

18. The system of claim 17 , the system for applying further comprising a system for shutting down and restarting the non-failed instance server.

19. The system of claim 13 , wherein the cause comprises insufficient Java 2 Enterprise Edition (J2EE) server resources.

20. The system of claim 19 , wherein the insufficient J2EE server resources comprise at least one selected from a group consisting of: insufficient memory available to a Java Virtual Machine (JVM), insufficient connections in a Java Database Connectivity (JDBC) connection pool, insufficient connection in a web container pool, and insufficient threads in an object request broker (ORB).

21. The system of claim 13 , further comprising a system for applying the at least one configuration change to an added server.

22. The system of claim 13 , the system for recovering including a system for restarting the server.

23. The system of claim 13 , further comprising a system for detecting the failure.

24. The system of claim 13 , wherein the application server is part of a server farm, and the system for automatically applying including a system for applying the at least one configuration change to at least one server in the server farm.

25. A computer program comprising program code stored on a computer-readable medium, which when executed, enables a computer system to implement a method for restarting a failed application server instance, the method comprising:

receiving a notice of a failure of an application server instance;

obtaining a cause of the failure;

automatically applying at least one configuration change to the application server instance based on the cause; and

recovering the application server instance.

26. A method of generating a system for restarting a failed application server instance, the method comprising:

providing a computer system operable to:

receive a notice of a failure of an application server instance;

obtain a cause of the failure;

automatically apply at least one configuration change to the application server instance based on the cause; and

recover the application server instance.

Assignments (3)
CHANGE OF NAME Recorded Oct 2, 2017
From: GOOGLE INC.
To: GOOGLE LLC
Reel/Frame 044101/0610 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Dec 30, 2011
From: INTERNATIONAL BUSINESS MACHINES CORPORATION
To: GOOGLE INC.
Reel/Frame 027463/0594 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jul 2, 2007
From: CLARK, LAWRENCE E.; JOINES, STACY R.; LYLE, RUTHIE D.
To: INTERNATIONAL BUSINESS MACHINES CORPORATION
Reel/Frame 019506/0168 →