DEBUGGING IN-CLOUD DISTRIBUTED CODE IN LIVE LOAD ENVIRONMENT

• US 20190026216A1
• Filed: 09/13/2018
• Published: 01/24/2019
• Est. Priority Date: 01/29/2016
• Status: Active Grant

• Current Assignee: CA, Inc. (d/b/a CA Technologies) (Broadcom, Inc.)
• Original Assignee: CA, Inc. (d/b/a CA Technologies) (Broadcom, Inc.)
• Inventors: Mankovskii, Serguei
• Granted Patent: US 10,445,222 B2
• Time in Patent Office: Days
• CPC Class Codes: G06F 11/362 Software debugging
• CPC Class Codes: G06F 11/3648 using additional hardware
• CPC Class Codes: G06F 11/3664 Environments for testing or debugging software
• CPC Class Codes: H04L 67/10 in which an application is distributed across nodes in the network software deployment G06F8/60; multiprogramming arrangements G06F9/46

Abstract

A multi-device data processing machine system includes a plurality of network-connected cliental servers including first and second production servers coupled to a dynamic load balancer. The machine system also includes an SaaS development server that is configured to pass under-development process requests to the load balancer in combination with a mix command such that the load balancer routes a mix of routine production traffic and the under-development process requests to at least one of the production servers that is instrumented for enabling remote debugging of code executing therein so that the under-development process requests can be debugged under the full or partial stresses of a live production environment.

Claims

1-20. -20. (canceled)

21. A machine-implemented method of developing operative code in a live production loaded environment that includes recordation of transactions, the developing method comprising:

marking development-related communications so as to distinguish the development-related communications from live production-related communications;

distributing the live production-related communications and the marked development-related communications to one or more servers of said live production loaded environment, where the one or more servers have instantiated in them, first code for handling production process instances and second code for handling development process instances, wherein transaction requests of the live production-related communications are routed for handling by the first code and transaction requests of the marked development-related communications are routed for handling by the second code; and

recording outcomes from the handling of the transaction requests of the marked development-related communications and from the handling of the transaction requests of the live production-related communications, the recording being responsive to presence and absence of the markings that distinguish the development-related communications from the live production-related communications.

22. The method of claim 21 wherein said marking of the development-related communications includes attaching development-indicating tokens to the development-related communications.

23. The method of claim 21 wherein said marking of the development-related communications includes assigning unique destination addresses to the development-related communications the unique destination addresses being usable for distinguishing the development-related communications form the live production-related communications.

24. The method of claim 21 wherein the second code includes debugging code.

25. The method of claim 21 wherein said responsiveness of the outcomes recording includes recording outcomes from the handling of the transaction requests of the marked development-related communications in a simulated database rather than in a live production database.

26. The method of claim 21 wherein said responsiveness of the outcomes recording includes recording outcomes from the handling of the transaction requests of the marked development-related communications in a live production database and in a manner that the recorded outcomes from handling of the marked development-related communications can be distinguished from recorded outcomes of handling the live production-related communications.

28. The method of claim 21 wherein correlator lookup tables (LUTs) are provided in at least those of the servers to which the marked development-related communications can be distributed, the correlator LUTs enabling the servers to internally distinguish contents of the marked development-related communications from contents of the live production-related communications.

29. The method of claim 28 wherein the handling of the development process instances within the servers includes loading debug supporting library functions provided within the servers when instantiating the code for handling the development process instances.

30. The method of claim 28 wherein the instantiated code for handling the development process instances includes reporting code configured to report at least one of prespecified execution thread trace inspections, breakpoint encounters and development transaction status to a development server.

31. The method of claim 28 wherein the instantiated code for handling the development process instances includes reconfiguration code enabling reconfiguration of debugging operations within one or more of the servers in response to debugging commands sent by the development server.

32. The method of claim 21 and further comprising:

initiating development transactions by routing simulated transaction sessions through simulated client terminals which produce the marked development-related communications.

33. The method of claim 32 and further comprising:

passing the produced marked development-related communications through a dynamic load balancer which is responsive to markings of the development-related communications when distributing communications to respective servers within the live production loaded environment.

34. The method of claim 21 and further comprising:

determining effects on performance of the handling of the production process instances due to concurrent handling of the development process instances; and

determining effects on performance of the handling of the development process instances due to concurrent handling of the production process instances.

27. The method of claim 27 and further comprising:

purging from the live production database the recorded outcomes from handling of the marked development-related communications.

35. A networked system comprising:

interconnected servers and traffic distributors adapted for handling live production-related communications used for carrying out live production transactions;

a development server configured to generate and mark transaction sessions for use in debugging under-development software, the marking being usable for distinguishing development-related communications from the live production-related communications, the development server being configured to cause routing to at least one of the servers that handles live production-related communications, one or more of development-related communications containing respective and marked transaction session requests for concurrent handling by the at least one of the servers; and

storage for recording therein outcomes of handling of the live production-related communications and of the development-related communications, the storage being configured to distinguish between recordings therein of outcomes of the handling of the live production-related communications and of outcomes of the handling of the development-related communications.

36. The system of claim 35 wherein:

said marking of the generated transaction sessions includes attaching development-indicating tokens for inclusion in the development-related communications.

37. The system of claim 35 wherein:

said marking of the generated transaction sessions includes assigning unique destination addresses for inclusion in the development-related communications, the unique destination addresses being usable for distinguishing the development-related communications form the live production-related communications.

38. The system of claim 35 wherein:

said storage includes a simulated database and a live production database; and

outcomes from handling of the development-related communications are stored in the simulated database while outcomes from the handling of the live production-related communications are stored in the live production database.

39. A non-transitory computer readable medium for use in a networked system having interconnected servers and traffic distributors adapted for handling live production-related communications used for carrying out live production transactions, the medium storing instructions for causing a carrying out within the networked system of an automated method for developing operative code while the code is executed in a live production loaded environment of the networked system, where the system records transactions carried out within the system, the developing method comprising:

marking development-related communications so as to distinguish the development-related communications from live production-related communications;

distributing the live production-related communications and the marked development-related communications to one or more servers of said live production loaded environment, where the one or more servers have instantiated in them, first code for handling production process instances and second code for handling development process instances, wherein transaction requests of the live production-related communications are routed for handling by the first code and transaction requests of the marked development-related communications are routed for handling by the second code; and

recording outcomes from the handling of the transaction requests of the marked development-related communications and from the handling of the transaction requests of the live production-related communications, the recording being responsive to presence and absence of the markings that distinguish the development-related communications from the live production-related communications.

40. The medium of claim 39 wherein said marking of the development-related communications includes attaching development-indicating tokens to the development-related communications.