High Quality JMS Messaging.
Release 7.0.0
Enhancements
-
Support of Clustered Queues has been added.
Read more ...
-
SwiftMQ Explorer has been improved and has a new look.
Read more ...
-
XA: SwiftMQ now fully supports XA heuristic recovery.
Read more ...
-
Monitor Swiftlet (HA version): Alert on HA failover added.
Read more ...
Changes
-
JNDI Swiftlet: Lookups are now locally resolved first and, if not found, send to other routers. This enables clients to use a JNDI alias all the time.
-
JNDI Swiftlet: A JNDI alias is now automatically created for all queues, including clustered queues.
Bugfixes
-
Topic Manager Swiftlet: A wrong user name was used if a durable subscriber was created administratively (via SwiftMQ Explorer/CLI) and if authentication was enabled.
-
Network Swiftlet (blocking): Blocking handler didn't terminate when socket.close() was called while it was during processing (= not reading from socket). This caused a connector of a replication channel to stop working after a "missing heartbeat" disconnect.
-
JMS Client: NullPointerException during transparent reconnect while the client was within close of an existing session.
-
JMS Client: Transparent reconnect while session.recover/rollback was pending occasionally did not restart message delivery.
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