CORRELATING QUERIES ISSUED BY APPLICATIONS WITH THEIR SOURCE LINES AND ANALYZING APPLICATIONS FOR PROBLEM DETERMINATION AND WHERE USED ANALYSIS

• US 20100332473A1
• Filed: 06/30/2009
• Published: 12/30/2010
• Est. Priority Date: 06/30/2009
• Status: Active Grant

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Surange, Sonali, Brodsky, Stephen Andrew, Kwong, Michael Yiupun, Courtois, Zeus Orion, Jacopi, Tom William, Leung, Tony Kai-chi
• Granted Patent: US 9,020,939 B2
• Time in Patent Office: Days
• US Class Current: 707/736
• CPC Class Codes: G06F 11/3612 by runtime analysis performance monitoring G06F11/3466
• CPC Class Codes: G06F 11/3624 by performing operations on the source code, e.g. via a compiler
• CPC Class Codes: G06F 11/3636 by tracing the execution of the program
• CPC Class Codes: G06F 16/2455 Query execution
• CPC Class Codes: G06F 8/75 Structural analysis for program understanding
• CPC Class Codes: G06F 9/547 Remote procedure calls [RPC]; Web services

Abstract

Provided are techniques for invoking with a processor executing on a computer a source code parser to obtain source information that includes a first location of an Application Programming Interface (API) call and parameters of the API call in source code of a client application, where the parameters the API call do not include query text for a query that is to be used to access a database; examining a stack trace to determine a second location of the API call in the stack trace; and deriving the query of the API call and a third location of the query in the source code by identifying the query in the stack trace at the location of the API call in the stack trace.

Claims

1. A method, comprising:

invoking with a processor executing on a computer a source code parser to obtain source information that includes a first location of an Application Programming Interface (API) call and parameters of the API call in source code of a client application, where the parameters the API call do not include query text for a query that is to be used to access a database;

examining a stack trace to determine a second location of the API call in the stack trace; and

deriving the query of the API call and a third location of the query in the source code by identifying the query in the stack trace at the first location of the API call in the stack trace.

2. The method of claim 1, further comprising:

in response to deriving the query of the API call,

obtaining the query text of the query;

invoking a query parser to parse the query to identify one or more tables and one or more columns used by the query;

storing correlator results for the API call that identify a source file of the client application, the first location of the API call in the source code, parameters of the API call, and database objects which the query makes use of, wherein one of the parameters is the query text of the query; and

performing analysis using the correlator results.

3. The method of claim 2, further comprising:

retrieving the correlator results; and

generating user interface views using the correlator results.

4. The method of claim 3, wherein the user interface views provide at least one of:

a view showing the query in the database and the query in the source code, a view showing database schemas and database objects that the query uses, a view showing queries per class, a view showing the queries used by each database object in the database, a view showing how queries are run, a view for exporting data, and a view showing performance information of execution count and execution time for each of the queries.

5. A method, comprising:

setting, with a processor executing on a computer, one or more breakpoints in source code of a client application based on locations of Application Programming Interface (API) calls in the source code; and

while running the client application through a debugger, upon reaching each of the one or more breakpoints,

identifying one or more debugger rules associated with a query at a breakpoint;

in response to determining that conditions of the one or more debugger rules are satisfied, obtaining a stack trace before the query makes a call to a database; and

deriving query text of the query and a location of the query in source code of the client application.

6. The method of claim 5, further comprising:

in response to determining that conditions of the one or more debugger rules are not satisfied, continuing to run the client application through the debugger until another breakpoint is reached or execution of the client application is completed.

7. The method of claim 5, further comprising:

in response to deriving the query of the API call,

obtaining the query text of the query;

invoking a query parser to parse the query to identify one or more tables and one or more columns used by the query;

storing correlator results for the API call that identify a source file of the client application, the first location of the API call in the source code, parameters of the API call, and database objects which the query makes use of, wherein one of the parameters is the query text of the query; and

performing analysis using the correlator results.

8. The method of claim 7, further comprising:

retrieving the correlator results; and

generating user interface views using the correlator results, wherein the user interface views provide at least one of;

a view showing the query in the database and the query in the source code, a view showing database schemas and database objects that the query uses, a view showing queries per class, a view showing the queries used by each database object in the database, a view showing how queries are run, a view for exporting data, and a view showing performance information of execution count and execution time for each of the queries.

9. A computer program product comprising a computer readable storage medium storing computer readable program code that, when executed on a processor of a computer, causes the computer to:

invoke with a processor executing on a computer a source code parser to obtain source information that includes a first location of an Application Programming Interface (API) call and parameters of the API call in source code of a client application, where the parameters the API call do not include query text for a query that is to be used to access a database;

examine a stack trace to determine a second location of the API call in the stack trace; and

derive the query of the API call and a third location of the query in the source code by identifying the query in the stack trace at the first location of the API call in the stack trace.

10. The computer program product of claim 9, wherein the computer readable program code, when executed on a processor of a computer, causes the computer to:

in response to deriving the query of the API call,

obtain the query text of the query;

invoke a query parser to parse the query to identify one or more tables and one or more columns used by the query;

store correlator results for the API call that identify a source file of the client application, the first location of the API call in the source code, parameters of the API call, and database objects which the query makes use of, wherein one of the parameters is the query text of the query; and

perform analysis using the correlator results.

11. The computer program product of claim 10, wherein the computer readable program code, when executed on a processor of a computer, causes the computer to:

retrieve the correlator results; and

generate user interface views using the correlator results.

12. The computer program product of claim 11, wherein the user interface views provide at least one of:

a view showing the query in the database and the query in the source code, a view showing database schemas and database objects that the query uses, a view showing queries per class, a view showing the queries used by each database object in the database, a view showing how queries are run, a view for exporting data, and a view showing performance information of execution count and execution time for each of the queries.

13. A computer program product comprising a computer readable storage medium storing computer readable program code that, when executed on a processor of a computer, causes the computer to:

set, with a processor executing on a computer, one or more breakpoints in source code of a client application based on locations of Application Programming Interface (API) calls in the source code; and

while running the client application through a debugger, upon reaching each of the one or more breakpoints,

identify one or more debugger rules associated with a query at a breakpoint;

in response to determining that conditions of the one or more debugger rules are satisfied, obtain a stack trace before the query makes a call to a database; and

derive query text of the query and a location of the query in source code of the client application.

14. The computer program product of claim 13, wherein the computer readable program code, when executed on a processor of a computer, causes the computer to:

in response to determining that conditions of the one or more debugger rules are not satisfied, continue to run the client application through the debugger until another breakpoint is reached or execution of the client application is completed.

15. The computer program product of claim 13, wherein the computer readable program code, when executed on a processor of a computer, causes the computer to:

in response to deriving the query of the API call,

obtain the query text of the query;

invoke a query parser to parse the query to identify one or more tables and one or more columns used by the query;

store correlator results for the API call that identify a source file of the client application, the first location of the API call in the source code, parameters of the API call, and database objects which the query makes use of, wherein one of the parameters is the query text of the query; and

perform analysis using the correlator results.

16. The computer program product of claim 15, wherein the computer readable program code, when executed on a processor of a computer, causes the computer to:

retrieve the correlator results; and

generate user interface views using the correlator results, wherein the user interface views provide at least one of;

a view showing the query in the database and the query in the source code, a view showing database schemas and database objects that the query uses, a view showing queries per class, a view showing the queries used by each database object in the database, a view showing how queries are run, a view for exporting data, and a view showing performance information of execution count and execution time for each of the queries.

17. A system, comprising:

a processor;

memory; and

circuitry to perform operations, the operations comprising;

invoking with a processor executing on a computer a source code parser to obtain source information that includes a first location of an Application Programming Interface (API) call and parameters of the API call in source code of a client application, where the parameters the API call do not include query text for a query that is to be used to access a database;

examining a stack trace to determine a second location of the API call in the stack trace; and

deriving the query of the API call and a third location of the query in the source code by identifying the query in the stack trace at the first location of the API call in the stack trace.

18. The system of claim 17, wherein the operations further comprise:

in response to deriving the query of the API call,

obtaining the query text of the query;

invoking a query parser to parse the query to identify one or more tables and one or more columns used by the query;

storing correlator results for the API call that identify a source file of the client application, the first location of the API call in the source code, parameters of the API call, and database objects which the query makes use of, wherein one of the parameters is the query text of the query; and

performing analysis using the correlator results.

19. The system of claim 18, wherein the operations further comprise:

retrieving the correlator results; and

generating user interface views using the correlator results.

20. The system of claim 19, wherein the user interface views provide at least one of:

a view showing the query in the database and the query in the source code, a view showing database schemas and database objects that the query uses, a view showing queries per class, a view showing the queries used by each database object in the database, a view showing how queries are run, a view for exporting data, and a view showing performance information of execution count and execution time for each of the queries.

21. A system, comprising:

a processor;

memory; and

circuitry to perform operations, the operations comprising;

setting, with a processor executing on a computer, one or more breakpoints in source code of a client application based on locations of Application Programming Interface (API) calls in the source code; and

while running the client application through a debugger, upon reaching each of the one or more breakpoints,

identifying one or more debugger rules associated with a query at a breakpoint;

in response to determining that conditions of the one or more debugger rules are satisfied, obtaining a stack trace before the query makes a call to a database; and

deriving query text of the query and a location of the query in source code of the client application.

22. The system of claim 21, wherein the operations further comprise:

in response to determining that conditions of the one or more debugger rules are not satisfied, continuing to run the client application through the debugger until another breakpoint is reached or execution of the client application is completed.

23. The system of claim 21, wherein the operations further comprise:

in response to deriving the query of the API call,

obtaining the query text of the query;

invoking a query parser to parse the query to identify one or more tables and one or more columns used by the query;

storing correlator results for the API call that identify a source file of the client application, the first location of the API call in the source code, parameters of the API call, and database objects which the query makes use of, wherein one of the parameters is the query text of the query; and

performing analysis using the correlator results.

24. The system of claim 23, wherein the operations further comprise:

retrieving the correlator results; and

generating user interface views using the correlator results, wherein the user interface views provide at least one of;

a view showing the query in the database and the query in the source code, a view showing database schemas and database objects that the query uses, a view showing queries per class, a view showing the queries used by each database object in the database, a view showing how queries are run, a view for exporting data, and a view showing performance information of execution count and execution time for each of the queries.