Correlating queries issued by applications with their source lines and analyzing applications for problem determination and where used analysis

• US 9,020,939 B2
• Filed: 06/30/2009
• Issued: 04/28/2015
• Est. Priority Date: 06/30/2009
• Status: Expired due to Fees

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Brodsky, Stephen Andrew, Courtois, Zeus Orion, Jacopi, Tom William, Kwong, Michael Yiupun, Leung, Tony Kai-chi, Surange, Sonali
• Primary Examiner(s): Fan, Shiow-Jy
• Application Number:
  US12/495,669
• Publication Number:
  US 20100332473A1
• Time in Patent Office: 2,128 Days
• Field of Search: 707/736, 719/328
• 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:

obtaining, with a processor executing on a computer, information from source code of a client application that includes a location of an Application Programming Interface (API) call that issues a query and parameters of the API call in the source code, wherein query text for the query is not available until the source code is run;

running the source code to obtain a stack trace that includes the location of the API call in the stack trace and the query text for the query issued by the API call;

examining the stack trace to determine a match between the location of the API call in the source code and the location of the API call in the stack trace;

identifying the query text in the stack trace for the API call in the stack trace as the query text associated with the API call at the location in the source code;

storing the query and database objects used by the query in a repository; and

in response to receiving a change request for one of the database objects, returning the query from the repository for use in assessing an impact of the change request.

2. The method of claim 1, further comprising:

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 location of the API call in the source code, the parameters of the API call, and the 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 a 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. The method of claim 1, further comprising:

parsing the source code is parsed to obtain the information.

6. 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:

obtain information from source code of a client application that includes a location of an Application Programming Interface (API) call that issues a query and parameters of the API call in the source code, wherein query text for the query is not available until the source code is run;

run the source code to obtain a stack trace that includes the location of the API call in the stack trace and the query text for the query issued by the API call;

examine the stack trace to determine a match between the location of the API call in the source code and the location of the API call in the stack trace;

identifying the query text in the stack trace of for the API call in the stack trace as the query text associated with the API call at the location in the source code;

storing the query and database objects used by the query in a repository; and

in response to receiving a change request for one of the database objects, returning the query from the repository for use in assessing an impact of the change request.

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

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 location of the API call in the source code, the parameters of the API call, and the 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.

8. The computer program product of claim 7, 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.

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

a view showing the query in a 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.

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

parse the source code is parsed to obtain the information.

11. A system, comprising:

a processor;

memory; and

circuitry to perform operations, the operations comprising;

obtaining information from source code of a client application that includes a location of an Application Programming Interface (API) call that issues a query and parameters of the API call in the source code, wherein query for the query text is not available until the source code is run;

running the source code to obtain a stack trace that includes the location of the API call in the stack trace and the query text for the query issued by the API call;

examining the stack trace to determine a match between the location of the API call in the source code and the location of the API call in the stack trace;

identifying the query text in the stack trace for the API call in the stack trace as the query text associated with the API call at the location in the source code;

storing the query and database objects used by the query in a repository; and

in response to receiving a change request for one of the database objects, returning the query from the repository for use in assessing an impact of the change request.

12. The system of claim 11, wherein the operations further comprise:

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 location of the API call in the source code, the parameters of the API call, and the 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.

13. The system of claim 12, wherein the operations further comprise:

retrieving the correlator results; and

generating user interface views using the correlator results.

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

a view showing the query in a 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.

15. The system of claim 12, wherein the operations further comprise:

parsing the source code is parsed to obtain the information.