Systems and methods for cache and pool initialization on demand

• US 20050262305A1
• Filed: 10/15/2004
• Published: 11/24/2005
• Est. Priority Date: 05/21/2004
• Status: Active Grant

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: BEA Systems Incorporated (Oracle Corporation)
• Inventors: Chow, Thorick, White, Seth
• Granted Patent: US 7,756,910 B2
• Time in Patent Office: Days
• US Class Current: 711/133
• CPC Class Codes: G06F 12/023 Free address space management
• CPC Class Codes: G06F 12/0891 using clearing, invalidating or resetting means

Abstract

The present invention provides users and processes with various features to control the memory usage by a cache and pool dynamically at runtime. The cache and pool can be initialized on demand to remove idle objects of classes from them without the server being restarted. When the cache and pool reach their maximum sizes, idle objects in them may be removed to make room for newly active objects using various strategies in batches, where the schedule (periodicity), size and processing time of each batch can be dynamically adjusted. When a newly created object is being added to a full cache where each object is enrolled in a transaction, one or more active objects may be passivated from the cache based on various criteria to make room for the new instance to be added. Various features of the cache and pool can be defined in a configuration file. This description is not intended to be a complete description of, or limit the scope of, the invention. Other features, aspects, and objects of the invention can be obtained from a review of the specification, the figures, and the claims.

Claims

1. A system to support cache initialization on demand, comprising:

a cache capable of storing in memory one or more objects of each of one or more classes defined by an object-oriented programming language; and

a cache control component capable of initializing the cache on demand at runtime to the initial condition before a class in the one or more classes is deployed by removing one or more idle objects of the class from the cache.

2. The system according to claim 1, wherein:

the object-oriented programming language can be Java®

or C++.

3. The system according to claim 1, wherein:

the class can be one of an interface, a module, a Java®

bean and an EJB type.

4. The system according to claim 1, wherein:

the cache control component is further capable of initializing the cache without shutting down and/or starting up an application server running the cache.

5. The system according to claim 1, wherein:

the cache control component is further capable of performing on each object in the one or more objects at least one of;

instantiating and/or adding the object into the cache and setting the idle time of the object to zero; and

monitoring the active and/or idle time of the object.

6. The system according to claim 1, further comprising:

a button associated with the class on an user interface, wherein the button is capable of triggering the initialization of the cache of the class.

7. The system according to claim 6, wherein:

the user interface can be a console.

8. A system to support cache initialization on demand, comprising:

a cache capable of storing in memory one or more instances of each of one or more EJB types; and

a cache control component capable of initializing the cache on demand at runtime to the initial condition before an EJB type in the one or more EJB types is deployed by removing one or more idle instances of the EJB type from the cache.

9. A system to support pool initialization on demand, comprising:

a pool capable of storing in memory one or more objects of each of one or more classes; and

a pool control component capable of initializing the pool on demand at runtime to the initial condition before a class in the one or more classes is deployed by removing one or more idle objects of the class from the pool until one or more criteria are met.

10. The system according to claim 9, wherein:

the pool control component is further capable of initializing the pool without shutting down and/or starting up an application server running the pool.

11. The system according to claim 9, further comprising:

one or more properties associated with a class of the one or more classes; and

a configuration file capable of defining the one or more properties.

12. The system according to claim 11, wherein:

a property in the one or more properties can be the initial size of the pool for the class, i.e., the initial number of objects of the class set for the pool.

13. The system according to claim 9, wherein:

a criterion in the one or more retry criteria can be the size of the pool for the class is no greater than the initial size of the pool for the class.

14. A system to support pool initialization on demand, comprising:

a pool capable of storing in memory one or more instances of each of one or more EJB types; and

a pool control component capable of initializing the pool on demand at runtime to the initial condition before an EJB type in the one or more EJB types is deployed by removing one or more idle instances of the EJB type from the pool until one or more criteria are met.

15. The system according to claim 14, further comprising:

one or more properties associated with an EJB type of the one or more EJB types; and

a deployment descriptor capable of defining the one or more properties.

16. A method to support cache initialization on demand, comprising:

storing in memory one or more objects of each of one or more classes defined by an object-oriented programming language via a cache; and

initializing the cache on demand at runtime to the initial condition before a class in the one or more classes is deployed by removing one or more idle objects of the class from the cache.

17. The method according to claim 16, further comprising:

initializing the cache without shutting down and/or starting up an application server running the cache.

18. The method according to claim 16, further comprising:

performing on each object in the one or more objects at least one of;

instantiating and/or adding the object into the cache and setting the idle time of the object to zero; and

monitoring the active and/or idle time of the object.

19. The method according to claim 16, further comprising:

triggering the initialization of the cache of the class via a button associated with the class on an user interface, wherein the user interface can be a console.

20. A method to support cache initialization on demand, comprising:

storing in memory one or more instances of each of one or more EJB types via a cache; and

initializing the cache on demand at runtime to the initial condition before an EJB type in the one or more EJB types is deployed by removing one or more idle instances of the EJB type from the cache.

21. A method to support pool initialization on demand, comprising:

storing in memory one or more objects of each of one or more classes via a pool; and

initializing the pool on demand at runtime to the initial condition before a class in the one or more classes is deployed by removing one or more idle objects of the class from the pool until one or more criteria are met.

22. The method according to claim 21, further comprising:

initializing the pool without shutting down and/or starting up an application server running the pool.

23. The method according to claim 21, further comprising:

defining one or more properties associated with a class of the one or more classes via a configuration file.

24. A method to support pool initialization on demand, comprising:

storing in memory one or more instances of each of one or more EJB types via a pool; and

initializing the pool on demand at runtime to the initial condition before an EJB type in the one or more EJB types is deployed by removing one or more idle instances of the EJB type from the pool until one or more criteria are met.

25. The method according to claim 24, further comprising:

defining one or more properties associated with an EJB type of the one or more EJB types via a deployment descriptor.

26. A machine readable medium having instructions stored thereon that when executed by a processor cause a system to:

store in memory one or more objects of each of one or more classes defined by an object-oriented programming language via a cache; and

initialize the cache on demand at runtime to the initial condition before a class in the one or more classes is deployed by removing one or more idle objects of the class from the cache.

27. The machine readable medium of claim 26, further comprising instructions that when executed cause the system to:

initialize the cache without shutting down and/or starting up an application server running the cache.

28. The machine readable medium of claim 26, further comprising instructions that when executed cause the system to:

perform on each object in the one or more objects at least one of;

instantiating and/or adding the object into the cache and setting the idle time of the object to zero; and

monitoring the active and/or idle time of the object.

29. The machine readable medium of claim 26, further comprising instructions that when executed cause the system to:

trigger the initialization of the cache of the class via a button associated with the class on an user interface, wherein the user interface can be a console.

30. A machine readable medium having instructions stored thereon that when executed by a processor cause a system to:

store in memory one or more instances of each of one or more EJB types via a cache; and

initialize the cache on demand at runtime to the initial condition before an EJB type in the one or more EJB types is deployed by removing one or more idle instances of the EJB type from the cache.

31. A machine readable medium having instructions stored thereon that when executed by a processor cause a system to:

store in memory one or more objects of each of one or more classes via a pool; and

initialize the pool on demand at runtime to the initial condition before a class in the one or more classes is deployed by removing one or more idle objects of the class from the pool until one or more criteria are met.

32. The machine readable medium of claim 31, further comprising instructions that when executed cause the system to:

initialize the pool without shutting down and/or starting up an application server running the pool.

33. The machine readable medium of claim 31, further comprising instructions that when executed cause the system to:

define one or more properties associated with a class of the one or more classes via a configuration file.

34. A machine readable medium having instructions stored thereon that when executed by a processor cause a system to:

store in memory one or more instances of each of one or more EJB types via a pool; and

initialize the pool on demand at runtime to the initial condition before an EJB type in the one or more EJB types is deployed by removing one or more idle instances of the EJB type from the pool until one or more criteria are met.

35. The machine readable medium of claim 34, further comprising instructions that when executed cause the system to:

define one or more properties associated with an EJB type of the one or more EJB types via a deployment descriptor.

36. A system to support cache initialization on demand, comprising:

means for storing in memory one or more objects of each of one or more classes defined by an object-oriented programming language via a cache; and

means for initializing the cache on demand at runtime to the initial condition before a class in the one or more classes is deployed by removing one or more idle objects of the class from the cache.

37. A system to support cache initialization on demand, comprising:

means for storing in memory one or more instances of each of one or more EJB types via a cache; and

means for initializing the cache on demand at runtime to the initial condition before an EJB type in the one or more EJB types is deployed by removing one or more idle instances of the EJB type from the cache.

38. A system to support pool initialization on demand, comprising:

means for storing in memory one or more objects of each of one or more classes via a pool; and

means for initializing the pool on demand at runtime to the initial condition before a class in the one or more classes is deployed by removing one or more idle objects of the class from the pool until one or more criteria are met.

39. A system to support pool initialization on demand, comprising:

means for storing in memory one or more instances of each of one or more EJB types via a pool; and

means for initializing the pool on demand at runtime to the initial condition before an EJB type in the one or more EJB types is deployed by removing one or more idle instances of the EJB type from the pool until one or more criteria are met.

40. A computer data signal embodied in a transmission medium, comprising:

a code segment including instructions to store in memory one or more objects of each of one or more classes defined by an object-oriented programming language via a cache; and

a code segment including instructions to initialize the cache on demand at runtime to the initial condition before a class in the one or more classes is deployed by removing one or more idle objects of the class from the cache.

41. A computer data signal embodied in a transmission medium, comprising:

a code segment including instructions to store in memory one or more instances of each of one or more EJB types via a cache; and

a code segment including instructions to initialize the cache on demand at runtime to the initial condition before an EJB type in the one or more EJB types is deployed by removing one or more idle instances of the EJB type from the cache.

42. A computer data signal embodied in a transmission medium, comprising:

a code segment including instructions to store in memory one or more objects of each of one or more classes via a pool; and

a code segment including instructions to initialize the pool on demand at runtime to the initial condition before a class in the one or more classes is deployed by removing one or more idle objects of the class from the pool until one or more criteria are met.

43. A computer data signal embodied in a transmission medium, comprising:

a code segment including instructions to store in memory one or more instances of each of one or more EJB types via a pool; and

a code segment including instructions to initialize the pool on demand at runtime to the initial condition before an EJB type in the one or more EJB types is deployed by removing one or more idle instances of the EJB type from the pool until one or more criteria are met.