Upgrading from version 6.10 to version 6.11
Consider the following information when upgrading from Diffusion™ version 6.10 to version 6.11.
Upgrading your applications
- Server-side components
-
Recompile all Java™ application components that are deployed to the Diffusion server, such as authorization handlers, against the new version diffusion.jar file. This file is located in the lib directory of your new Diffusion server installation.
Some features that your Java application components might use have been removed or deprecated. Pay attention to new deprecation warnings and compilation failures that occur during recompilation and review the API changes information in the following section to see if these changes affect your applications.
- Clients
-
You can choose not to recompile your client applications and continue to use client libraries from a previous release. If you choose to use client libraries from a previous release, ensure that the libraries are compatible with the new server. For more information, see Interoperability.
You can choose to upgrade your client applications to use the new client libraries. To do this, recompile the client applications against the client libraries located in the clients directory of your new Diffusion server installation and repackage your client application with the new library.
Your client applications may use features that have been removed or deprecated. Review the API changes information in the following section to see if these changes affect your applications.
API changes
Further information about removed or deprecated features is available in the release notes provided online at http://docs.diffusiondata.com/docs/6.11.2/ReleaseNotice.html
API affected | Deprecated feature | Suggested alternative |
---|---|---|
All SDKs | Session Properties Listeners | Session Event Listeners |
JavaScript client | The use of `Buffer` has been deprecated throughout the JavaScript client | Use the browser compatible `Uint8Array` instead |
All SDKs | The ability to specify which topics are replicated in a cluster is deprecated. The default is to replicate all topics. | none |
All SDKs | The fanout feature is deprecated. | Remote Servers and Remote Topic Views |
API affected | Removed feature | Suggested alternative |
---|---|---|
All SDKs | The proceed and open methods on the MissingTopicNotification have been no-ops since 6.6 and were deprecated at that release. They have now been removed. | none |
Java & NET clients | The setSessionPropertiesListener method in the ClientControl feature that did not use CompletableFutures was deprecated in release 6.7 and has been removed in this release as well as the SessionPropertiesListener interface that supported it. | Use the CompletableFuture version, or the new session event listener interface. |
XML Configuration and Server Configuration API Removals
- ThreadPoolConfig.setCoreSize
- ThreadPoolConfig.getCoreSize
- ThreadPoolConfig.setMaximumSize
- ThreadPoolConfig.getMaximumSize
- ThreadPoolConfig.setKeepAlive
- ThreadPoolConfig.getKeepAlive
- ValidationPolicyConfig.isSubscription
- ValidationPolicyConfig.isConnection
- Server.xsd
- thread-pool-definition.core-size
- thread-pool-definition.max-size
- thread-pool-definition.keep-alive
- thread-pool-definition.rejection-handler-class
- security.authorisation-handler-class
- auto-deployment
- Statistics.xsd
- statistics.topic-statistics
- statistics.reporters
- client-statistics.monitor-instances
Upgrading your server installation
- Use the graphical or headless installer to install the new version of
Diffusion
.
For more information, see Installing the Diffusion server.
- Contact DiffusionData for an updated license file.
- You can copy most of your existing configuration files from the etc directory of your previous installation to the etc directory of your new installation.
Behavior changes at the Diffusion server
-
The default maximum message size as configured in Server.xml has been increased from 32KiB to 256KiB.
-
The Diffusion licence no longer supports fanout features. Customers with licences containing these features will need to obtain updated licences.