Change Log - Version 1.4.0 - Release Date August 7, 2014
- Improved CPU scalability of the dispatch service, allowing for more destinations and/or more match criteria.
- Usability and validation improvements to the installer.
- Updated RabbitMQ version to 3.3.4.
- Updated Erlang version to 17.1.
- The default configuration of the Endpoint Web Service has changed, to allow better cooperation with other PreEmptive Analytics products installed on the same host. A default install will retain the same `/endpoint` path, so this does not require any changes to upstream applications or Data Hubs.
- In `Dispatch.config`, all destination entries must specify a non-empty `` tag.
- Previously, omitting this tag would behave like ``, which may have led to unintended dispatching.
- The installer will automatically upgrade existing destination entries if `Dispatch.config` is present.
- Non-durable destinations now have the same ‘offline’ behavior as durable destinations.
- No messages are attempted to the non-durable destination while it is offline.
- After the offlineRetry period, all non-durable destinations automatically come back online.
- The following HTTP response codes are now treated as offline responses: 501, 502, 504, 505. In prior releases, these codes were treated as error responses.
- The `Date` HTTP Header will be set if it is not passed by the upstream client, per the HTTP standard. This helps ensure that the Replayer and Workbench provide consistent results from replays.
- Offline responses always cause logging to state that incoming messages will be saved, even when the destination is non-durable (and doesn't ever queue messages).
- Error responses always cause logging to state that the message will be queued, even when this is incorrect:
- When the destination is non-durable (and doesn't ever queue messages).
- When the `errorGiveup` threshold has been reached (and the message is intentionally dropped).