1
This text covers how to run the spring http performance benchmark test.
3
This test can not be run automatically within remoting testsuite since requires deploying a web app.
4
So in order to run this test, will have to do it manually. First step is to get a web container to deploy within.
5
Any web container will do, but I have been using Tomcat 5.5.17. Am also using Spring framework 1.2.8.
9
1. Run remoting build with tests.jars target. This will build the jboss-remoting.jar and jboss-remoting-tests.jar
10
that will be needed within web deployment file.
11
2. Create web deployment file. This currently has to be done manually. Create new directory and copy
12
src/tests/org/jboss/test/remoting/performance/spring/http/web/WEB-INF into this new directory. Should
13
then have WEB-INF directory with contents applicationContext.xml, remoting-servlet.xml, and web.xml under
14
root directory. Now create a lib directory under the WEB-INF directory.
15
Copy the jboss-remoting.jar and jboss-remoting-tests.jar into the lib directory. Also copy all the jars under
16
the remoting project's lib/spring directory into this new lib directory.
17
Will also need to copy /lib/oswego-concurrent/lib/concurrent.jar into the lib directory.
18
Now zip up the WEB-INF directory into a file called remoting.war. This will be the web deployment file.
19
Its contents should be:
23
- applicationContext.xml
24
- remoting-servlet.xml
28
- jboss-remoting-tests.jar
41
3. Deploy remoting.war to web container (i.e. copy to apache-tomcat-5.5.17\webapps directory).
42
4. Start web container (i.e. apache-tomcat-5.5.17\bin\startup.bat/sh)
43
5. Run the benchmark client. This can be done by running ant target "tests.performance.sequence.spring_http".
44
The following system properties are used:
46
- perf.seq.numofclients
48
- perf.seq.payloadsize