Method and system for providing post-mortem service level debugging

• US 8,201,151 B2
• Filed: 12/20/2007
• Issued: 06/12/2012
• Est. Priority Date: 12/20/2007
• Status: Expired due to Fees

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Barker, Kevin Spencer, Derdak, Stefan Georg, Mathrubutham, Ramani, Mei, Xiaochun, Miller, Aaron Higuchi, Pollinger, Thomas, Tsang, Juliana Hing Sze
• Primary Examiner(s): Das, Chameli
• Application Number:
  US11/960,703
• Publication Number:
  US 20090164978A1
• Time in Patent Office: 1,636 Days
• Field of Search: 717/128, 717/129
• US Class Current: 717/129
• CPC Class Codes: G06F 11/3636 by tracing the execution of the program

Abstract

A computer program product comprises a computer useable medium. The computer useable medium has a computer readable program such that when the computer readable medium is executed on a computer, the computer is caused to configure an interceptor at a service invocation point corresponding to a component service of a software application. Further, the computer is caused to record, at the interceptor, data in a trace file. The data is associated with a service invocation at the service invocation point. Finally, the computer is caused to provide the trace file to a service level debugger that navigates through the trace file.

Claims

1. A computer program product comprising a computer useable storage medium having a computer readable program stored thereon, wherein the computer readable program when executed on a computer causes the computer to:

configure an interceptor at a service invocation point corresponding to a component service of a software application;

record, at the interceptor, data in a trace file, the data being associated with a service invocation at the service invocation point;

provide the trace file to a service level debugger that navigates through the trace file;

pause the service invocation at a break point;

update the service level debugger with a live invocation context;

receive a modified invocation context from the service level debugger to update a runtime engine; and

continue execution until the service level debugger reaches a subsequent break point.

2. The computer program product of claim 1, wherein the service level debugger is operable without a server on which the software application is stored being configured in a debugging mode.

3. The computer program product of claim 1, wherein the software application is built on top of a Service Oriented Architecture.

4. A method comprising:

configuring, with a processor, an interceptor at a service invocation point corresponding to a component service of a software application;

recording, at the interceptor, data in a trace file, the data being associated with a service invocation at the service invocation point;

providing the trace file to a service level debugger that navigates through the trace file;

pausing the service invocation at a break point;

updating the service level debugger with a live invocation context;

receiving a modified invocation context from the service level debugger to update a runtime engine; and

continuing execution until the service level debugger reaches a subsequent break point.

5. The method of claim 4, wherein the service level debugger is operable without a server on which the software application is stored being configured in a debugging mode.

6. The method of claim 4, wherein the software application is built on top of a Service Oriented Architecture.

7. A system having a processor comprising:

an interceptor that records, in a trace file, data associated with a service invocation, the interceptor located at a service invocation point corresponding to a component service of a software application, the service invocation being at the service invocation point;

a service level debugger that navigates through the trace file; and

a component service that pauses the service invocation at a break point, updates the service level debugger with a live invocation context, receives a modified invocation context from the service level debugger to update a runtime engine, and continues execution until the service level debugger reaches a subsequent break point.

8. The system of claim 7, wherein the service level debugger is operable without a server on which the software application is stored being configured in a debugging mode.