Page History

...

These messages should only occur during startup. The tests need to verify the order of messages. In the case of the BRK-1002 and BRK-1003 the respective ports should only be available between the two log messages.

Broker Startup

testBrokerStartupConfiguration

...

1. The BRK ID is correct
2. This occurs after the BRK-1001 startup message
3. This must be the last message the broker prints after startup. Currently, if there is no further interaction with the broker then there should be no more logging.

Broker Shutdown

testBrokerShutdownListeningTCPDefault

...

1. The BRK ID is correct
2. This is the last message the broker will log.

Management Console Test Suite

The Management Console test suite validates that the follow log messages as specified in the Functional Specification.

This suite of tests validate that the management console messages occur in correctly and according to the following format:

MNG-1001 : Startup
MNG-1002 : Starting : <service> : Listening on port <Port>
MNG-1003 : Shuting down : <service> : port <Port>
MNG-1004 : Ready
MNG-1005 : Stopped
MNG-1006 : Using SSL Keystore : <path>

Management Startup

...

testManagementStartupEnabled

...

Description:
Using the startup configuration validate that the managment startup messasge is logged correctly.
Input:
Standard configuration with management enabled
Output:

<date> MNG-1001 : Startup

Constraints:
This is the FIRST message logged by MNG
Validation Steps:

1. The BRK ID is correct
2. This is the FIRST message logged by MNG

...

testManagementStartupDisabled

...

Description:
Verify that when management is disabled in the configuration file the startup message is not logged.
Input:
Standard configuration with management disabled
Output:
NO MNG messages
Validation Steps:

1. Validate that no MNG messages are produced.

...

testManagementStartupRMIRegistry

...

Description:
Using the default configuration validate that the RMI Registry socket is correctly reported as being opened
Input:
The default configuration file
Output:

<date> MESSAGE MNG-1002 : Starting : RMI Registgry : Listening on port 8999

Constraints:
The RMI ConnectorServer and Registry log messages do not have a prescribed order
Validation Steps:

1. The MNG ID is correct
2. The specified port is the correct '8999'

...

testManagementStartupRMIRegistryCustom

...

Description:
Using the default configuration validate that the RMI Registry socket is correctly reported when overridden via the command line.
Input:
The default configuration file and a custom -m value
Output:

<date> MESSAGE MNG-1002 : Starting : RMI Registgry : Listening on port <port>

Constraints:
The RMI ConnectorServer and Registry log messages do not have a prescribed order
Validation Steps:

1. The MNG ID is correct
2. The specified port is as specified on the commandline.

...

testManagementStartupRMIConnectorServer

...

Description:
Using the default configuration validate that the RMI ConnectorServer socket is correctly reported as being opened
Input:
The default configuration file
Output:

<date> MESSAGE MNG-1002 : Starting : RMI ConnectorServer : Listening on port 9099

Constraints:
The RMI ConnectorServer and Registry log messages do not have a prescribed order
Validation Steps:

1. The MNG ID is correct
2. The specified port is the correct '9099'

...

testManagementStartupRMIConnectorServerCustom

...

Description:
Using the default configuration validate that the RMI Registry socket is correctly reported when overridden via the command line.
Input:
The default configuration file and a custom -m value
Output:

<date> MESSAGE MNG-1002 : Starting : RMI ConnectorServer : Listening on port <port>

Constraints:
The RMI ConnectorServer and Registry log messages do not have a prescribed order
Validation Steps:

1. The MNG ID is correct
2. The specified port is as specified on the commandline.

...

testManagementStartupSSLKeystore

...

Description:
Using the default configuration with SSL enabled for the management port the SSL Keystore path should be reported via MNG-1006
Input:
Management SSL enabled default configuration.
Output:

<date> MESSAGE MNG-1006 : Using SSL Keystore : test_resources/ssl/keystore.jks

Validation Steps:

1. The MNG ID is correct
2. The keystore path is as specified in the configuration

...

testManagementStartupReady

...

Description:
Using the default configuration the final stage of management startup is to report a MNG-1004 Ready message.
Input:
Default broker configuration.
Output:

<date> MESSAGE MNG-1004 : Ready

Validation Steps:

1. The MNG ID is correct
2. There has been a MNG-1001 message
3. There has been at least one MNG-1002 Listenting message
4. No further MNG messages are produced as part of the startup process, i.e. before broker use.

Management Shutdown

...

testManagementShutdownRMIRegistry

...

Description:
Using the default configuration the management RMI Registry will start and so on shutdown it will log that it is shutting down.
Input:
The default configuration file.
Output:

<date> MNG-1003 : Shutting down : RMI Registgry : Listening on port 8999

Validation Steps:

1. The MNG ID is correct
2. The MNG-1004 message has been logged.

...

testManagementShutdownRMIConnectorServer

...

Description:
Using the default configuration the management RMI ConnectorServer will start and so on shutdown it will log that it is shutting down.
Input:
The default configuration file.
Output:

MNG-1003 : Shutting down : RMI ConnectorServer : Listening on port 9099

Validation Steps:

1. The MNG ID is correct
2. The MNG-1004 message has been logged.

...

testManagementShutdownStopped

...

Description:
On final shutdown the management console will report that it has stopped. All MNG logging must be complete before this message is logged.
Input:
The default configuration file.
Output:

MNG-1005 : Stopped

Validation Steps:

1. The MNG ID is correct
2. The MNG-1004 message has been logged.
3. For each MNG-1002 message that was logged a MNG-1003 is also logged before this message.
4. This is the last MNG message reported.

Performance Test Cases

TBC