build-jms-point-to-point-test-plan.html 18.3 KB
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 399 400 401 402 403 404 405 406 407 408 409 410 411 412 413 414 415 416 417 418 419 420 421 422 423 424 425 426 427 428 429 430 431 432 433 434 435 436 437 438 439 440 441 442 443 444 445 446 447 448 449 450 451 452 453 454 455 456 457 458 459 460 461 462 463 464 465 466 467 468 469 470 471 472 473 474 475 476 477 478 479 480
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<!--
   Licensed to the Apache Software Foundation (ASF) under one or more
   contributor license agreements.  See the NOTICE file distributed with
   this work for additional information regarding copyright ownership.
   The ASF licenses this file to You under the Apache License, Version 2.0
   (the "License"); you may not use this file except in compliance with
   the License.  You may obtain a copy of the License at

       http://www.apache.org/licenses/LICENSE-2.0

   Unless required by applicable law or agreed to in writing, software
   distributed under the License is distributed on an "AS IS" BASIS,
   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
   See the License for the specific language governing permissions and
   limitations under the License.
-->

<!-- start the processing -->
<html>
<head>
<link rel="stylesheet" type="text/css" href="../../docs/css/style.css"/>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8"/>

<title>Apache JMeter - User's Manual: Building a JMS (Java Messaging Service) Point-to-Point Test Plan</title>
<style>
  .code { font-weight: bold; }
</style>
</head>

<body bgcolor="#ffffff" text="#000000" link="#525D76">
<table border="0" cellspacing="0">
<tr>
<td align="left">
<a href="http://www.apache.org"><img style="margin: 0px 30px 0px 0px" title="Apache Software Foundation" width="261" height="106" src="../../docs/images/asf-logo.png" border="0"/></a>
</td>
<td align="right">
<a href="http://jmeter.apache.org/"><img width="259" height="88" src="../../docs/images/jmeter.png" alt="Apache JMeter" title="Apache JMeter" border="0"/></a>
</td>
</tr>
</table>
<table border="0" cellspacing="4">
<tr><td>
<hr noshade size="1"/>
</td></tr>
<tr>
<td align="left" valign="top">
<table>
<tr>
<td bgcolor="#525D76">
<div align="right"><a href="index.html"><font size=-1 color="#ffffff" face="arial,helvetica,sanserif">Index</font></a></div>
</td>
<td bgcolor="#525D76">
<div align="right"><a href="build-jms-topic-test-plan.html"><font size=-1 color="#ffffff" face="arial,helvetica,sanserif">Next</font></a></div>
</td>
<td bgcolor="#525D76">
<div align="right"><a href="build-ws-test-plan.html"><font size=-1 color="#ffffff" face="arial,helvetica,sanserif">Prev</font></a></div>
</td>
</tr>
</table>
<br>
<table border="0" cellspacing="0" cellpadding="2" width="100%">
<tr><td bgcolor="#525D76">
<font color="#ffffff" face="arial,helvetica,sanserif">
<a name="building"><strong>10. Building a JMS Point-to-Point Test Plan</strong></a></font>
</td></tr>
<tr><td>
<blockquote>
<p>
<table border="1" bgcolor="#bbbb00" width="50%" cellspacing="0" cellpadding="2">
<tr><td>
            Make sure the required jar files are in JMeter's <tt class="code">lib</tt> directory. If they are not, shutdown JMeter,
            copy the jar files over and restart JMeter. 
            See <a href="get-started.html#libraries_activemq">Getting Started</a> for details.
        </td></tr>
</table>
</p>
<p>In this section, you will learn how to create a
                <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.
To construct the Test Plan, you will use the
following elements:
                <a href="test_plan.html#thread_group">Thread Group</a>,
                <a href="../usermanual/component_reference.html#JMS_Point-to-Point">JMS Point-to-Point</a>, and
                <a href="../usermanual/component_reference.html#Graph_Results">Graph Results</a>.
            </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="get-started.html#libraries_activemq">here</a> for the list
of jars provided by ActiveMQ.</p></blockquote>
</p>
</td></tr>
<tr><td><br></td></tr>
</table>
<table border="0" cellspacing="0" cellpadding="2" width="100%">
<tr><td bgcolor="#525D76">
<font color="#ffffff" face="arial,helvetica,sanserif">
<a name="adding_threadgroup"><strong>10.1 Adding a Thread Group</strong></a></font>
</td></tr>
<tr><td>
<blockquote>
<p>The first step you want to do with every JMeter Test Plan is to add a
                <a href="test_plan.html#thread_group">Thread Group</a> element.  The Thread Group tells
JMeter the number of users you want to simulate, how often the users should send
requests, and the how many requests they should send.
            </p><p>Go ahead and add the ThreadGroup element by first selecting the Test Plan,
clicking your right mouse button to get the  <span class="menuchoice">
 <span class="guimenuitem">Add</span>  </span>
 menu, and then select
 <span class="menuchoice">
 <span class="guimenuitem">Add</span>&nbsp;&rarr;&nbsp;<span class="guimenuitem">ThreadGroup</span>  </span>
.</p><p>You should now see the Thread Group element under Test Plan.  If you do not
see the element, then &quot;expand&quot; the Test Plan tree by clicking on the
Test Plan element.</p><p>Next, you need to modify the default properties.  Select the Thread Group element
in the tree, if you have not already selected it. You should now see the Thread
Group Control Panel in the right section of the JMeter window (see Figure 10.1
below)</p><table border="0" cellspacing="0" cellpadding="0"><tr><td><img  src="../../docs/images/screenshots/webtest/threadgroup.png"/><br>
<font size="-1">
Figure 10.1. Thread Group with Default Values</font></td></tr></table>
<p>Start by providing a more descriptive name for our Thread Group. In the name
field, enter <tt class="code">Point-to-Point</tt>.</p><p>Next, increase the number of users (called threads) to <tt class="code">5</tt>.</p><p>In the next field, the Ramp-Up Period, leave 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
5 users and a 5 second Ramp-Up Period, then the delay between starting users
would be 1 second (5 users / 5 seconds = 1 user per second).  If you set the
value to 0, then JMeter will immediately start all of your users.</p><p>Clear the checkbox labeled &quot;<tt class="code">Forever</tt>&quot;, and enter a value of <tt class="code">4</tt> in the Loop
Count field.  This property tells JMeter how many times to repeat your test.
If you enter a loop count value of <tt class="code">0</tt>, then JMeter will run your test only
once. To have JMeter repeatedly run your Test Plan, select the <tt class="code">Forever</tt>
checkbox.</p><p>
<table border="1" bgcolor="#bbbb00" width="50%" cellspacing="0" cellpadding="2">
<tr><td>In most applications, you have to manually accept
changes you make in a Control Panel.  However, in JMeter, the Control Panel
automatically accepts your changes as you make them.  If you change the
name of an element, the tree will be updated with the new text after you
leave the Control Panel (for example, when selecting another tree element).</td></tr>
</table>
</p>
</blockquote>
</p>
</td></tr>
<tr><td><br></td></tr>
</table>
<table border="0" cellspacing="0" cellpadding="2" width="100%">
<tr><td bgcolor="#525D76">
<font color="#ffffff" face="arial,helvetica,sanserif">
<a name="adding_point_to_point_sampler"><strong>10.2 Adding JMS Point-to-Point Sampler</strong></a></font>
</td></tr>
<tr><td>
<blockquote>
<p>Start by adding the sampler <a href="../usermanual/component_reference.html#JMS_Point-to-Point">JMS Point-to-Point</a>
to the Point-to-Point element 
( <span class="menuchoice">
 <span class="guimenuitem">Add</span>&nbsp;&rarr;&nbsp;<span class="guimenuitem">Sampler</span>&nbsp;&rarr;&nbsp;<span class="guimenuitem">JMS Point-to-Point</span>  </span>
).
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><p>
                <table>
<tr>
<td bgcolor="#039acc"   valign="top" align="left">
<font color="#000000" size="-1" face="arial,helvetica,sanserif">
Name
</font>
</td>
<td bgcolor="#039acc"   valign="top" align="left">
<font color="#000000" size="-1" face="arial,helvetica,sanserif">
Value
</font>
</td>
<td bgcolor="#039acc"   valign="top" align="left">
<font color="#000000" size="-1" face="arial,helvetica,sanserif">
Description
</font>
</td>
</tr>
<tr>
<td bgcolor="#039acc" colspan="3"  valign="top" align="left">
<font color="#000000" size="-1" face="arial,helvetica,sanserif">
JMS Resources
</font>
</td>
</tr>
<tr>
<td bgcolor="#a0ddf0" colspan="1"  valign="top" align="left">
<font color="#000000" size="-1" face="arial,helvetica,sanserif">
QueueConnectionFactory</font>
</td>
<td bgcolor="#a0ddf0" colspan="1"  valign="top" align="left">
<font color="#000000" size="-1" face="arial,helvetica,sanserif">
<tt class="code">ConnectionFactory</tt></font>
</td>
<td bgcolor="#a0ddf0" colspan="1"  valign="top" align="left">
<font color="#000000" size="-1" face="arial,helvetica,sanserif">
 This is the default JNDI entry for the connection factory within ActiveMQ.</font>
</td>
</tr>
<tr>
<td bgcolor="#a0ddf0" colspan="1"  valign="top" align="left">
<font color="#000000" size="-1" face="arial,helvetica,sanserif">
JNDI Name Request Queue</font>
</td>
<td bgcolor="#a0ddf0" colspan="1"  valign="top" align="left">
<font color="#000000" size="-1" face="arial,helvetica,sanserif">
<tt class="code">Q.REQ</tt></font>
</td>
<td bgcolor="#a0ddf0" colspan="1"  valign="top" align="left">
<font color="#000000" size="-1" face="arial,helvetica,sanserif">
This is equal to the JNDI name defined in the JNDI properties.</font>
</td>
</tr>
<tr>
<td bgcolor="#a0ddf0" colspan="1"  valign="top" align="left">
<font color="#000000" size="-1" face="arial,helvetica,sanserif">
JNDI Name Reply Queue</font>
</td>
<td bgcolor="#a0ddf0" colspan="1"  valign="top" align="left">
<font color="#000000" size="-1" face="arial,helvetica,sanserif">
<tt class="code">Q.RPL</tt></font>
</td>
<td bgcolor="#a0ddf0" colspan="1"  valign="top" align="left">
<font color="#000000" size="-1" face="arial,helvetica,sanserif">
This is equal to the JNDI name defined in the JNDI properties.</font>
</td>
</tr>
<tr>
<td bgcolor="#039acc" colspan="3"  valign="top" align="left">
<font color="#000000" size="-1" face="arial,helvetica,sanserif">
Message Properties
</font>
</td>
</tr>
<tr>
<td bgcolor="#a0ddf0" colspan="1"  valign="top" align="left">
<font color="#000000" size="-1" face="arial,helvetica,sanserif">
Communication Style</font>
</td>
<td bgcolor="#a0ddf0" colspan="1"  valign="top" align="left">
<font color="#000000" size="-1" face="arial,helvetica,sanserif">
<tt class="code">Request Response</tt></font>
</td>
<td bgcolor="#a0ddf0" colspan="1"  valign="top" align="left">
<font color="#000000" size="-1" face="arial,helvetica,sanserif">
This means that you need at least a service running outside of JMeter and that will respond to the requests. 
                        This service must listen to the Request Queue and send messages to the queue referenced by the <tt class="code">message.getJMSReplyTo()</tt></font>
</td>
</tr>
<tr>
<td bgcolor="#a0ddf0" colspan="1"  valign="top" align="left">
<font color="#000000" size="-1" face="arial,helvetica,sanserif">
Content</font>
</td>
<td bgcolor="#a0ddf0" colspan="1"  valign="top" align="left">
<font color="#000000" size="-1" face="arial,helvetica,sanserif">
<tt class="code">test</tt></font>
</td>
<td bgcolor="#a0ddf0" colspan="1"  valign="top" align="left">
<font color="#000000" size="-1" face="arial,helvetica,sanserif">
This is just the content of the message.</font>
</td>
</tr>
<tr>
<td bgcolor="#a0ddf0" colspan="1"  valign="top" align="left">
<font color="#000000" size="-1" face="arial,helvetica,sanserif">
JMS Properties</font>
</td>
<td bgcolor="#a0ddf0" colspan="1"  valign="top" align="left">
<font color="#000000" size="-1" face="arial,helvetica,sanserif">
&nbsp;
</font>
</td>
<td bgcolor="#a0ddf0" colspan="1"  valign="top" align="left">
<font color="#000000" size="-1" face="arial,helvetica,sanserif">
Nothing needed for ActiveMQ.</font>
</td>
</tr>
<tr>
<td bgcolor="#039acc" colspan="3"  valign="top" align="left">
<font color="#000000" size="-1" face="arial,helvetica,sanserif">
JNDI Properties
</font>
</td>
</tr>
<tr>
<td bgcolor="#a0ddf0" colspan="1"  valign="top" align="left">
<font color="#000000" size="-1" face="arial,helvetica,sanserif">
InitialContextFactory</font>
</td>
<td bgcolor="#a0ddf0" colspan="1"  valign="top" align="left">
<font color="#000000" size="-1" face="arial,helvetica,sanserif">
<tt class="code">org.apache.activemq.jndi.ActiveMQInitialContextFactory</tt></font>
</td>
<td bgcolor="#a0ddf0" colspan="1"  valign="top" align="left">
<font color="#000000" size="-1" face="arial,helvetica,sanserif">
The standard InitialContextFactory for ActiveMQ</font>
</td>
</tr>
<tr>
<td bgcolor="#039acc" colspan="3"  valign="top" align="left">
<font color="#000000" size="-1" face="arial,helvetica,sanserif">
 Properties
</font>
</td>
</tr>
<tr>
<td bgcolor="#a0ddf0" colspan="1"  valign="top" align="left">
<font color="#000000" size="-1" face="arial,helvetica,sanserif">
<tt class="code">queue.Q.REQ</tt></font>
</td>
<td bgcolor="#a0ddf0" colspan="1"  valign="top" align="left">
<font color="#000000" size="-1" face="arial,helvetica,sanserif">
<tt class="code">example.A</tt></font>
</td>
<td bgcolor="#a0ddf0" colspan="1"  valign="top" align="left">
<font color="#000000" size="-1" face="arial,helvetica,sanserif">
This defines a JNDI name <tt class="code">Q.REQ</tt> for the request queue that points to the queue <tt class="code">example.A</tt></font>
</td>
</tr>
<tr>
<td bgcolor="#a0ddf0" colspan="1"  valign="top" align="left">
<font color="#000000" size="-1" face="arial,helvetica,sanserif">
<tt class="code">queue.Q.RPL</tt></font>
</td>
<td bgcolor="#a0ddf0" colspan="1"  valign="top" align="left">
<font color="#000000" size="-1" face="arial,helvetica,sanserif">
<tt class="code">example.B</tt></font>
</td>
<td bgcolor="#a0ddf0" colspan="1"  valign="top" align="left">
<font color="#000000" size="-1" face="arial,helvetica,sanserif">
This defines a JNDI name <tt class="code">Q.RPL</tt> for the reply queue that points to the queue <tt class="code">example.B</tt></font>
</td>
</tr>
<tr>
<td bgcolor="#039acc" colspan="3"  valign="top" align="left">
<font color="#000000" size="-1" face="arial,helvetica,sanserif">
Provider URL
</font>
</td>
</tr>
<tr>
<td bgcolor="#a0ddf0" colspan="1"  valign="top" align="left">
<font color="#000000" size="-1" face="arial,helvetica,sanserif">
Provider URL</font>
</td>
<td bgcolor="#a0ddf0" colspan="1"  valign="top" align="left">
<font color="#000000" size="-1" face="arial,helvetica,sanserif">
<tt class="code">tcp://localhost:61616</tt></font>
</td>
<td bgcolor="#a0ddf0" colspan="1"  valign="top" align="left">
<font color="#000000" size="-1" face="arial,helvetica,sanserif">
This defines the URL of the ActiveMQ messaging system.</font>
</td>
</tr>
</table>

            </p></blockquote>
</p>
</td></tr>
<tr><td><br></td></tr>
</table>
<table border="0" cellspacing="0" cellpadding="2" width="100%">
<tr><td bgcolor="#525D76">
<font color="#ffffff" face="arial,helvetica,sanserif">
<a name="adding_listener"><strong>10.3 Adding a Listener to View Store the Test Results</strong></a></font>
</td></tr>
<tr><td>
<blockquote>
<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 JMS requests in a file and presenting
a visual model of the data.
            </p><p>Select the Thread Group element and add a
                <a href="../usermanual/component_reference.html#Graph_Results">Graph Results</a> listener 
( <span class="menuchoice">
 <span class="guimenuitem">Add</span>&nbsp;&rarr;&nbsp;<span class="guimenuitem">Listener</span>&nbsp;&rarr;&nbsp;<span class="guimenuitem">Graph Results</span>  </span>
).  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
Browse button and browse to a directory and then enter a filename.
            </p><table border="0" cellspacing="0" cellpadding="0"><tr><td><img width='915' height='686' src="../../docs/images/screenshots/graph_results.png"/><br>
<font size="-1">
Figure 10.2. Graph Results Listener</font></td></tr></table>
</blockquote>
</p>
</td></tr>
<tr><td><br></td></tr>
</table>
<br>
<table>
<tr>
<td bgcolor="#525D76">
<div align="right"><a href="index.html"><font size=-1 color="#ffffff" face="arial,helvetica,sanserif">Index</font></a></div>
</td>
<td bgcolor="#525D76">
<div align="right"><a href="build-jms-topic-test-plan.html"><font size=-1 color="#ffffff" face="arial,helvetica,sanserif">Next</font></a></div>
</td>
<td bgcolor="#525D76">
<div align="right"><a href="build-ws-test-plan.html"><font size=-1 color="#ffffff" face="arial,helvetica,sanserif">Prev</font></a></div>
</td>
</tr>
</table>
</td>
</tr>
<tr><td>
<hr noshade size="1"/>
</td></tr>
<tr>
<td>
<table width=100%>
<tr>
<td>
<font color="#525D76" size="-1"><em>
Copyright &copy; 1999-2017, Apache Software Foundation
</em></font>
</td>
<td align="right">
<font color="#525D76" size="-1"><em>
$Id: build-jms-point-to-point-test-plan.xml 1767315 2016-10-31 15:52:25Z pmouawad $
</em></font>
</td>
</tr>
<tr><td colspan="2">
<div align="center"><font color="#525D76" size="-1">
Apache, Apache JMeter, JMeter, the Apache feather, and the Apache JMeter logo are
trademarks of the Apache Software Foundation.
</font>
</div>
</td></tr>
</table>
</td>
</tr>
</table>
</body>
</html>
<!-- end the processing -->