Release 7.5.3

Changes

  • JMS Client: Increase default for swiftmq.pool.session.threads.max and swiftmq.pool.connection.threads.max to 50 to avoid lockups during transparent reconnect.
  • SNMP Management Swiftlet: Upgrade to SNMP4J 1.10.1 and SNMP4J-Agent 1.3.1.

Bugfixes

  • Store Swiftlet: Shrink operation may create inconsistency due to concurrent store read transactions. See below.
  • Store Swiftlet (HA, Replicated File Store, STANDBY): Free page management on STANDBY store may turn into high memory consumption.
  • Scheduler Swiftlet: JMS message ID of messages sent by message jobs are based on System.currentTimeMillis, not unique and thus sometimes removed by duplicate message detection of the receiving client.
  • JMS Client: Transparent reconnect; connection enters infinite reconnect loop if an exception due to invalid SMQP version connection is thrown.
  • JMS Client: Transparent reconnect; connection enters infinite reconnect loop if connecting to an open (e.g. port 80) but invalid port.
  • JMS Client: Transparent reconnect; after reaching max-retries (e.g. router stopped) with multiple concurrent requests waiting, only the first request is released.

Shrink-Bug Note

This bug may occur under high load when a Shrink operation is performed while concurrent read transactions are running on the store. Write transactions were stopped during Shrink but read transactions not. However, they may change the file pointer while pages are written to the store. This may lead to inconsistency.

We highly recommend to disable Shrink jobs until you are able to upgrade to 7.5.3.

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