Methods and systems for debugging bytecode in an on-demand service environment

• US 9,727,443 B2
• Filed: 11/17/2015
• Issued: 08/08/2017
• Est. Priority Date: 04/20/2010
• Status: Active Grant

• Current Assignee: Salesforce.com, Inc.
• Original Assignee: Salesforce.com, Inc.
• Inventors: Matthiesen, Taggart C., Unger, Richard, Wisnovsky, Peter S.
• Primary Examiner(s): Zhen, Li B
• Assistant Examiner(s): CHEN, SEN THONG
• Application Number:
  US14/943,944
• Publication Number:
  US 20160070639A1
• Time in Patent Office: 630 Days
• Field of Search: 717124
• CPC Class Codes: G06F 11/3636 by tracing the execution of the program
• CPC Class Codes: G06F 11/3664 Environments for testing or debugging software

Abstract

Described herein are means for debugging byte code in an on-demand service environment system including a system for simulating execution debug in a multi-tenant database environment. Such means may include: receiving a request at a web-server of the system, determining one or more trace preferences are active for the request, sending the request to a logging framework communicatively interfaced to the multi-tenant database implementation, processing the request via the logging framework, and capturing at least a portion of the execution data emitted responsive to execution of the plurality of events for use in simulating execution debug of the events. Other related embodiments are additionally described.

Claims

1. A method for simulating execution debug in a system of a multi-tenant database environment, the system having at least a processor and a memory therein, wherein the method comprises:

executing code within the multi-tenant database environment on behalf of a plurality of separate and distinct customer organizations, each customer organization being uniquely identified by an organization identifier (OrgID), the multi-tenant database environment having elements of hardware and software that are shared by the plurality of separate and distinct customer organizations;

wherein stopping the execution of the code for execution debug within the multi-tenant environment is not permitted due to such stopping of the code execution causing a code execution stop for all of the customer organizations presently executing other code on the shared hardware and software resource elements provided by the multi-tenant environment;

forcing emission of execution data from the execution of the code within the multi-tenant database environment on behalf of the plurality of separate and distinct customer organizations by encoding one or more trace flags into the code prior to executing the code and by routing any operation or executable line of code processed against the multi-tenant database implementation on behalf of any one of the plurality of separate and distinct customer organizations through an encapsulated library of services to trigger the emission of the execution data when one or more trace preferences are active for a request to execute the code, the one or more trace preferences based on a client organization identifier (OrgID) associated with the request;

capturing the execution data emitted from the execution of the code within the multi-tenant database environment, wherein the execution data emitted by the encapsulated library of services provides a transcript of all execution events that occur within the multi-tenant database implementation on behalf of any one of the plurality of separate and distinct customer organizations;

persistently storing the captured execution data emitted from the execution of the code as the transcript of execution events; and

replaying execution events associated with the OrgID associated with the request to simulate an original execution performed via the execution of the code within the multi-tenant environment by referencing the persistently stored execution data of the transcript of execution events without requiring any portion of the original execution be re-executed or reprocessed, wherein an execution debug simulator replays the execution events from the transcript captured based on the one or more trace debug preferences triggered to be active pursuant to the request as originally received.

2. The method of claim 1, wherein replaying the transcript of execution events to simulate an original execution performed via the execution of the code within the multi-tenant environment comprises retrieving and replaying the transcript of execution events without pausing, stopping, halting operations associated with the original execution performed via the execution of the code within the multi-tenant environment.

3. The method of claim 1, wherein replaying the transcript of execution events to simulate an original execution performed via the execution of the code within the multi-tenant environment comprises analyzing variable inputs/outputs, analyzing command return codes, analyzing formed SQL queries, and/or analyzing data sets returned subject to SQL queries without pausing, stopping, halting operations associated with the original execution performed via the execution of the code within the multi-tenant environment.

4. The method of claim 1:

wherein performing the execution of the code within the multi-tenant database environment comprises executing code from the encapsulated library of services;

wherein all interactions requested by the plurality of separate and distinct customer organizations from the multi-tenant database implementation are provided by execution code within the encapsulated library of services.

5. The method of claim 4:

wherein a host organization implements the multi-tenant database implementation;

wherein the method further comprises;

receiving a request for services at the host organization from one of the plurality of separate and distinct customer organizations; and

routing any execution of the code required in fulfillment of the request through the encapsulated library of services regardless of the functionality or operation to be executed in fulfillment of the request.

6. The method of claim 1, wherein a collection of execution events emitted by the encapsulated library of services provides a full and complete view of processing for each individual line of code executed or processed by the multi-tenant database implementation on behalf of any one of the plurality of separate and distinct customer organizations.

7. The method of claim 1, wherein capturing the execution data emitted from the execution of the code within the multi-tenant database environment comprises capturing the execution data via a high-data-rate Random Access Memory (RAM) and wherein the high-data-rate RAM caches the portion of the execution data emitted responsive to execution of the plurality of events until a flush command is received.

8. The method of claim 7, wherein persistently storing the captured execution data emitted from the execution of the code as a transcript of execution events comprises flushing a portion of the execution data from the high-data-rate RAM to a non-volatile storage device for persistent storage, wherein the non-volatile storage device is selected from the group comprising:

persistent storage on a hard-disk drive within the host organization having space allocated to a customer organization associated with the request;

persistent storage within the multi-tenant database implementation in an area allocated to a customer organization associated with the request; and

persistent storage on a non-volatile storage device communicatively interfaced with an end-user client machine having originated the request, wherein the end-user client machine is remote and distinct from the system of the host organization.

9. The method of claim 1, wherein replaying the transcript of execution events to simulate an original execution performed via the execution of the code within the multi-tenant environment further comprises:

accessing a specified portion of the execution data emitted responsive to the execution of a plurality of events associated with the execution of the code; and

simulating execution of the plurality of events via a graphical user interface, wherein simulating execution of the plurality of events comprises at least presenting output corresponding to execution of one or more of the plurality of events based on the portion of execution data accessed and without re-executing any of the plurality of events.

10. The method of claim 1, further comprising:

receiving a request for services from one of the plurality of separate and distinct customer organizations, the request for services causing the execution of the code within the multi-tenant database environment; and

wherein forcing emission of execution data from the execution of the code within the multi-tenant database environment comprises forcing the emission of execution data from the execution of the code based at least in part on one or more trace preferences transmitted within the request for services.

11. The method of claim 10, further comprising:

extracting the one or more trace preferences from the request for services to determine which, if any, trace flags are active for the request for services.

12. The method of claim 1, further comprising:

receiving a request for services from one of the plurality of separate and distinct customer organizations, the request for services causing the execution of the code within the multi-tenant database environment; and

wherein forcing emission of execution data from the execution of the code within the multi-tenant database environment comprises forcing the emission of execution data from the execution of the code based at least in part on one or more trace preferences pre-stored or pre-associated with incoming requests from the customer organizations originating the request for services.

13. Non-transitory computer readable storage media having instructions store thereupon that, when executed by a processor of a system in a multi-tenant database environment, the instructions cause the system to perform operations comprising:

executing code within the multi-tenant database environment on behalf of a plurality of separate and distinct customer organizations, each customer organization being uniquely identified by an organization identifier (OrgID), the multi-tenant database environment having elements of hardware and software that are shared by the plurality of separate and distinct customer organizations;

wherein stopping the execution of the code for execution debug within the multi-tenant environment is not permitted due to such stopping of the code execution causing a code execution stop for all of the customer organizations presently executing other code on the shared hardware and software resource elements provided by the multi-tenant environment;

forcing emission of execution data from the execution of the code within the multi-tenant database environment on behalf of the plurality of separate and distinct customer organizations by encoding one or more trace flags into the code prior to executing the code and by routing any operation or executable line of code processed against the multi-tenant database implementation on behalf of any one of the plurality of separate and distinct customer organizations through an encapsulated library of services to trigger the emission of the execution data when one or more trace preferences are active for a request to execute the code, the one or more trace preferences based on a client organization identifier (OrgID) associated with the request;

capturing the execution data emitted from the execution of the code within the multi-tenant database environment, wherein the execution data emitted by the encapsulated library of services provides a transcript of all execution events that occur within the multi-tenant database implementation on behalf of any one of the plurality of separate and distinct customer organizations;

persistently storing the captured execution data emitted from the execution of the code as the transcript of execution events; and

replaying execution events associated with the OrgID associated with the request to simulate an original execution performed via the execution of the code within the multi-tenant environment by referencing the persistently stored execution data of the transcript of execution events without requiring any portion of the original execution be re-executed or reprocessed, wherein an execution debug simulator replays the execution events from the transcript captured based on the one or more trace debug preferences triggered to be active pursuant to the request as originally received.

14. The non-transitory computer readable storage media of claim 13, wherein replaying the transcript of execution events to simulate an original execution performed via the execution of the code within the multi-tenant environment comprises retrieving and replaying the transcript of execution events without pausing, stopping, halting operations associated with the original execution performed via the execution of the code within the multi-tenant environment.

15. The non-transitory computer readable storage media of claim 13:

wherein performing the execution of the code within the multi-tenant database environment comprises executing code from the encapsulated library of services;

wherein all interactions requested by the plurality of separate and distinct customer organizations from the multi-tenant database implementation are provided by execution code within the encapsulated library of services.

16. A system for simulating execution debug in a multi-tenant database environment, the system comprising:

a multi-tenant database environment to execute code on behalf of a plurality of separate and distinct customer organizations, each customer organization being uniquely identified by an organization identifier (OrgID), the multi-tenant database environment having elements of hardware and software that are shared by the plurality of separate and distinct customer organizations;

wherein stopping the execution of the code for execution debug within the multi-tenant environment is not permitted due to such stopping of the execution of the code causing a code execution stop for all of the customer organizations presently executing other code on the shared hardware and software resource elements provided by the multi-tenant environment;

the multi-tenant database environment to force emission of execution data from the execution of the code within the multi-tenant database environment on behalf of the plurality of separate and distinct customer organizations by encoding one or more trace flags into the code prior to executing the code and by routing any operation or executable line of code processed against the multi-tenant database implementation on behalf of any one of the plurality of separate and distinct customer organizations through an encapsulated library of services to trigger the emission of the execution data when one or more trace preferences are active for a request to execute the code, the one or more trace preferences based on a client organization identifier (OrgID) associated with the request;

memory to capture the execution data emitted from the execution of the code within the multi-tenant database environment, wherein the execution data emitted by the encapsulated library of services provides a transcript of all execution events that occur within the multi-tenant database implementation on behalf of any one of the plurality of separate and distinct customer organizations;

storage media to persistently store the captured execution data emitted from the execution of the code as the transcript of execution events; and

a debug simulator to replay the transcript of execution events associated with the OrgID associated with the request to simulate an original execution performed via the execution of the code within the multi-tenant environment by referencing the persistently stored execution data of the transcript of execution events without requiring any portion of the original execution be re-executed or reprocessed, wherein an execution debug simulator replays the execution events from the transcript captured based on the one or more trace debug preferences triggered to be active pursuant to the request as originally received.

17. The system of claim 16, further comprising:

a web server provides a web-based interface to a remotely located end-user client machine associated with one of the plurality of separate and distinct customer organizations;

wherein the remotely located end-user client machine submits a request for services from the multi-tenant database implementation;

the web server to receive the request for services from the remotely located end-user client machine;

the web server to encode one or more trace flags into the request for services based on trace preferences corresponding to a user identifier (UserID) or a client organization identifier (OrgID) associated with the request for services; and

the web server to forward the request having the one or more trace flags encoded therein to one or more work thread processors to process the request for services within the multi-tenant database implementation.

18. The system of claim 16, wherein the debug simulator to replay the transcript of execution events to simulate an original execution performed via the execution of the code within the multi-tenant environment comprises the debug simulator to retrieve and replay the transcript of execution events without pausing, stopping, halting operations associated with the original execution performed via the execution of the code within the multi-tenant environment.