DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=41774>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=41774 Summary: User doc _Building a JMS point-to-point test_ has mistakes Product: JMeter Version: 2.2 Platform: All OS/Version: All Status: NEW Severity: minor Priority: P3 Component: Main AssignedTo: [email protected] ReportedBy: [EMAIL PROTECTED] This user document has a few confusing items that make getting started rather difficult. It looks like this doc was derived from another one and not completely cleaned up. Proposed patch shown below (I am not a committer). Thanks for listening, hope you'll find this usable. -- Index: C:/Proj/eclipse-workspace/jmeter/xdocs/usermanual/build-jms-point-to-point-test-plan.xml =================================================================== --- C:/Proj/eclipse-workspace/jmeter/xdocs/usermanual/build-jms-point-to-point-test-plan.xml (revision 515246) +++ C:/Proj/eclipse-workspace/jmeter/xdocs/usermanual/build-jms-point-to-point-test-plan.xml (working copy) @@ -28,17 +28,19 @@ <a href="build-test-plan.html">Test Plan</a> to test a JMS Point-to-Point messaging solution. The setup of the test is 1 threadgroup with 5 threads sending 4 messages each through a request queue. A fixed reply queue will be used for monitoring the reply messages. -each one to 10 iterations. To construct the Test Plan, you will use the +To construct the Test Plan, you will use the following elements: <a href="test_plan.html#thread_group">Thread Group</a>, <complink name="JMS Point-to-Point"/>, and <complink name="Graph Results"/>. </p> - <p>General notes on JMS. There are currently two JMS samplers. One uses JMS topics -and the other uses queues. Topic messages are commonly know as pub/sub messaging. -It is generally used in cases where a message is publish by a producer and -consumed by multiple subscribers. </p> + <p>General notes on JMS: There are currently two JMS samplers. One uses JMS topics +and the other uses queues. Topic messages are commonly known as pub/sub messaging. +Topic messaging is generally used in cases where a message is published by a producer and +consumed by multiple subscribers. A JMS sampler needs the JMS implementation jar files; +for example, from Apache ActiveMQ. See <a href="#libraries_activemq">here</a> for the list +of jars provided by ActiveMQ 3.0.</p> </section> @@ -70,7 +72,7 @@ <p>Next, increase the number of users (called threads) to 5.</p> - <p>In the next field, the Ramp-Up Period, leave the the default value of 0 + <p>In the next field, the Ramp-Up Period, set the value to 0 seconds. This property tells JMeter how long to delay between starting each user. For example, if you enter a Ramp-Up Period of 5 seconds, JMeter will finish starting all of your users by the end of the 5 seconds. So, if we have @@ -102,7 +104,7 @@ </note> <p>Start by adding the sampler <complink name="JMS Point-to-Point"/> -to the Jakarta Users element (Add --> Sampler --> JMS Point-to-Point). +to the Point-to-Point element (Add --> Sampler --> JMS Point-to-Point). Then, select the JMS Point-to-Point sampler element in the tree. In building the example a configuration will be provided that works with ActiveMQ 3.0. </p> @@ -163,9 +165,9 @@ <th colspan="3"> Properties</th> </tr> <tr> - <td colspan="1">brokerURL</td> + <td colspan="1">providerURL</td> <td>tcp://localhost:61616</td> - <td>This defines the url of the active mq messaging system.</td> + <td>This defines the URL of the active mq messaging system.</td> </tr> <tr> <td>queue.Q.REQ</td> @@ -185,11 +187,11 @@ <section name="11.3 Adding a Listener to View Store the Test Results" anchor="adding_listener"> <p>The final element you need to add to your Test Plan is a <a href="component_reference.html#listeners">Listener</a>. This element is -responsible for storing all of the results of your HTTP requests in a file and presenting +responsible for storing all of the results of your JMS requests in a file and presenting a visual model of the data. </p> - <p>Select the Jakarta Users element and add a + <p>Select the Test Plan element and add a <complink name="Graph Results"/> listener (Add --> Listener --> Graph Results). Next, you need to specify a directory and filename of the output file. You can either type it into the filename field, or select the -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
