Reclaiming resources in response to forced state transitions

• US 20040059749A1
• Filed: 09/24/2002
• Published: 03/25/2004
• Est. Priority Date: 09/24/2002
• Status: Active Grant

• Current Assignee: LinkedIn Corporation (Microsoft Corporation)
• Original Assignee: International Business Machines Corporation
• Inventors: Frey, Jeffrey A., Sykes, Matthew J., Kinder, Stephen J.
• Granted Patent: US 7,143,106 B2
• Time in Patent Office: Days
• US Class Current: 707/103R
• CPC Class Codes: G06F 9/5011 the resources being hardware resources other than CPUs, Servers and Terminals
• CPC Class Codes: G06F 9/5022 Mechanisms to release resources
• CPC Class Codes: Y10S 707/99944 Object-oriented database structure
• CPC Class Codes: Y10S 707/99945 Object-oriented database structure processing

Abstract

Resources used by components are aggressively reclaimed, in order to enable those resources to be available to other components. To aggressively reclaim one or more resources of a component, the component is forced to transition from one state to a reclaim state, and at the reclaim state, the resources are reclaimed, if necessary.

Claims

1. A method of reclaiming resources, said method comprising:

forcing a component to transition from a state to a reclaim state to reclaim one or more resources associated with the component; and

reclaiming at least one resource of the one or more resources, in response to the forced transition.

2. The method of claim 1, wherein the forcing is based on a reclaim management policy associated with the component.

3. The method of claim 1, wherein the component is a component of an application, and wherein the reclaiming is invisible to at least one of the component and one or more other components of the application.

4. The method of claim 1, further comprising determining, at a decision state within a lifecycle of states of said component, whether said forcing is to take place, and wherein said forcing comprises forcing said component from the decision state to the reclaim state, in response to the determining.

5. The method of claim 4, wherein said determining comprises checking whether at least one resource of the component is to be managed aggressively.

6. The method of claim 4, wherein said determining comprises dynamically determining, based on one or more considerations, whether said forcing is to occur.

7. The method of claim 6, wherein said one or more considerations comprises determining whether a desired number of resources are available.

8. The method of claim 1, wherein at least one resource of the one or more resources comprises a connection.

9. The method of claim 8, wherein the component comprises a bean instance.

10. A system of reclaiming resources, said system comprising:

means for forcing a component to transition from a state to a reclaim state to reclaim one or more resources associated with the component; and

means for reclaiming at least one resource of the one or more resources, in response to the forced transition.

11. The system of claim 10, wherein the forcing is based on a reclaim management policy associated with the component.

12. The system of claim 10, wherein the component is a component of an application, and wherein the reclaiming is invisible to at least one of the component and one or more other components of the application.

13. The system of claim 10, further comprising means for determining, at a decision state within a lifecycle of states of said component, whether the forcing is to take place, and wherein said means for forcing comprises means for forcing said component from the decision state to the reclaim state, in response to the determining.

14. The system of claim 13, wherein said means for determining comprises means for checking whether at least one resource of the component is to be managed aggressively.

15. The system of claim 13, wherein said means for determining comprises means for dynamically determining, based on one or more considerations, whether the forcing is to occur.

16. The system of claim 15, wherein said one or more considerations comprises determining whether a desired number of resources are available.

17. The system of claim 10, wherein at least one resource of the one or more resources comprises a connection.

18. The system of claim 17, wherein the component comprises a bean instance.

19. A system of reclaiming resources, said system comprising:

a container to force a component to transition from a state to a reclaim state to reclaim one or more resources associated with the component, and to at least initiate reclaim of at least one resource of the one or more resources, in response to the forced transition.

20. At least one program storage device readable by a machine tangibly embodying at least one program of instructions executable by the machine to perform a method of reclaiming resources, said method comprising:

forcing a component to transition from a state to a reclaim state to reclaim one or more resources associated with the component; and

reclaiming at least one resource of the one or more resources, in response to the forced transition.

21. The at least one program storage device of claim 20, wherein the forcing is based on a reclaim management policy associated with the component.

22. The at least one program storage device of claim 20, wherein the component is a component of an application, and wherein the reclaiming is invisible to at least one of the component and one or more other components of the application.

23. The at least one program storage device of claim 20, wherein said method further comprises determining, at a decision state within a lifecycle of states of said component, whether said forcing is to take place, and wherein said forcing comprises forcing said component from the decision state to the reclaim state, in response to the determining.

24. The at least one program storage device of claim 23, wherein said determining comprises checking whether at least one resource of the component is to be managed aggressively.

25. The at least one program storage device of claim 23, wherein said determining comprises dynamically determining, based on one or more considerations, whether said forcing is to occur.

26. The at least one program storage device of claim 25, wherein said one or more considerations comprises determining whether a desired number of resources are available.

27. The at least one program storage device of claim 20, wherein at least one resource of the one or more resources comprises a connection.

28. The at least one program storage device of claim 27, wherein the component comprises a bean instance.