FUSE test plan

Summary

This is a test plan which should be carried out when we build a new FUSE release. It consists of a set of tests that should be run against a network of brokers. They mostly use the command line tools in msg-admin-utils rpm.

Tests

Test A : Non-durable topic subscribers across the network.

Test Configuration

This tests that we can create a topic, and have subscribers on all brokers in the network. The brokers should deliver all messages successfully without hanging.

The brokers should be configured with 512M memory and 1G store. Delete log files in /var/log/activemq. Add into broker configuration deleteAllMessagesOnStartup="true". Set wrapper.java.maxmemory to 1024mb (/etc/activemq/wrapper.conf).

Two stores to test:

   <kahaPersistenceAdapter directory="${activemq.base}/data/kahadb"/>

   <amqPersistenceAdapter directory="${activemq.base}/data/amq"/>

We should use the egee-backbone-conf-VTB topology (i.e. 3 brokers, each with uni-directional network connection to the other two brokers).

Procedure

1. start a consumer on each brokers:

> msg-test-consumer -b <BROKER> -p 6163 /topic/test.testA 

1. Start a single producer on one broker

> msg-test-producer -b <BROKER_1> -p 6163 -n 1000000 /topic/test.testA

1. Monitor system memory and store usage - check that if the store usage fills the broker does not hang.

Performance tests

Performance tests of KahaDB & AMQ Persistence in AMQ5.3.1 and 5.4.0

• see https://twiki.cern.ch/twiki/bin/view/Main/KSAMQTestPerf