Tracking data throughout an asset lifecycle
US-12166894-B2 · Dec 10, 2024 · US
US10740166B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-10740166-B2 |
| Application number | US-201715849397-A |
| Country | US |
| Kind code | B2 |
| Filing date | Dec 20, 2017 |
| Priority date | Jan 12, 2012 |
| Publication date | Aug 11, 2020 |
| Grant date | Aug 11, 2020 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
Execution of a program in a plurality of threads is monitored. Responsive to identifying an exception triggered by the program execution in a first of the plurality of threads, a data collector can be dynamically created for the exception. The data collector can be configured to collect data exclusively relevant to the program execution in the first thread.
Opening claim text (preview).
The invention claimed is: 1. A method comprising: monitoring execution of a program in a plurality of threads; responsive to identifying an exception triggered by the program execution in a first of the plurality of threads, dynamically creating a data collector for the exception, the data collector configured to collect data exclusively relevant to the program execution in the first thread; prior to a function of a first failure data capture system being initiated, initiating the data collector to collect the data exclusively relevant to the program execution in the first thread; collecting, using the data collector, the data exclusively relevant to the program execution in the first thread; and outputting the data exclusively relevant to the program execution in the first thread. 2. The method of claim 1 , wherein the initiating the data collector to collect the data exclusively relevant to the program execution in the first thread comprises initiating the data collector once for a corresponding initiation of the first failure data capture system. 3. The method of claim 2 , wherein the initiating the data collector to collect the data exclusively relevant to the program execution in the first thread comprises limiting the initiation of the corresponding first failure data capture system to a single instance of the first failure data capture system for the identified exception. 4. The method of claim 1 , wherein the initiating the data collector to collect the data exclusively relevant to the program execution in the first thread comprises initiating the data collector to collect the data for an instance of a method in a call stack nearest the exception in the call stack, wherein the exception is an original exception triggered by the program execution in the first of the plurality of threads. 5. The method of claim 1 , further comprising: registering the data collector with a first failure data capture system as an exception collector in an exception collector list; and responsive to outputting the data exclusively relevant to the program execution in the first thread, de-registering the data collector with the first failure data capture system by removing the data collector from the exception collector list. 6. A system comprising: a processor configured to initiate executable operations comprising: monitoring execution of a program in a plurality of threads; responsive to identifying an exception triggered by the program execution in a first of the plurality of threads, dynamically creating a data collector for the exception, the data collector configured to collect data exclusively relevant to the program execution in the first thread; prior to a function of a first failure data capture system being initiated, initiating the data collector to collect the data exclusively relevant to the program execution in the first thread; collecting, using the data collector, the data exclusively relevant to the program execution in the first thread; and outputting the data exclusively relevant to the program execution in the first thread. 7. The system of claim 6 , wherein the initiating the data collector to collect the data exclusively relevant to the program execution in the first thread comprises the processor initiating the data collector once for a corresponding initiation of the first failure data capture system. 8. The system of claim 7 , wherein the initiating the data collector to collect the data exclusively relevant to the program execution in the first thread comprises the processor limiting the initiation of the corresponding first failure data capture system to a single instance of the first failure data capture system for the identified exception. 9. The system of claim 6 , wherein the initiating the data collector to collect the data exclusively relevant to the program execution in the first thread comprises the processor initiating the data collector to collect the data for an instance of a method in a call stack nearest the exception in the call stack, wherein the exception is an original exception triggered by the program execution in the first of the plurality of threads. 10. The system of claim 6 , wherein the processor is further configured to initiate executable operations comprising: registering the data collector with a first failure data capture system as an exception collector in an exception collector list; and responsive to outputting the data exclusively relevant to the program execution in the first thread, de-registering the data collector with the first failure data capture system by removing the data collector from the exception collector list. 11. A computer program product, comprising: a computer-readable storage medium having program code stored thereon, wherein the computer-readable storage medium is not a transitory, propagating signal per se, the program code executable by a data processing system to initiate operations including: monitoring execution of the program in a plurality of threads; and responsive to identifying an exception triggered by the program execution in a first of the plurality of threads, dynamically creating a data collector for the exception, the data collector configured to collect data exclusively relevant to the program execution in the first thread; prior to a function of a first failure data capture system being initiated, initiating the data collector to collect the data exclusively relevant to the program execution in the first thread; collecting, using the data collector, the data exclusively relevant to the program execution in the first thread; and outputting the data exclusively relevant to the program execution in the first thread. 12. The computer program product of claim 11 , wherein the initiating the data collector to collect the data exclusively relevant to the program execution in the first thread comprises initiating the data collector once for a corresponding initiation of the first failure data capture system. 13. The computer program product of claim 12 , wherein the initiating the data collector to collect the data exclusively relevant to the program execution in the first thread comprises limiting the initiation of the corresponding first failure data capture system to a single instance of the first failure data capture system for the identified exception. 14. The computer program product of claim 11 , wherein the initiating the data collector to collect the data exclusively relevant to the program execution in the first thread comprises initiating the data collector to collect the data for an instance of a method in a call stack nearest the exception in the call stack, wherein the exception is an original exception triggered by the program execution in the first of the plurality of threads. 15. The computer program product of claim 11 , wherein the program code is executable by the data processing system to initiate operations further comprising: registering the data collector with a first failure data capture system as an exception collector in an exception collector list; and responsive to outputting the data exclusively relevant to the program execution in the first thread, de-registering the data collector with the first failure data capture system by removing the data collector from the exception collector list.
Data logging (G06F11/14, G06F11/2205 take precedence) · CPC title
Monitoring of software · CPC title
for parallel or distributed programming · CPC title
Storage of error reports, e.g. persistent data storage, storage using memory protection · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.