Method and System for Creating a Logical View Out of Remote Method Invocations

1. A method for debugging an application on a source node, comprising: creating a first Remote Method Invocation (RMI) by a first application executing on the source node; associating, by a first debugger executing on the source node, a first debug object with the first RMI; sending the first RMI with the first debug object to a first target node; determining, using the first debug object, that the first target node supports debugging; instantiating, in response to the determination, a second debugger on the first target node; executing, by a second application on the first target node, the first RMI; gathering, by the second debugger, debugging information during execution of the first RMI on the first target node; receiving debugging information from the first target node; and outputting a logical view of a chain of the first RMI.

2. The method of claim 1 , further comprising: sending the debugging information to the source node using information in the first debug object.

3. The method of claim 2 , further comprising: processing the debugging information by the first debugger.

4. The method of claim 1 , further comprising: determining whether the first RMI comprises an argument; and wrapping the argument with a debug object wrapper to obtain the first debug object.

5. The method of claim 1 , further comprising: determining whether the first RMI comprises an argument; and creating the first debug object without the argument.

6. The method of claim 1 , further comprising: creating a second RMI by the second application at the first target node; associating a second debug object with the second RMI; and sending the second RMI with the second debug object to a second target node.

7. The method of claim 6 , further comprising: instantiating a third debugger on the second target node in response to receiving the second debug object; executing the second RMI on the second target node; gathering second debugging information by the third debugger during execution of the second RMI on the second target node; and sending the second debugging information to the first target node using information in the second debug object.

8. The method of claim 1 , wherein the first debug object comprises a debugging session identifier.

9. The method of claim 1 , wherein the first debug object comprises a virtual machine identifier and a thread identifier.

10. A system for debugging an application, comprising: a source node comprising: a first processor, a first application executing on the first processor and configured to create a first Remote Method Invocation (RMI), and a first debugger, when executed on the first processor, is configured to: associate a first debug object with the first RMI, send the first RMI with the first debug object to a first target node, receive debugging information from the first target node, and output a logical view of a chain of the first RMI; and the first target node configured to receive the first RMI and the first debug object and comprising: a second processor, a second application executing on the second processor and configured to execute the first RMI, and a second debugger instantiated in response to receiving the first debug object and configured to gather debugging information during execution of the first RMI and send the debugging information to the first debugger.

11. The system of claim 10 , wherein the second debugger is further configured to: intercept a second RMI from the second application on the first target node; determine whether the second RMI comprises an argument; wrap the argument with a debug object wrapper to obtain the second debug object if the second RMI comprises the argument; create the second debug object without the argument if the second RMI does not comprise the argument; and send the second RMI with the debug object to a second target node.

12. The system of claim 11 , wherein the second debugger is further configured to: receive debugging information from the second target node.

13. The system of claim 12 , wherein the second debugger is further configured to: send debugging information received from the second target node to the source node.

14. The system of claim 10 , wherein the first debug object comprises a debugging session identifier.

15. The system of claim 10 , wherein the first debug object comprises a virtual machine identifier and a thread identifier.

16. A tangible computer readable medium comprising software instructions for debugging an application on a source node comprising software instructions for: creating a first Remote Method Invocation (RMI) by a first application executing on the source node; associating, by a first debugger executing on the source node, a first debug object with the first RMI; sending the first RMI with the first debug object to a first target node; determining, using the first debug object, that the first target node supports debugging; instantiating, in response to the determination, a second debugger on the first target node; executing, by a second application on the first target node, the first RMI; gathering, by the second debugger, debugging information during execution of the first RMI on the first target node; receiving debugging information from the first target node; and outputting a logical view of a chain of the first RMI.

17. The tangible computer readable medium of claim 16 , further comprising: sending the debugging information to the source node using information in the first debug object.

18. The tangible computer readable medium of claim 16 , further comprising: determining whether the first RMI comprises an argument; wrapping the argument with a debug object wrapper to obtain the first debug object if the first RMI comprises an argument; and creating the first debug object without the argument.