Release 11.2.0

Enhancements

Bugfixes

  • Management: CLI command tokenizer returned blanks as tokens.
  • Router: ConcurrentSkipListMap replaced because it shows different behavior in Java 8 and 9/10. This bug produces an exception when the Router is started under Java 10.
  • Explorer: Upgraded jide.jar to release 3.7.4 due to Java 9/10 compatibility.

Changes

  • SNMP Swiftlet: Contains only the latest MIBs as all Swiftlets in their latest version are included in the SwiftMQ distribution.

Java 9 and Java 10 Compatibility

A new module system has been introduced in Java 9 that prevents access to modules and will display warnings like this:

      WARNING: An illegal reflective access operation has occurred
      WARNING: Illegal reflective access by xxx (file:yyy) to field zzz
      WARNING: Please consider reporting this to the maintainers of xxx
      WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
      WARNING: All illegal access operations will be denied in a future release

This has been solved in SwiftMQ 11.2.0 by granting access in the scripts

  • explorer, exploreramqp
  • smqr1, smqr2, router
  • smqr1_replicated/jdbc/shared, smqr2_replicated/jdbc/shared

These scripts now have an optional first parameter "java9". If that parameter is given, module access is granted, otherwise not:

      ./smqr1 java9

The only difference in behavior is that the above warning messages are shown if the parameter is not specified.

If you use your own scripts and want to use Java 9/10, please consider to add the parameter too. Just use our scripts as template.

SwiftMQ 11.2.0 requires at least Java 8 and is compliant with Java 9 and Java 10.

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