Legal claims defining the scope of protection, as filed with the USPTO.
1. A multiprocessing transaction recovery manager, operable with a transactional application manager and a resource manager, comprising: a memory allocated to store a threadsafety indicator for receiving and storing a positive threadsafety data and a non-positive threadsafety data of at least one transactional component managed by one of said transactional application manager and said resource manager, wherein the positive threadsafety data confirms the multiprocessing recovery manager has no affinity to an application thread and the non-positive threadsafety data has affinity to the application thread; a commit protocol component for performing commit processing for said at least one transactional component; and a thread selector responsive to the positive threadsafety data for selecting a single thread for said commit processing to be performed by said commit protocol component, wherein said thread selector is further operable to select plural threads for said commit processing to be performed by said commit protocol component responsive to the non-positive threadsafety data and thread selector is further operable to select minimal plural threads for said commit processing to be performed by said commit protocol component responsive to a mixture of the positive threadsafety data and the non-positive threadsafety data stored for plural said transactional components by grouping threadsafe transactional components for said commit processing under a single thread.
2. The multiprocessing transaction recovery manager of claim 1 , wherein said resource manager is a database management system.
3. The multiprocessing transaction recovery manager of claim 1 , wherein the commit protocol component is operable to perform two-phase commit processing.
4. A method of operating a multiprocessing transaction recovery manager, in communication with a transactional application manager and a resource manager, comprising the steps of: receiving and storing, by a threadsafety indicator, a positive threadsafety data and a non-positive threadsafety data of at least one transactional component managed by one of said transactional application manager and said resource manager, wherein the positive threadsafety data confirms the multiprocessing recovery manager has no affinity to an application thread and the non-positive threadsafety data has affinity to the application thread; performing, by a commit protocol component, commit processing for said at least one transactional component; responsive to the positive threadsafety data, selecting, by a thread selector, a single thread for said commit processing to be performed by said commit protocol component; selecting, by said thread selector, plural threads for said commit processing to be performed by said commit protocol component responsive to the non-positive threadsafety data; and selecting, by said thread selector, minimal plural threads for said commit processing to be performed by said commit protocol component responsive to a mixture of the positive threadsafety data and the non-positive threadsafety data stored for plural said transactional components by grouping threadsafe transactional components for said commit processing under a single thread.
5. The method of claim 4 , wherein said resource manager is a database management system.
6. The method of claim 4 , wherein the commit protocol component is operable to perform two-phase commit processing.
7. A computer program product for managing the application assignments to processing threads, the computer program product comprising: a computer readable storage device; first program instructions to receive, by a threadsafety indicator, a positive threadsafety data and a non-positive threadsafety data of at least one transactional component, wherein the positive threadsafety data and the non-positive threadsafety data is managed by one of the transactional application manager and the resource manager, wherein the positive threadsafety data confirms a recovery manager has no affinity to an application thread and the non-positive threadsafety data has affinity to the application thread; second program instructions to perform commit processing, by a commit protocol component, for the at least one transactional component; third program instructions to select, by a thread selector, a single thread for commit processing to be performed by the commit protocol component, based on the positive threadsafety data; fourth program instructions to select plural threads for the commit processing to be performed by the commit protocol component responsive to the non-positive threadsafety data; and fifth program instructions to select minimal plural threads for said commit processing to be performed by the commit protocol component responsive to a mixture of the positive threadsafety data and the non-positive threadsafety data stored for plural said transactional components by grouping threadsafe transactional components for said commit processing under a single thread, wherein the first, second, third, fourth and fifth program instructions are stored on the computer readable storage device, and the computer readable storage device is not a signal per se.
8. The computer program product of claim 7 , wherein the resource manager is a database management system.
9. The computer program product of claim 7 , wherein the commit protocol component is operable to perform two-phase commit processing.
Unknown
July 30, 2013
Browse 5M+ US patents with plain-English claim translations and AI-generated analysis.