Page History

Test ID

Test Steps

Expected Result

LOG-0

Select the LoggingManagement node for the server in the Qpid Connections tree.

The LoggingManagement MBean is opened in the MBean view, showing the Runtime Options tab.

LOG-1

Double click the org.apache.qpid LoggerName

The Set Runtime Logger Level dialog opens.

LOG-1.1

Select a Level of ERROR from the combo box and click ok.

The org.apache.qpid Logger and all those below it beginning with org.apache.qpid (except org.apache.qpid.server.queue.AMQQueueMBean) are now shown at ERROR Level in the table.

LOG-2

Press the Edit button in the Runtime RootLogger Level area.

The Set Runtime RootLogger Level dialog opens.

LOG-2.1

Select a Level of WARN from the combo box and click ok.

The Level is updated to WARN, plus any Logger (except qpid.message) without a highlighted blue Logger as a prefix inherits from the RootLogger and will also change to WARN Level in the table.

LOG-3

Select the org.apache.qpid.server.Main LoggerName and press the Edit Selected Logger button.

The Set Runtime Logger Level dialog opens.

LOG-3.1

Select a Level of WARN from the combo box and click ok.

The org.apache.qpid.server.Main Logger is now shown at WARN Level in the table, all others remain unchanged.

Test ID

Test Steps

Expected Result

CONN-0

Select the Connections node for the test VirtualHost in the Qpid Connections tree.

The Connections selection screen is opened in the MBean view, with no entries in the table.

CONN-0.1

Run the ping_sender.sh utility script, but do not press a key to exit the script when the sending is complete.

After a refresh interval, two connections from the IP address of the machine ping_sender.sh was run will appear in the table

CONN-1

Double-click the first connection entry in the table.

The connection MBean opens in the MBean View, showing the Attributes tab.

CONN-1.1

Select the Operations tab in the connection MBean view.

The Operations tab opens, listing channel 1 in the table, which is Transactional, has 0 unacked messages, and no (null) default queue.

CONN-2

Select the channel entry in the table.

The Commit and Rollback Transactions buttons activate as the selected channel is transactional.

CONN-3

Press the Close Connection button and confirm the action.

The connection is closed, the main view is cleared and a dialog opens to inform the user that the open MBean was unregistered from the server.