Method of detecting lost objects in a software system

• US 7,017,152 B2
• Filed: 04/06/2001
• Issued: 03/21/2006
• Est. Priority Date: 04/06/2001
• Status: Active Grant

• Current Assignee: Nasdaq Technology AB (Nasdaq, Inc.)
• Original Assignee: Appmind Software AB
• Inventors: Bystedt, Ingemar, Wretman, Niklas, Dunell, Bo
• Primary Examiner(s): Chaki, Kakali
• Assistant Examiner(s): VU, TUAN A
• Application Number:
  US09/827,810
• Publication Number:
  US 20040015848A1
• Time in Patent Office: 1,810 Days
• Field of Search: 707/103.R, 709201-203, 709/248, 709/213, 711/202, 711/203, 711/207, 711133-134, 711/141, 711/158, 717/127, 717/118, 717/140, 717/178, 717/131, 718/107, 718/104, 715/513, 715/740
• US Class Current: 717/130
• CPC Class Codes: G06F 9/4493 Object persistence

Abstract

The execution of program sections written in an object-oriented programming language is supervised. A program section is started, and a supervision object is created as an instance of a class. In a memory, information is stored to identify the created object for a time period. The program section is terminated, and the information stored in the memory is removed when the created object is completed and/or inactive. The memory is then scanned to identify information that has been stored in the memory longer than the time period, and if so, an alarm signal is triggered.

Claims

1. A computer-implemented method of supervising the execution of one or more program sections written in an object-oriented programming language, comprising:

(a) starting a program section and creating an object as an instance of a class;

(b) storing in a memory a timing information unit associated with the created object and an expiration time period associated with the stored information unit, the information unit associated with the created object allowing supervision of execution of the program section;

(c) removing the timing information unit stored in the memory when the associated object is completed;

(d) scanning the memory to identify a timing information unit associated with an object that is not completed and for which there has been no activity for a time period longer than the associated expiration time period;

(e) testing the object associated with the identified timing information unit to determine whether the object is active or not active; and

(f) if the object is active, resetting the associated expiration time period, and if the object is inactive, triggering an alarm signal.

2. The method according to claim 1, wherein step (b) further comprises recording a starting time of the expiration time period.

3. The method according to claim 1, further comprising:

designating the uncompleted object for which there has been no activity for a time period longer than the associated expiration time period as being in a lost state.

4. The method according to claim 3, wherein the alarm signal indicates that a failure associated with the lost object has been detected.

5. The method according to claim 1, further comprising:

maintaining statistical information about a number of instances in each class.

6. The method according to claim 5, further comprising:

generating a message when a usage volume exceeds a predetermined level.

7. The method in claim 1, further comprising creating a register key associated with the object.

8. The method in claim 1, further comprising storing one or more contexts in a memory location associated with the created object, and

correlating faults in objects in a distributed environment using the one or more contexts.

9. A computer-implemented method of supervising the execution of one or more program sections written in an object-oriented programming language, comprising:

(a) starting a program section and creating an object;

(b) storing a timing information unit identifying the created object in a memory, the timing information unit associated with the created object allowing supervision of execution of the program section;

(c) removing the timing information unit stored in the memory when the created object is completed;

(d) scanning the memory to identify a timing information unit associated with an object that is not completed and for which there has been no activity for a time period longer than a predetermined time period;

(e) testing to determine if the associated object is active or inactive;

(f) for each timing information unit identified in step (d) when the object is inactive, notifying an operator and marking a memory location storing the information unit as free; and

(g) resetting an activity time period for the object when the object is active.

10. The method in claim 9, further comprising:

(g) delaying a transmission of the alarm signal for each timing information unit identified in step (d) when the created object is active.

11. The method in claim 9, further comprising creating a register key associated with the object.

12. The method in claim 9, further comprising storing one or more contexts in a memory location associated with the created object, and

correlating faults in objects in a distributed environment using the one or more contexts.

13. Apparatus for supervising the execution of one or more program sections written in an object-oriented programming language, comprising:

electronic circuitry configured to start a program section and creating an object as an instance of a class; and

a memory for storing a timing information unit associated with the created object and an expiration time period associated with the stored timing information unit, the timing information unit associated with the created object allowing supervision of execution of the program section;

the electronic circuitry further configured to;

remove the timing information unit stored in the memory unit when the created object is completed;

scan the memory to identify the timing information unit associated with an object that is not completed and for which there has been no activity for a time period longer than the associated expiration time period;

test to determine if the associated object is active or inactive;

trigger an alarm signal in response to the identified timing information unit if the object is determined to be inactive; and

reset the associated expiration time period if the object is determined to be active.

14. The apparatus according to claim 13, wherein the electronic circuitry is further configured to record a starting time of the expiration time period.

15. The apparatus according to claim 13, wherein the electronic circuitry is further configured to detect the uncompleted object for which there has been no activity for a time period longer than the associated expiration time period as being in a lost state.

16. The apparatus according to claim 15, wherein the electronic circuitry is further configured to delay termination of the program section after lapse of the expiration time period if the created object is active.

17. The apparatus according to claim 15, wherein the alarm signal indicates that a failure associated with the lost object has been detected.

18. The apparatus according to claim 13, wherein the electronic circuitry is further configured to:

maintain statistical information about a number of instances in each class.

19. The apparatus according to claim 13, wherein the electronic circuitry is further configured to:

generate a message when a usage volume exceeds a predetermined level.

20. The method in claim 13, wherein the electronic circuitry is further configured to create a register key associated with the object.

21. The method in claim 13, wherein the electronic circuitry is further configured to store one or more contexts in a memory location associated with the created object and to correlate faults in objects in a distributed environment using the one or more contexts.

22. An apparatus for supervising the execution of one or more program sections written in an object-oriented programming language, comprising:

electronic circuitry configured to start a program section and creating an object as an instance of a class; and

a memory for storing timing information unit identifying the created object;

the electronic circuitry further configured to;

remove the timing information unit stored in the memory when the created object is completed or inactive;

scan the memory to identify the timing information unit having been stored in the memory for a time period longer than a predetermined time period;

test the object associated with the identified timing information unit to determine whether the object is active or not active; and

if the object is active, reset an activity time period associated with the object, and if the object is inactive, designate the object as being in a lost state and send an alarm signal.

23. The apparatus in claim 22, wherein the electronic circuitry is further configured to send the alarm signal only when the information unit has been stored in the memory for a time period longer than the predetermined time period and the created object is inactive.

24. The apparatus in claim 22, wherein the electronic circuitry is further configured to delay sending the alarm signal when the created object is active.

25. The method in claim 22, wherein the electronic circuitry is further configured to create a register key associated with the object.

26. The method in claim 22, wherein the electronic circuitry is further configured to store one or more contexts in a memory location associated with the created object and to correlate faults in objects in a distributed environment using the one or more contexts.

27. A computer-implemented method of automatically supervising execution in an object-oriented software application, comprising;

(a) registering an object in a persistent location;

(b) specifying an expected expiration time associated with the object indicating an expected expiration time when the object is expected to terminate;

(c) deregistering the object, when the object terminates by the expected expiration time, by removing the object from the persistent location;

(d) supervising the persistent location to detect an object that has not been deregistered after expiration of the expected expiration time associated with the object;

(e) testing the detected object to determine whether the object is active or not active, and if the object is active, resetting the expected expiration time associated with the object; and

(f) if the object is inactive, creating a report indicating an operational failure for the inactive object.

28. The method in claim 27, further comprising creating a register key associated with the object.

29. The method in claim 27, further comprising storing one or more contexts in a memory location associated with the created object, and

correlating faults in objects in a distributed environment using the one or more contexts.