Fault tolerance for computer programs that operate over a communication network

• US 6,922,792 B2
• Filed: 10/26/2001
• Issued: 07/26/2005
• Est. Priority Date: 10/27/2000
• Status: Expired due to Term

• Current Assignee: International Business Machines Corporation
• Original Assignee: Eternal Systems, Inc.
• Inventors: Melliar-Smith, Peter M., Moser, Louise E.
• Primary Examiner(s): Baderman, Scott
• Assistant Examiner(s): LOHN, JOSHUA A
• Application Number:
  US10/053,240
• Publication Number:
  US 20020099973A1
• Time in Patent Office: 1,369 Days
• Field of Search: 714/4, 707/202
• US Class Current: 714/4.3
• CPC Class Codes: G06F 11/1471 involving logging of persistent data for recovery
• CPC Class Codes: G06F 11/1474 in transactions G06F16/20 takes precedence
• CPC Class Codes: G06F 11/1482 by means of middleware or OS functionality
• CPC Class Codes: H04L 67/1095 Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
• CPC Class Codes: Y10S 707/99953 Recoverability

Abstract

Mechanisms for a Networked Enterprise Server that provide fault tolerance for computer programs that interact with computer programs within and between enterprises over a communication network, such as the Internet or a virtual private network. Fault tolerance is provided by unifying transaction processing and object or process replication. Transaction processing is used in this invention to protect the local data and processing against faults, while replication is used to protect the processing and communication that span multiple enterprises.

Claims

1. A method for providing fault tolerance between computers of different enterprises across a communication network, comprising:

unifying transaction processing and object or process replication between computers across a communication network;

wherein a computer program operating on at least one of said computers can recover from a fault while it is communicating with a program on another of said computers across said communication network;

wherein an object or process operates in a networked mode or a transactional mode;

wherein in said transactional mode, an object or process on one computer can interact with an object or process in a local database, but not with an object or process on another computer across said communication network; and

wherein data in transactional mode is protected against faults by a transaction processing system.

2. A method as recited in claim 1, wherein said transaction processing protects local data and processing against faults.

3. A method as recited in claim 1, wherein said replication protects processing and communication across said communication network against faults.

4. A method as recited in claim 1:

wherein in said networked mode, an object or process on one computer can interact with en object or process on an another computer across said communication network; and

wherein an object or process in networked mode is protected against faults by an object or process replication system.

5. A method as recited in claim 4:

wherein an object or process operates in said networked mode by default; and

wherein in networked mode an object or process can interact freely with another object or process on the same computer, or with an object or process on another computer across said communication network.

6. A method as recited in claim 1:

wherein an object or process enters transactional mode either by explicitly initiating a transaction, or by being invoked by another object or process that is part of a transaction; and

wherein in transactional mode, an object or process cannot invoke methods of a remote object or process across said communication network, and cannot accept request messages that originate from an object or process that is not part of the transaction.

7. A method as recited in claim 6, wherein an object or process leaves transactional mode and returns to networked mode when the transaction commits or aborts.

8. A method as recited in claim 1, wherein computers of different enterprises across said communication network maintain consistent views of interactions across said communication network.

9. A method as recited in claim 1, wherein messages sent between computers across said communication network are never retracted.

10. A method as recited in claim 1, wherein a fault in a computer of one enterprise will not abort activities in a computer of another enterprise.

11. A method as recited in claim 1:

wherein roll-forward recovery is used in networked mode; and

wherein roil-back/abort recovery is used in transactional mode.

12. A method as recited in claim 11:

wherein said roll-forward recovery starts from a checkpoint and then replays messages from a message log; and

wherein messages involved in an aborted transaction are not replayed.

13. A method as recited in claim 12, wherein roll-forward recovery of one object or process does not disrupt continued operation of another object or process or of a database.

14. A method as recited in claim 13, wherein a message generated during roll-forward recovery of an object or process is detected as a duplicate message and is not processed a second time.

15. A method as recited in claim 13, wherein an object or process recovered using roll-forward recovery receives a reply from another object or process and a value from a database that is the same reply and value received during the initial operation of the object or process.

16. A method as recited in claim 1, wherein while an objector process is in transactional mode, a request received from another object or process that is not part of the same transaction is queued until the transaction commits or aborts.

17. A method as recited in claim 16, wherein recovery of an object or process restores the state of the object or process and then processes a message that was queued waiting for a transaction to commit or abort.

18. A method as recited in 17, wherein a message for a current transaction is processed but a message of an enclosing transaction or no transaction remains queued.

19. A method for providing fault tolerance between computers of different enterprises across a communication network, comprising:

unifying transaction processing and object or process or process replication between computers across a communication network;

wherein a computer program operating on at least one of said computers can recover from a fault while it is communicating with a program on another of said computers across said communication network;

wherein an object or process or process operates in a networked mode or a transactional mode;

wherein in said transactional mode, an object or process on one computer can interact with an object or process in a local database, but not with an object or process on another computer across said communication network; and

wherein data in transactional mode is protected against faults by a transaction processing system.

20. A method as recited in claim 19, wherein said transaction processing protects local data and processing against faults.

21. A method as recited in claim 19, wherein said replication protects processing and communication across said communication network against faults.

22. A method as recited in claim 19:

wherein in said networked mode, an object or process or process on one computer can interact with an object or process on an another computer across said communication network; and

wherein an object or process in networked mode is protected against faults by an object or process replication system.

23. A method as recited in claim 22:

wherein an object or process operates in said networked mode by default; and

wherein in networked mode an object or process can interact freely with another object or process on the same computer, or with an object or process on another computer across said communication network.

24. A method as recited in claim 19:

wherein an object or process enters transactional mode either by explicitly initiating a transaction, or by being invoked by another object or process that is part of a transaction; and

wherein in transactional mode, an object or process cannot invoke methods of a remote object or process across said communication network, and cannot accept request messages that originate from an object or process that is not part of the transaction.

25. A method as recited in claim 24, wherein an object or process leaves transactional mode and returns to networked mode when the transaction commits or aborts.

26. A method as recited in claim 19, wherein computers of different enterprises across said communication network maintain consistent views of interactions across said communication network.

27. A method as recited in claim 19, wherein messages sent between computers across said communication network are never retracted.

28. A method as recited in claim 19, wherein a fault in a computer of one enterprise will not abort activities in a computer of another enterprise.

29. A method as recited in claim 19:

wherein roll-forward recovery is used in networked mode; and

wherein roll-back/abort recovery is used in transactional mode.

30. A method as recited in claim 29:

wherein said roll-forward recovery starts from a checkpoint and then replays messages from a message log; and

wherein messages Involved in an aborted transaction are not replayed.

31. A method as recited in claim 30, wherein roll-forward recovery of one object or process does not disrupt continued operation of another object or process or of a database.

32. A method as recited in claim 31, wherein a message generated during roll-forward recovery of an object or process is detected as a duplicate message and is not processed a second time.

33. A method as recited in claim 31, wherein an object or process recovered using roll-forward recovery receives a reply from another object or process and a value from a database that is the same reply and value received during the initial operation of the object or process.

34. A method as recited in claim 19, wherein while en object or process is in transactional mode, a request received from another object or process that is not part of the same transaction is queued until the transaction commits or aborts.

35. A method as recited in claim 34, wherein recovery of an object or process restores the state of the object or process and then processes a message that was queued waiting for a transaction to commit or abort.

36. A method as recited in 35, wherein a message for a current transaction is processed but a message of an enclosing transaction or no transaction remains queued.

37. A method for providing fault tolerance between computers of different enterprises across a communication network, comprising:

unifying transaction processing and object or process replication between computers across a communication network;

wherein a computer program operating on at least one of said computers can recover from a fault while it is communicating with a program on another of said computers across said communication network;

wherein an object or process operates in a networked mode or a transactional mode;

wherein in said networked mode, an object or process on one computer can interact with an object or process on an another computer across said communication network;

wherein an object or process in networked mode is protected against faults by an object or process replication system;

wherein in said transactional mode, an object or process on one computer can interact with an object or process in a local database, but not with an object or process on another computer across said communication network; and

wherein data in transactional mode is protected against faults by a transaction processing system.

38. A method as recited in claim 37, wherein said transaction processing protects local data and processing against faults.

39. A method as recited in claim 37, wherein said replication protects processing and communication across said communication network against faults.

40. A method as recited in claim 37:

wherein an object or process operates in said networked mode by default; and

wherein in networked mode an object or process can interact freely with another object or process on the same computer, or with an object or process on another computer across said communication network.

41. A method as recited in claim 37:

wherein an object or process enters transactional mode either by explicitly initiating a transaction, or by being invoked by another object or process that is part of a transaction; and

wherein in transactional mode, an object or process cannot invoke methods of a remote object or process across said communication network, and cannot accept request messages that originate from an object or process that is not part of the transaction.

42. A method as recited in claim 41, wherein an object or process leaves transactional mode and returns to networked mode when the transaction commits or aborts.

43. A method as recited in claim 37, wherein computers of different enterprises across said communication network maintain consistent views of interactions across said communication network.

44. A method as recited in claim 37, wherein messages sent between computers across said communication network are never retracted.

45. A method as recited in claim 37, wherein a fault in a computer of one enterprise will not abort activities in a computer of another enterprise.

46. A method as recited in claim 37:

wherein roll-forward recovery is used in networked mode; and

wherein roll-back/abort recovery is used in transactional mode.

47. A method as recited in claim 46:

wherein said roll-forward recovery starts from a checkpoint and then replays messages from a message log; and

wherein messages involved in an aborted transaction are not replayed.

48. A method as recited in claim 47, wherein roll-forward recovery of one object or process does not disrupt continued operation of another object or process or of a database.

49. A method as recited in claim 48, wherein a message generated during roll-forward recovery of an object or process is detected as a duplicate message and is not processed a second time.

50. A method as recited in claim 48, wherein an object or process recovered using roll-forward recovery receives a reply from another object or process and a value from a database that is the same reply and value received during the initial operation of the object or process.

51. A method as recited in claim 37, wherein while an object or process is in transactional mode, a request received from another object or process that is not part of the same transaction is queued until the transaction commits or aborts.

52. A method as recited in claim 51, wherein recovery of an object or process restores the state of the object or process and then processes a message that was queued waiting for a transaction to commit or abort.

53. A method as recited in 52, wherein a message for a current transaction is processed but a message of an enclosing transaction or no transaction remains queued.

54. A method for providing fault tolerance between computers of different enterprises across a communication network, comprising:

unifying transaction processing and object or process replication between computers across a communication network;

wherein a computer program operating on at least one of said computers can recover from a fault while it Is communicating with a program on another of said computers across said communication network;

wherein an object or process operates in a networked mode or a transactional mode;

wherein in said transactional mode, an object or process on one computer can interact with an object or process in a local database, but not with an object or process on another computer across said communication network; and

wherein data in transactional mode is protected against faults by a transaction processing system.

55. A method as recited in claim 54, wherein said transaction processing protects local data and processing against faults.

56. A method as recited in claim 54, wherein said replication protects processing and communication across said communication network against faults.

57. A method as recited in claim 54:

wherein in said networked mode, an object or process on one computer can interact with an object or process on an another computer across said communication network; and

wherein an object or process in networked mode is protected against faults by an object or process replication system.

58. A method as recited in claim 57:

wherein an object or process operates in said networked mode by default; and

wherein in networked mode an object or process can interact freely with another object or process on the same computer, or with an object or process on another computer across said communication network.

59. A method as recited in claim 54:

wherein an object or process enters transactional mode either by explicitly initiating a transaction, or by being invoked by another object or process that is part of a transaction; and

wherein in transactional mode, an object or process cannot invoke methods of a remote object or process across said communication network, and cannot accept request messages that originate from an object or process that is not part of the transaction.

60. A method as recited in claim 59, wherein an object or process leaves transactional mode and returns to networked mode when the transaction commits or aborts.

61. A method as recited in claim 54, wherein computers of different enterprises across said communication network maintain consistent views of interactions across said communication network.

62. A method as recited in claim 54, wherein messages sent between computers across said communication network are never retracted.

63. A method as recited in claim 54, wherein a fault in a computer of one enterprise will not abort activities in a computer of another enterprise.

64. A method as recited in claim 54:

wherein roll-forward recovery is used in networked mode; and

wherein roll-back/abort recovery is used in transactional mode.

65. A method as recited in claim 64:

wherein said roll-forward recovery starts from a checkpoint and then replays messages from a message log; and

wherein messages involved in an aborted transaction are not replayed.

66. A method as recited in claim 65, wherein roll-forward recovery of one object or process does not disrupt continued operation of another object or process or of a database.

67. A method as recited in claim 66, wherein a message generated during roll-forward recovery of an object or process is detected as a duplicate message and is not processed a second time.

68. A method as recited in claim 66, wherein an object or process recovered using roll-forward recovery receives a reply from another object or process and a value from a database that is the same reply and value received during the initial operation of the object or process.

69. A method as recited in claim 54, wherein while an object or process is in transactional mode, a request received from another object or process that is not part of the same transaction is queued until the transaction commits or aborts.

70. A method as recited in claim 69, wherein recovery of an object or process restores the state of the object or process and then processes a message that was queued waiting for a transaction to commit or abort.

71. A method as recited in 70, wherein a message for a current transaction is processed but a message of an enclosing transaction or no transaction remains queued.

72. A method for providing fault tolerance between computers of different enterprises across a communication network, comprising:

unifying transaction processing and object or process replication between computers across a communication network;

wherein a computer program operating on at least one of said computers can recover from a fault while it is communicating with a program on another of said computers across said communication network;

wherein an object or process operates in a networked mode or a transactional mode;

wherein roll-forward recovery is used in networked mode;

wherein roll-back/abort recovery is used in transactional mode;

wherein in said transactional mode, an object or process on one computer can interact with an object or process in a local database, but not with an object or process on another computer across said communication network; and

wherein data in transactional mode is protected against faults by a transaction processing system.

73. A method as recited in claim 72, wherein said transaction processing protects local data and processing against faults.

74. A method as recited in claim 72, wherein said replication protects processing and communication across said communication network against faults.

75. A method as recited in claim 72:

wherein in said networked mode, an object or process on one computer can interact with an object or process on an another computer across said communication network; and

wherein an object or process in networked mode is protected against faults by an object or process replication system.

76. A method as recited in claim 75:

wherein an object or process operates in said networked mode by default; and

wherein in networked mode an object or process can interact freely with another object or process on the same computer, or with an object or process on another computer across said communication network.

77. A method as recited in claim 72:

wherein an object or process enters transactional mode either by explicitly initiating a transaction, or by being invoked by another object or process that is part of a transaction; and

wherein in transactional mode, an object or process cannot invoke methods of a remote object or process across said communication network, and cannot accept request messages that originate from an object or process that is not part of the transaction.

78. A method as recited in claim 77, wherein an object or process leaves transactional mode and returns to networked mode when the transaction commits or aborts.

79. A method as recited in claim 72, wherein computers of different enterprises across said communication network maintain consistent views of interactions across said communication network.

80. A method as recited in claim 72, wherein messages sent between computers across said communication network are never retracted.

81. A method as recited in claim 72, wherein a fault in a computer of one enterprise will not abort activities in a computer of another enterprise.

82. A method as recited in claim 72:

wherein said roll-forward recovery starts from a checkpoint and then replays messages from a message log; and

wherein messages involved in an aborted transaction are not replayed.

83. A method as recited in claim 82, wherein roll-forward recovery of one object or process does not disrupt continued operation of another object or process or of a database.

84. A method as recited in claim 83, wherein a message generated during roll-forward recovery of an object or process is detected as a duplicate message and is not processed a second time.

85. A method as recited in claim 83, wherein an object or process recovered using roll-forward recovery receives a reply from another object or process and a value from a database that is the same reply and value received during the initial operation of the object or process.

86. A method as recited in claim 72, wherein while an object or process is in transactional mode, a request received from another object or process that is not part of the same transaction is queued until the transaction commits or aborts.

87. A method as recited in claim 86, wherein recovery of an object or process restores the state of the object or process and then processes a message that was queued waiting for a transaction to commit or abort.

88. A method as recited in 87, wherein a message for a current transaction is processed but a message of an enclosing transaction or no transaction remains queued.

89. A method for providing fault tolerance between computers of different enterprises across a communication network, comprising:

unifying transaction processing and object or process replication between computers across a communication network;

wherein a computer program operating on at least one of said computers can recover from a fault while it is communicating with a program on another of said computers across said communication network;

wherein an object or process operates in a networked mode or a transactional mode;

wherein while an object or process is in transactional mode, a request received from another object or process that is not part of the same transaction is queued until the transaction commits or aborts;

wherein in said transactional mode, an object or process on one computer can interact with an object or process in a local database, but not with an object or process on another computer across said communication network; and

wherein data in transactional mode is protected against faults by a transaction processing system.

90. A method as recited in claim 89, wherein said transaction processing protects local data and processing against faults.

91. A method as recited in claim 89, wherein said replication protects processing and communication across said communication network against faults.

92. A method as recited in claim 89:

wherein in said networked mode, an object or process on one computer can interact with an object or process on an another computer across said communication network; and

wherein an object or process in networked mode is protected against faults by an object or process replication system.

93. A method as recited in claim 92:

wherein an object or process operates in said networked mode by default; and

wherein in networked mode an object or process can interact freely with another object or process on the same computer, or with an object or process on another computer across said communication network.

94. A method as recited in claim 89:

wherein an object or process enters transactional mode either by explicitly initiating a transaction, or by being invoked by another object or process that is part of a transaction; and

wherein in transactional mode, an object or process cannot invoke methods of a remote object or process across said communication network, and cannot accept request messages that originate from an object or process that is not part of the transaction.

95. A method as recited in claim 94, wherein an object or process leaves transactional mode and returns to networked mode when the transaction commits or aborts.

96. A method as recited in claim 89, wherein computers of different enterprises across said communication network maintain consistent views of interactions across said communication network.

97. A method as recited in claim 89, wherein messages sent between computers across said communication network are never retracted.

98. A method as recited in claim 89, wherein a fault in a computer of one enterprise will not abort activities in a computer of another enterprise.

99. A method as recited in claim 89:

wherein roll-forward recovery is used in networked mode; and

wherein roll-back/abort recovery is used in transactional mode.

100. A method as recited in claim 99:

wherein said roll-forward recovery starts from a checkpoint and then replays messages from a message log; and

wherein messages involved in an aborted transaction are not replayed.

101. A method as recited in claim 100, wherein roll-forward recovery of one object or process does not disrupt continued operation of another object or process or of a database.

102. A method as recited in claim 101, wherein a message generated during roll-forward recovery of an object or process is detected as a duplicate message and is not processed a second time.

103. A method as recited in claim 100, wherein an object or process recovered using roll-forward recovery receives a reply from another object or process and a value from a database that is the same reply and value received during the initial operation of the object or process.

104. A method as recited in claim 89, wherein recovery of an object or process restores the state of the object or process and then processes a message that was queued waiting for a transaction to commit or abort.

105. A method as recited in 104, wherein a message for a current transaction is processed but a message of an enclosing transaction or no transaction remains queued.