Skip to content

znifeng/remote-debug-agent

 
 

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

36 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

remote-debug-agent

A java agent which allows you to debug your web application remotely. It's very useful in integration tests.
Go to wiki

How to use:

Add this agent to your application's JAVA_OPTS, do testing actions(click a button or invoke an interface) normally, send a request to the custom port, and get debug information of the program that just ran. Here are the details:

From source code: cd ${project dir}, type command gradle jar, you will find all binary files in ${project dir}/agent/build/libs.
From binary files: put all jar files to any directory you want, add -javaagent:${directory above}/remote-debug-agent.jar=includes=com.foo.bar,apiport=8098 to your web application's JAVA_OPTS. (e.g. if you use tomcat as middleware, you can add this option in catalina.sh) Then start your web application, the agent will provide service in port 8098. This is your debugging interface.

Now you can debug your program remotely. For example, a button in GUI sends a request and invokes a method in com.foo.bar.SomeClass. Before clicking the button, send another request with url http://ip:8098/trace/start. Then click the button. Last, send a http://ip:8098/trace/list request, and the agent will return you debug information that contains what methods you invoked just now, what are the parameters and return value, cost time, even covered code lines.
A specific example likes:

[{
	"coverage": "[11,13][16,16]",
	"cost time": 0,
	"method": "java.lang.String com.github.rdagent.test.WebappHandler.handle()",
	"calls": [{
		"coverage": "[21,21][24,24]",
		"cost time": 0,
		"method": "boolean com.github.rdagent.test.WebappHandler.largeThanHalf(double)",
		"parameters": ["0.24444334899195885"],
		"return value": "0"
	}],
	"return value": "random number( 0.24444334899195885 ) is little than half"
}]

The example is in the test directory of this project.

For now, this agent supports some popular frameworks:

  • Frameworks and middlewares that use standard java servlet, like Spring, Tomcat and so on.
  • Struts2
  • Dubbo
  • Rabbitmq
  • Groovy Grails(yes, this agent supports other JVM languages)
  • Scala Play

Of course, you can use this agent in your local java program. It collects debug information and dumps them into a file after the main thread stoped.

Advance Usage

How to make this agent be compatible with more frameworks
I also have provided an easy way to support more frameworks(based on HttpServlet). For example, you have a web application that uses com.foo.bar.MyServlet as core frame. To use this agent in your application, just write a class extends com.github.rdagent.transformer.handler.DefaultServletAdatper, override injectClassNameList() method, make it return a List contains String value "com.foo.bar.MyServlet". Pack this class into a jar file, put it beside remote-debug-agent.jar, and done. You have already been able to debug your application remotely.

How to use it in the internet environment
By default, this agent uses the client's IP address as threads' identification to distinguish different invokers, so that many testers can debug remotely in the integration environment at the same time. But if you work in the internet environment or can't fix your IP address for any reason, this default way may not be enough. Like How to make this agent be compatible with more frameworks chapter, you can easily solve this problem by extending DefaultServletAdatper too. Override extractIdentity() method and use getHttpXXX(e.g. getHttpHeader()) method to get other information in the request, you can use any String as the thread's identification.
* Scala Play doesn't use servlet architecture, and I haven't provided any easy way to obtain custom identification yet.

About sql and jdbc driver
You can use http://ip:8098/trace/list?sql=true to get what SQL was excuted by a method. This function depends on which jdbc driver you use. By default, the agent supports oracle and mysql database. If you use other databases, you have to do a little development. Like above chapters, you just need to write a class extends com.github.rdagent.transformer.handler.DefaultJdbcAdapter, and override filterClassName method. Make it return a List contains the prefix of your jdbc driver's package, like "com.mysql", "oracle.jdbc" and son on (E.g. if you use PostgreSql, you should return "org.postgresql". You can unzip your jdbc driver's jar file to check the prefix of package). That's all you need to do for supporting your own database.

About

a useful java agent for integration testing

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Languages

  • Java 100.0%