TESTING AND REPRODUCTION OF CONCURRENCY ISSUES

• US 20190310930A1
• Filed: 04/04/2018
• Published: 10/10/2019
• Est. Priority Date: 04/04/2018
• Status: Active Grant

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Joglekar, Amit P., Mohandas, Praveen
• Granted Patent: US 10,579,501 B2
• Time in Patent Office: Days
• CPC Class Codes: G06F 11/3632 of specific synchronisation aspects
• CPC Class Codes: G06F 11/3636 by tracing the execution of the program
• CPC Class Codes: G06F 11/3644 by instrumenting at runtime
• CPC Class Codes: G06F 11/3664 Environments for testing or debugging software
• CPC Class Codes: G06F 9/485 Task life-cycle, e.g. stopping, restarting, resuming execution G06F9/4881 takes precedence
• CPC Class Codes: G06F 9/52 Program synchronisation; Mutual exclusion, e.g. by means of semaphores
• CPC Class Codes: G06F 9/526 Mutual exclusion algorithms
• CPC Class Codes: G06F 9/547 Remote procedure calls [RPC]; Web services

Abstract

A method and system for testing a server code in a server concurrently handling multiple client requests create a job-specific breakpoint in the server code using a library application programming interface (API) that allows the job-specific breakpoint in the server code being enabled or disabled based on a job identifier. The library API controls the job-specific breakpoint in the server code via a plurality of readymade functions that execute, in a desired sequence, various synchronous and asynchronous program paths associated with the multiple client requests. By using the library API, the method and system are capable of establishing a new server connection with the server and retrieving the job identifier from the server associated with the established new server connection, pausing execution of a client job based on enabling the job-specific breakpoint, and resuming execution of the client job based on disabling the job-specific breakpoint.

Claims

1. A method for testing a server code in a server concurrently handling multiple client requests, the method comprising:

creating a job-specific breakpoint in the server code using a library application programming interface, wherein the job-specific breakpoint in the server code is enabled or disabled based on a job identifier, the library application programming interface controls the job-specific breakpoint in the server code, the library application programming interface comprises a plurality of readymade functions that execute, in a desired sequence, various synchronous and asynchronous program paths associated with the multiple client requests and are capable of

establishing a new server connection with the server and retrieving the job identifier from the server associated with the established new server connection;

pausing execution of a client job based on enabling the job-specific breakpoint in the server code using the library application programming interface; and

resuming execution of the client job based on disabling the job-specific breakpoint in the server code using the library application programming interface.

2. The method of claim 1, wherein the job-specific breakpoint in the server code allows creating readable and repeatable reproduction scripts and test cases containing interleaved executions of parallel client requests.

3. The method of claim 1, further comprising:

an application programming interface to create a new thread of execution for every client request executed in the client job using syntax of the programming language used for implementing the library application programming interface.

4. The method of claim 1, wherein the library application programming interface retains information about relationships between client jobs, job identifiers, threads, and breakpoints including node specific breakpoints.

5. The method of claim 1, wherein the library application programming interface allows queuing of client requests.

6. The method of claim 1, wherein the server code is tested based on one or more of the following interactions:

interaction between synchronous and asynchronous execution of client requests submitted concurrently from two or more different client jobs;

interaction between nodes of the server; and

interaction between asynchronous execution of a previous client request and synchronous and asynchronous execution of a subsequent client request in same client job for a given client.

7. The method of claim 6, wherein the one or more interactions are a result of a state change including failure of a node in a cluster or any state change in a specialized state-machine used by server components.

8. The method of claim 1, wherein the job-specific breakpoint is located in a synchronous execution path or an asynchronous execution path in the server code.

9. The method of claim 1, further comprising:

performing one or more of the following error checks using the library application programming interface;

determining whether a client job has been created;

determining whether the client job is currently executing another client request;

determining whether execution of the another client request is currently paused at a job-specific breakpoint;

determining whether execution of the client job is currently paused at a specified asynchronous breakpoint;

determining whether there is no future breakpoint specified for the client job; and

determining whether a future breakpoint has been specified for the client job.

10. The method of claim 1, further comprising:

creating the job-specific breakpoint in the server code for a node of the server using the library application programming interface; and

pausing execution of the client job based on enabling the job-specific breakpoint in the server code for the node of the server using the library application programming interface.

11. The method of claim 1, further comprising:

deleting the job-specific breakpoint in the server code for a node of the server using the library application programming interface; and

resuming execution of the client job based on disabling, the job-specific breakpoint in the server code for the node of the server using the library application programming interface.

12. A computer system for testing a server code in a server concurrently handling multiple client requests, the computer system comprising:

one or more processors, one or more computer-readable memories, one or more computer-readable tangible storage devices, and program instructions stored on at least one of the one or more storage devices for execution by at least one of the one or more processors via at least one of the one or more memories, wherein the computer system is capable of performing a method comprising;

creating a job-specific breakpoint in the server code using a library application programming interface, wherein the job-specific breakpoint in the server code is enabled or disabled based on a job identifier, the library application programming interface controls the job-specific breakpoint in the server code, the library application programming interface comprises a plurality of readymade functions that execute, in a desired sequence, various synchronous and asynchronous program paths associated with the multiple client requests and are capable of

establishing a new server connection with the server and retrieving the job identifier from the server associated with the established new server connection;

pausing execution of a client job based on enabling the job-specific breakpoint in the server code using the library application programming interface; and

resuming execution of the client job based on disabling the job-specific breakpoint in the server code using the library application programming interface.

13. The computer system of claim 12, wherein the job-specific breakpoint in the server code allows creating readable and repeatable reproduction scripts and test cases containing interleaved executions of parallel client requests.

14. The computer system of claim 12, further comprising:

an application programming interface to create a new thread of execution for every client request executed in the client job using syntax of the programming language used for implementing the library application programming interface.

15. The computer system of claim 12, wherein the library application programming interface retains information about relationships between client jobs, job identifiers, threads, and breakpoints including node specific breakpoints.

16. The computer system of claim 12, wherein the library application programming interface allows queuing of client requests.

17. The computer system of claim 12, wherein the server code is tested based on one or more of the following interactions:

interaction between synchronous and asynchronous execution of client requests submitted concurrently from two or more different client jobs;

interaction between nodes of the server; and

interaction between asynchronous execution of a previous client request and synchronous and asynchronous execution of a subsequent client request in same client job for a given client.

18. The computer system of claim 17, wherein the one or more interactions are a result of a state change including failure of a node in a cluster or any state change in a specialized state-machine used by server components.

19. The computer system of claim 12, wherein the job-specific breakpoint is located in a synchronous execution path or an asynchronous execution path in the server code.

20. The computer system of claim 12, further comprising:

performing one or more of the following error checks using the library application programming interface;

determining whether a client job has been created;

determining whether the client job is currently executing another client request;

determining whether execution of the another client request is currently paused at a breakpoint;

determining whether execution of the client job is currently paused at a specified asynchronous breakpoint;

determining whether there is no future breakpoint specified for the client job; and