6.2.0

[6.2.0] - 2019-10-15

Added

• JMX bean can now be pinged to get command status:
  • COMMAND_RECEIVED
  • COMMAND_IN_PROGRESS
  • COMMAND_COMPLETE
  • COMMAND_FAILED
• Added commandId to all SystemEvents
• All Shuttering Executors now implement the ShutteringExecutor interface
• New table in the system database 'system_command_status'

Changed

• All commands now have state that can be queried by the JMX client
• MDC service component logging interceptor
• EventCatchupCommand and IndexerCatchupCommand now both have a common interface: CatchupCommand
• ShutterCommand and UnshutterCommand now both have a common interface: ApplicationShutteringCommand

6.1.2

[6.1.2] - 2019-10-04

Changed

• Storing of Commands whilst shuttered is now idempotent
• Do not shutter the JmsEnvelopeSender when called from the Command-Controller component

6.0.17

[6.0.17] - 2019-10-04

Changed

• Storing of Commands whilst shuttered is now idempotent
• Do not shutter the JmsEnvelopeSender when called from the Command-Controller component

6.1.1

[6.1.1] - 2019-10-01

Added

• Injectable debug logger that logs only if debug logging is set.

6.1.0

[6.1.0] - 2019-09-28

Changed

• All SystemCommandHandler methods now also take a mandatory commandId as a parameter
• SystemCommander JMX bean now returns a unique command id for each command that it runs

6.0.16

[6.0.16] - 2019-09-23

Changed

• Renamed ValidateCatchupCommand to VerifyCatchupCommand
• Added MBeanClientConnectionException to the JMX client classes to show that a connection error occurred

6.0.15

[6.0.15] - 2019-09-19

Added

• New SystemCommands: AddTriggerCommand, RemoveTriggerCommand and ValidateCatchupCommand

Changed

• Updated framework-api to 4.1.0

6.0.14

[6.0.14] - 2019-09-11

Changed

• System commands now run using a ManagedExecutor rather than an asynchronous EJB

6.0.13

[6.0.13] - 2019-09-10

Changed

• SystemCommandStore moved to an interface implemented by DefaultSystemCommandStore. This is to allow stubbing in integration tests

6.0.12

[6.0.12] - 2019-09-08

Changed

• All JMX SystemCommands are now run asynchronously. i.e the call to the JMX bean will return immediately
• The JMX SystemCommandBean now only throws 2 Exceptions
  1. UnsupportedSystemCommandException. If the command is unrecognised by the context.
  2. SystemCommandFailedException. On any other failure. NB. this Exception also contains the stacktrace of the server side exception