Method for matching distributed transactions and machine-readable recording medium with method programs

• US 6,332,160 B1
• Filed: 06/25/1998
• Issued: 12/18/2001
• Est. Priority Date: 06/27/1997
• Status: Expired due to Term

• Current Assignee: NEC Corporation
• Original Assignee: NEC Corporation
• Inventors: Tabuchi, Masahiro
• Primary Examiner(s): Maung, Zarni
• Assistant Examiner(s): Cardone, Jason D.
• Application Number:
  US09/104,356
• Time in Patent Office: 1,272 Days
• Field of Search: 709/205, 709/213, 709/224, 709/225, 709/228, 709/246, 709/204, 709/315, 709/317, 711/147, 711/150, 711/158, 345/329, 345/330, 345/331, 707/3, 707/6, 707/10, 714/4, 714/15, 714/48
• US Class Current: 709/224
• CPC Class Codes: H04L 67/10 in which an application is distributed across nodes in the network software deployment G06F8/60; multiprogramming arrangements G06F9/46
• CPC Class Codes: H04L 69/329 in the application layer [OSI layer 7]
• CPC Class Codes: H04L 69/40 for recovering from a failure of a protocol instance or entity, e.g. service redundancy protocols, protocol state redundancy or protocol service redirection management of faults, events, alarms or notifications in data switching networks H04L41/06
• CPC Class Codes: H04L 9/40 Network security protocols

Abstract

A method is presented of matching distributed transactions from a plurality of clients working cooperatively in a network-based information system, so that semantics conflicts submitted by user applications are resolved for each network application in the network server. Transactions manager 122 in the network server 100 executes parallel processing of transactions submitted by clients 200. Semantics conflict detection section 111 in an network application 110 in the network server 100 inspects for conflicts. When an accessing conflict arises among a number of clients 200, the semantics conflict detection section 111 forwards a processing routine having a resolving method consistent with the contents of the semantics conflict to the transactions manager 122, which executes the processing routine to resolve the semantics conflict in transactions.

Claims

1. A method for matching transactions in a distributed network system servicing a plurality of clients connected through a network server comprising a transactions manager, a transaction conflict detection section and a plurality of network applications, each network application comprising a semantics conflict detection section specific to a task, comprising:

forwarding a transaction generated by a change-data operation requested by a user application to said transactions manager;

recording said transaction in a memory device of said network server and preparing an execution thread for each received transaction to process a plurality of transactions in parallel;

inspecting said transaction for accessing conflicts with respect to a group of data common to other transactions by using said transaction conflict detection section;

requesting network applications to inspect for semantics conflicts in access-conflicting transactions by a using respective semantics conflict detections section;

comparing access-conflicting transactions to detect a semantics conflict by using a respective semantics conflict detection section in each network application;

when no semantics conflict is detected, continuing execution of said transaction in said transactions manager;

when a semantics conflict is detected, receiving in said transactions manager, from a semantics conflict detection section, an address of a processing routine having a method consistent with contents of said semantics conflict for resolving said semantics conflict, and executing said processing routine in said transactions manager, thereby resolving said semantics conflict.

2. The method according to claim 1, wherein, when a semantics conflict in access-conflicting transactions relates to a value change of a common attribute in a common group of data, a network application forwards an address of a processing routine to execute only those transactions whose change values exceed a pre-determined difference range of values or an address of a processing routine to execute transactions in a sequence of arrival of access-conflicting transactions.

3. The method according to claim 2, further comprising pre-selecting processing routines for each network application and for each type of semantics conflicts from a plurality of processing routines for resolving semantics conflicts.

4. The method according to claim 2, wherein said transactions manager bases a decision of whether a transaction being received from an on-line client conflicts with transactions received from other clients by detecting a wait-status for a locked common group of data.

5. The method according to claim 1, further comprising pre-selecting processing routines for each network application and for each type of semantics conflicts from a plurality of processing routines for resolving semantics conflicts.

6. The method according to claim 5, wherein said transactions manager bases a decision of whether a transaction being received from an on-line client conflicts with transactions received from other clients by detecting a wait-status for a locked common group of data.

7. The method according to claim 1, wherein said transactions manager bases a decision of whether a transaction being received from an on-line client conflicts with transactions received from other clients by detecting a wait-status for a locked common group of data.

8. A method for matching transactions in a distributed network system serving a plurality of clients connected on a network, comprising:

forwarding a transaction generated by a change-data operation requested by a user application running on one of the client computer to a transactions manager of a corresponding network application on a network server;

recording said transaction in a memory device of said network server and preparing an execution thereof for each received transaction to process a plurality of transactions in parallel;

inspecting said transaction for accessing conflicts with respect to a group of data common to other transactions by using a transaction conflict detection section of the network application on the server;

requesting network applications running on the network server to compare access-conflicting transactions to detect a semantics conflict by using a respective semantics conflict detection section of the respective network application;

inspecting said access-conflicting transactions for semantics conflicts by using a respective semantics conflict detection section in each network application;

continuing execution of said transaction in said transactions manager when there is no semantics conflict;

but, when there is a semantics conflict,

receiving in said transactions manager, from a semantics conflict detection section, an address of a processing routine having a method consistent with contents of said semantics conflict for resolving said semantics conflict; and

executing said processing routine in said transactions manager, thereby resolving said semantics conflict.

9. The method of claim 8, wherein, when a semantics conflict in access-conflicting transactions relates to a value change of a common attribute in a common group of data, one of the network applications forwards an address of a processing routine to execute only those transactions whose change values exceed a pre-determined difference range of values or an address of a processing routine to execute transactions in a sequence of arrival of access-conflicting transactions.

10. The method of claim 9, further comprising pre-selecting processing routines for each network application and for each type of semantics conflicts from a plurality of processing routines for resolving semantics conflicts.

11. The method of claim 9, wherein said transactions manager bases a decision of whether a transaction being received from an on-line client conflicts with transactions received from other clients by detecting a wait-status for a locked common group of data.

12. The method of claim 8, further comprising pre-selecting processing routines for each network application and for each type of semantics conflicts from a plurality of processing routines for resolving semantics conflicts.

13. The method of claim 12, wherein said transactions manager bases a decision of whether a transaction being received from an on-line client conflicts with transactions received from other clients by detecting a wait-status for a locked common group of data.

14. The method of claim 8, wherein said transactions manager bases a decision of whether a transaction being received from an on-line client conflicts with transactions received from other clients by detecting a wait-status for a locked common group of data.

15. A method for matching transactions in a distributed network system serving a plurality of clients connected through a network server having network applications, comprising:

receiving a transaction of a data-change operation requested by a user application in a transactions manager of said network server;

recording said transaction in a memory device of said network server and preparing an execution thread for each received transaction to process a plurality of transactions in parallel;

comparing, using a semantics conflict detection section in a network application, a received transaction with other transactions received from other clients to detect a semantics conflict between said received transaction and said other transactions;

when there is no semantics conflict, executing said received transaction in said transactions manager according to said data-change operation; and

when there is a semantics conflict, forwarding an address of a processing routine for resolving said semantics conflict from said semantics conflict detection section to said transactions manager and executing said processing routine by said transactions manager to resolve said semantics conflict.

16. The method according to claim 15, wherein said processing routine is related to a detected semantics conflict.

17. The method according to claim 15, wherein said processing routing is not associated with a characteristic of said data.

18. A method for matching distributed transactions in a distributed network system serving a plurality of clients connected through a network server, comprising:

receiving a transaction generated by a change-data operation requested by a user application in a transactions manager of said network server;

recording said transaction in a memory device of said network server and preparing an execution thread for each received transaction to process a plurality of transactions in parallel;

comparing, using a semantics conflict detection section in a network application, a received transaction with other transactions received and recorded in a reception log from other clients to detect a semantics conflict between said received transaction and said other transactions;

executing said received transaction by said transactions manager when there is no semantics conflict; and

forwarding an address of a processing routine for resolving a semantics conflict from said semantics conflict detection section to said transactions manager when there is a semantics conflict and executing said processing routine by said transactions manager, thereby resolving said semantics conflict.

19. The method according to claim 18, wherein, when a transaction is received in said network server from a reconnected client, an inspection range for semantics conflicts of said transaction is restricted to a portion of transactions received from other clients and recorded in a reception log.

20. A machine readable recording medium comprising a program for matching transactions in a distributed network system serving a plurality of clients connected through a network server, the program comprising:

forwarding a transaction generated by a change-data operation requested by a user application to said transactions manager;

recording said transaction in a memory device of said network server and preparing an execution thread for each received transaction to process a plurality of transactions in parallel;

inspecting said transaction for accessing conflicts with respect to a group of data common to other transactions by using said transaction conflict detection section;

requesting network applications to inspect for semantics conflicts in access-conflicting transactions by using a respective semantics conflict detection section;

comparing said access-conflicting transactions to detect semantics conflicts by using a respective semantics conflict detection section in each network application;

continuing execution of said transaction in said transactions manager when there is no semantics conflict;

but, when there is a semantics conflict,

receiving in said transactions manager an address of a processing routine having a method for matching transactions consistent with contents of semantics conflicts, from said semantics conflict detection section, when there is a semantics conflict; and

executing said processing routine in said transactions manager, thereby resolving said semantics conflict.