Page History

...

1. Running Broker
2. Client with a subscription.
3. The subscription is then closed.
   Output:

   No Format
   <date> SUB-1002 : Close

   Validation Steps:
4. The SUB ID is correct
5. There must be a SUB-1001 Create message preceding this message
6. This must be the last message from the given Subscription

Performance Test

...

Case

In addition to the performance test suite an additional performance test needs to be written that can be run with this new logging enabled and disabled so that an attempt at quantifying any impact can be made.

Test Structure

The test should perform the following actions:

1. Connect a client
2. Create a channel/JMS Session
3. Create an exchange
4. Create a queue
5. Bind the exchange and queue
6. Create a subscriber on the queue
7. Close the Subscriber
8. Close the Session
9. Close the Connection

This will ensure that we hit as many of the new logging routines as possible.
If this test should also be run prior to any code changes so that our current performance can be recorded.

Risks

Testing of this nature is dependant on a lot of items that are out of the tests control such as:

1. CPU scheduling
2. CPU performance
3. Load
4. GC

As a result the test cannot be guaranteed to produce the same results each time. To mitigate this risk running the test in a loop an reporting an average value of 10-20 runs should provide a more stable response.
Leaving the broker startup/shutdown out of the test loop will help improve the tests performance and repeatability.TBC