Release 9.2.6

Changes

  • JMS Client: Keepalive Missing Threshold at the client now configurable via system property swiftmq.jms.keepalive.missing.threshold. Default is 5.
  • SwiftMQ HA Router: If a "split brain" occures, one HA instance will backup its store and will automatically restart as a STANDBY. More ...

Bugfixes

  • Store Swiftlet: If there is a disk error, it exits but runs through the shutdown hook and may hang here.
  • JMS client: Setting a String message property, a MapMessage or StreamMessage entry to an empty String ("") will return null value on the corresponding getters. Bug was introduced in 9.1.0.
  • AMQP Client/AMQP Swiftlet: nextIncomingId/nextOutgoingId incremented for every message but must be incremented for every transfer frame.
  • AMQP Client: detach frame uses remote handle but must use local handle.

Compatibility

  • Configuration compatible with previous releases: 4.5.0 (routerconfig.xml will be converted on the first startup)
  • Class compatible with previous releases: 5.1.0 (see release notes of release 5.1.0).
  • Message compatible with previous releases: 4.0.0
  • Store compatible with previous releases: 4.0.0
  • Protocol compatible with previous releases: 4.0.0

How to Upgrade

SwiftMQ 9.2.6 defines two AMQP listeners on port 5672 (plain) and 5671 (SSL/TLS) to be able to run AMQP out of the box. They will also be added as part of the rolling upgrade process as specified on the links below. If you don't need these listeners, you may either delete them *after* the upgrade or use the "NOAMQP" option on the new release *during* the upgrade on the first start of the router start script of the new release, e.g:

        ./smqr1 NOAMQP

or

        ./smqr1_replicated NOAMQP

The option work on HA and non-HA releases but only on the very first start where the config files will be upgraded.