METHOD AND SYSTEM FOR REMOTE DEBUG PROTOCOL PROXYING FOR PRODUCTION DEBUGGING; SELECTIVE SESSION AND USER ROUTING FOR DEBUGGING IN MULTI-TENANT CLOUD COMPUTING INFRASTRUCTURE

• US 20120131555A1
• Filed: 05/17/2011
• Published: 05/24/2012
• Est. Priority Date: 05/17/2010
• Status: Active Grant

• Current Assignee: Salesforce.com, Inc.
• Original Assignee: Salesforce.com, Inc.
• Inventors: HOSSAIN, FIAZ, Iry, James, Zheng, Zuye, Kulkami, Nagraj
• Granted Patent: US 8,752,017 B2
• Time in Patent Office: Days
• US Class Current: 717/124
• CPC Class Codes: G06F 11/362 Software debugging

Abstract

A proxy server receives requests, and determines which application server of a cluster of servers to send the request. The determination may be based on a load balancing algorithm. The proxy server determines whether each request is a debug request. The proxy server send the debug request to a debug server, but blocks unsafe debug statements from reaching the debug server.

Claims

1. A method for selective session and user routing for debugging in multi-tenant cloud computing infrastructure in a database system, the method comprising:

receiving at proxy server machine a request, the machine including a processor system including one or more processors and a memory storing machine instructions for the proxy server machine;

determining, by the processor system, whether the request is a debugging request; and

if the request is a debugging request,

determining if the debugging request is safe by sending the debugging request to a debug server.

2. The method of claim 1, the determining being performed by the proxy server determining whether the request has a session id with a debug flag.

3. The method of claim 2, further comprising:

removing the debug flag after the code is sent to the debug server.

4. The method of claim 1, further comprising:

determining, by the proxy server, whether the request includes debug statements that are not safe; and

if it is determined that the request includes statements that are not safe, blocking the debug statements that are determined to be unsafe.

5. The method of claim 4, the determining of whether the request includes the debug statements that are unsafe, includes at least determining a level of debug access that is permitted to the request, and determining whether there are any debug statements in the request that require a level of access that is not permitted to the request.

6. The method of claim 5, the determining of whether there are any debug statements in the request that require a level of access that is not permitted including which of a plurality of debug levels is associated with the request.

7. The method of claim 6, the plurality of debug levels including at least one level that only allows debug statements that facilitate viewing output, but does not allow debug statements that change portions of statements.

8. The method of claim 6, the plurality of debug levels including at least one level that allows debug statements that facilitate swap change variables, but does not allow debug statements that change portions of statements.

9. The method of claim 6, the plurality of debug levels including at least one level that allows debug statements that swap portions of code.

10. The method of claim 6, the plurality of debug level including at least one level that permits debug statements that invoke returns, but does not allow variable changes.

11. The method of claim 1, further comprising, logging statements that are blocked.

12. The method of claim 1,

blocking at least two debug processes, blocking one debug process that modifies a class definition of an existing class while the code being debugged is running;

and another process that pop frames off a stack to rerun code, by blocking the at least two debug processes, code cannot be replaced or re-written while running.

13. The method of claim 1, each server of the cluster, including the debug server, running the same software, except the debug server also runs debug software.

14. The method of claim 13, the cluster of servers running a multi-tenant relational database service over a wide area network in which each tenant is provided usage of a portion of the database as service, the tenant not being required to download software or maintain the database, the multi-tenant database including one or more tenants that are organizations having clients and members that are users of the multi-tenant database as a result of the tenant being a tenant of the multi-tenant database.

15. The method of claim 1, the debug server being an application server that is part of a cluster of servers;

each server of the cluster, including the debug server, running the same software, except the debug server also runs debug software;

the determining being performed by at least the proxy server determining whether the request has a session id with a debug flag;

the cluster of servers running a multi-tenant relational database service over a wide area network in which each tenant is provided usage of a portion of the database as service, the tenant not being required to download software or maintain the database, the multi-tenant database including one or more tenants that are organizations having clients and members that are users of the multi-tenant database as a result of the tenant being a tenant of the multi-tenant database.

the method further comprising;

removing the debug flag after the code is sent to the debug server;

determining, by the proxy server, whether the request includes debug statements that are not safe by at least

determining a level of debug access that is permitted to the request, and determining whether there are any debug statements in the request that require a level of access that is not permitted to the request;

the plurality of debug levels including at least

a first level that only allows debug statements that facilitate viewing output, but does not allow debug statements that change portions of statements;

a second level that allows invoking returns and early return in addition to allowing debug statements that facilitate viewing output and

a third level that allows debug statements that change variables, but does not allow debug statements that change portions of statements; and

a fourth level that allows all debug statements;

if it is determined that the request includes at least one statements that is not safe, blocking the debug statements that are determined to be unsafe;

the determining of whether there are any debug statements in the request that require a level of access that is not permitted including which of a plurality of debug levels is associated with the request; and

logging statements that are blocked.

16. The method of claim 15, if the level of access is determined to be the first level, the second level, or the third level,

blocking at least two debug processes, blocking one debug process that swaps a prior class definition with a new class definition;

and another process that pop frames off a stack to rerun code, by blocking the at least two debug processes, code cannot be replaced or re-written while the code being debugged is running.

17. The method of claim 15, if the level of access is determined to be the first level or the second level,

blocking a debug process used to create a string and return an identifier associated with the string created while the code being debugged is running;

blocking a debug process for setting a value of one or more static fields while the code being debugged is running;

blocking a debug process for creating a new instance of a class while the code being debugged is running;

blocking a debug statement for creating a new array object while the code being debugged is running;

blocking a debug process for setting the value of one or more fields of an object that is an instance of a class type;

blocking a debug process that sets a range of array components while the code being debugged is running;

blocking a process that sets one or more local variables even if the local variable; and

blocking a debug process that invokes an instance of a method while the code being debugged is running;

18. A machine readable medium having stored thereon one or more machine instructions, which when implemented cause one or more processor to implement a method comprising:

receiving at proxy server machine a request, the machine including a processor system including one or more processors and a memory storing machine instructions for the proxy server machine;

determining, by the processor system, whether the request is a debugging request; and

if the request is a debugging request,

forwarding the request, via the proxy server to a debugging server.

19. A system comprising

one or more processors;

one or more storage systems having one or more

machine readable media having stored thereon one or more machine instructions, which when implemented cause one or more processor to implement a method comprising;

receiving at proxy server machine a request, the machine including a processor system including one or more processors and a memory storing machine instructions for the proxy server machine;

determining, by the processor system, whether the request is a debugging request; and

if the request is a debugging request,

forwarding the request, via the proxy server to a debugging server.