Remote debugging

• US 7,444,552 B2
• Filed: 03/28/2007
• Issued: 10/28/2008
• Est. Priority Date: 01/21/2004
• Status: Expired due to Term

• Current Assignee: SAP SE
• Original Assignee: SAP AG (SAP SE)
• Inventors: Kilian, Frank
• Primary Examiner(s): Lohn; Joshua A
• Application Number:
  US11/729,501
• Publication Number:
  US 20070174715A1
• Time in Patent Office: 580 Days
• Field of Search: 714/4, 714/31, 714/43
• US Class Current: 714/43
• CPC Class Codes: G06F 11/362 Software debugging

Abstract

A system and method are described for remotely debugging an application server. In one embodiment, a plurality of application servers are organized into groups referred to as “instances.” Each instance may include a group of redundant application servers, one or more debug nodes, and a dispatcher. The dispatcher distributes service requests to each of the application servers in accordance with a load-balancing mechanism. In addition, a central message passing architecture is defined which allows the various instances to communicate with one another. In one embodiment, a debug node is isolated from the load-balancing mechanism. The debug node may also be isolated from the central message passing architecture. A remote node may then debug an application on the debug node, without disrupting processes executing on other application servers in the instance.

Claims

1. A computer-implemented method comprising:

activating a debug node in response to a request from a remote node, wherein the debug node is an application server selected from a group of redundant application servers participating in a messaging service;

receiving a confirmation from the remote node that the debug node is no longer participating in the messaging service; and

debugging an application on the debug node in response to a request from the remote node.

2. The method of claim 1, further comprising:

wherein the group of redundant application servers participate in a load balancing mechanism; and

removing the debug node from participation in the load-balancing mechanism before debugging the application on the debug node.

3. The method of claim 2, further comprising:

wherein the load balancing mechanism is a dispatcher for distributing service requests among the redundant application servers in the group; and

removing the debug node from the load balancing mechanism is instructing the dispatcher to discontinue distributing service requests to the debug node while debugging the application on the debug node.

4. The method of claim 2, further comprising,

deactivating the debug node in response to a request from the remote node;

and

restoring participation in the load balancing mechanism for the selected application server.

5. The method of claim 1, further comprising,

deactivating the debug node in response to a request from the remote node;

and

restoring participation in the messaging service for the selected application server.

6. The method of claim 1, wherein the debug node is a Java 2 Enterprise Edition server node.

7. An apparatus comprising:

a development environment to debug an application; and

a processor and logic executable thereon to

issue a request to a message server to enable debugging in an instance of remote application servers;

receive an indication from the instance of remote application servers which of the remote application servers has been selected as a debug node;

receive a confirmation from the message server that the debug node has been isolated from a messaging service provided to the instance of remote application servers; and

issue a request to activate the debug node in which to commence debugging the application.

8. The apparatus of claim 7, wherein the processor and logic executable thereon is to further

issue a request via the message server to the instance of remote application servers to isolate the debug node from a load-balancing mechanism of the instance of application servers;

and

receive a confirmation from the message server that the debug node has been isolated from the load balancing mechanism prior to commencing debugging the application.

9. A system comprising:

a means for starting a debug node from a remote node, wherein the debug node is one of a plurality of nodes within an instance of application servers;

a means for isolating the debug node from a messaging service of the instance of application servers;

a means for debugging an application on the debug node from the remote node; and

a means for stopping the debug node from the remote node.

10. The system of claim 9 wherein the means for starting the debug node further comprises:

a means for isolating the debug node from a load-balancing mechanism of the instance of application servers.

11. An article of manufacture comprising:

an system-readable medium providing instructions that, when executed by an apparatus, cause the apparatus to

start a debug node from a remote node, wherein the debug node is one of a plurality of nodes within an instance of application servers;

confirm that the debug node has been isolated from a messaging service of the instance of application servers;

debug an application on the debug node from the remote node; and

stop the debug node from the remote node.

12. The article of manufacture of claim 11, wherein the instructions that, when executed by the apparatus, cause the apparatus to start a debug node from the remote node further cause the apparatus to

isolate the debug node from a load-balancing mechanism of the instance of application servers.