Garbage collection of persistent objects with dynamic multikeys

• US 10,289,728 B2
• Filed: 05/15/2006
• Issued: 05/14/2019
• Est. Priority Date: 05/15/2006
• Status: Active Grant

• Current Assignee: Avaya Incorporated
• Original Assignee: Avaya Incorporated
• Inventors: Klemm, Reinhard Peter
• Primary Examiner(s): Savla, Arpan P.
• Assistant Examiner(s): Tran, Bao G
• Application Number:
  US11/383,268
• Publication Number:
  US 20070276888A1
• Time in Patent Office: 4,747 Days
• Field of Search: 707102, 707206, 707200, 7079992, 707999, 707999002, 707748, 707812, 707999202, 707999001, 707610, 707618, 707797, 707798, 707802, 707803, 707809, 711133-136, 717152, 717166, 717177, 717116, 717120, 717714, 717716, 715234, 715753, 715791, 715792, 715802, 709203, 709230, 709234
• CPC Class Codes: G06F 12/0253 Garbage collection, i.e. reclamation of unreferenced memory
• CPC Class Codes: G06F 16/289 Object oriented databases

Abstract

A mechanism is disclosed that enables garbage collection of object instances that have persistent data and a mutable key. A mutable key capability is advantageous in a variety of applications, such as monitoring a set of users and their login status on a plurality of media servers (e.g., an email server, an instant messaging server, a voice mail server, a video server, an audio-conferencing server, etc.). Implementations based on the Enterprise JavaBean specification are disclosed for three illustrative embodiments of the present invention. The illustrative embodiments of the present invention can also be implemented in accordance with object persistence mechanisms other than Enterprise JavaBeans.

Claims

1. A method comprising:

identifying a non-persistent object instance comprising;

a first field having a first value configured to be mirrored in a database; and

a mutable primary key that uniquely identifies the non-persistent object instance, wherein the mutable primary key is a mutable value that can change during a life of the non-persistent object instance;

identifying a first persistent object instance comprising;

a first immutable primary key associated with the mutable primary key of the non-persistent object instance; and

a foreign key;

identifying a second persistent object instance comprising;

a second immutable primary key associated with the foreign key; and

a second field having a second value mirroring the first value, wherein the second field is configured to further mirror the second value to the database;

destroying the second persistent object instance;

destroying the first persistent object instance after the second persistent object instance is destroyed;

clearing the mutable primary key from the non-persistent object instance after the first persistent object instance is destroyed; and

marking, via a processor, the non-persistent object instance for garbage collection after the mutable primary key is cleared.

2. The method of claim 1, further comprising marking the first persistent object instance for garbage collection.

3. The method of claim 1, wherein the first and second persistent object instances are Enterprise JavaBean entity beans.

4. The method of claim 1, wherein the first immutable primary key is further associated with the first field.

5. The method of claim 1, further comprising marking the second persistent object instance for garbage collection.

6. The method of claim 1, wherein the non-persistent object instance is associated with a person.

7. The method of claim 1, wherein the mutable primary key is associated with at least one of an email address, a social security number, or a telephone number.

8. A non-transitory computer-readable storage device storing instructions which, when executed by a processor, cause the processor to perform operations comprising:

identifying a non-persistent object instance comprising;

a first field having a first value configured to be mirrored in a database; and

a mutable primary key that uniquely identifies the non-persistent object instance, wherein the mutable primary key is a mutable value that can change during a life of the non-persistent object instance;

identifying a first persistent object instance comprising;

a first immutable primary key associated with the mutable primary key of the non-persistent object instance; and

a foreign key;

identifying a second persistent object instance comprising;

a second immutable primary key associated with the foreign key; and

a second field having a second value mirroring the first value, wherein the second field is configured to further mirror the second value to the database;

destroying the second persistent object instance;

destroying the first persistent object instance after the second persistent object instance is destroyed;

clearing the mutable primary key from the non-persistent object instance after the first persistent object instance is destroyed; and

marking the non-persistent object instance for garbage collection after the mutable primary key is cleared.

9. The non-transitory computer-readable storage device of claim 8, storing additional instructions which, when executed by the processor, cause the processor to perform further operations comprising changing the mutable value.

10. The non-transitory computer-readable storage device of claim 8, wherein one of the first and second persistent object instances is an Enterprise JavaBean entity bean.

11. The non-transitory computer-readable storage device of claim 8, storing additional instructions which, when executed by the processor, cause the processor to perform further operations comprising marking the first persistent object instance for garbage collection.

12. The non-transitory computer-readable storage device of claim 8, wherein the first immutable primary key is further associated with the first field.

13. The non-transitory computer-readable storage device of claim 8, storing additional instructions which, when executed by the processor, cause the processor to perform further operations comprising marking the second persistent object instance for garbage collection.

14. The non-transitory computer-readable storage device of claim 8, wherein the mutable primary key is associated with at least one of an email address, a social security number, or a telephone number.

15. A system comprising:

a processor; and

a non-transitory computer-readable storage medium storing instructions which, when executed by the processor, cause the processor to perform operations comprising;

identifying a non-persistent object instance, comprising;

a first field having a first value configured to be mirrored in a database; and

a mutable primary key that uniquely identifies the non-persistent object instance, wherein the mutable primary key is a mutable value that can change during a life of the non-persistent object instance;

identifying a first persistent object instance comprising;

a first immutable primary key associated with the mutable primary key of the non-persistent object instance; and

a foreign key;

identifying a second persistent object instance comprising;

a second immutable primary key associated with the foreign key; and

a second field having a second value mirroring the first value,

wherein the second field is configured to further mirror the second value to the persistent store;

destroying the second persistent object instance;

destroying the first persistent object instance after the second persistent object instance is destroyed;

clearing the mutable primary key from the non-transitory object instance after the first persistent object instance is destroyed; and

marking the non-persistent object instance for garbage collection after the mutable primary key is cleared.

16. The system of claim 15, wherein the non-transitory computer-readable storage medium stores additional instructions which, when executed by the processor, cause the processor to perform further operations comprising changing the mutable value.

17. The system of claim 15, wherein the first and second persistent object instances are Enterprise JavaBean entity beans.

18. The system of claim 15, wherein the non-transitory computer-readable storage medium stores additional instructions which, when executed by the processor, cause the processor to perform further operations comprising marking the first persistent object instance for garbage collection.

19. The system of claim 15, wherein the first immutable primary key is associated with the first field.

20. The system of claim 15, wherein the non-transitory computer-readable storage medium stores additional instructions which, when executed by the processor, cause the processor to perform further operations comprising marking the second persistent object instance for garbage collection.

21. The system of claim 15, wherein the mutable primary key is associated with at least one of an email address, a social security number, or a telephone number.