1.33.0

@particularbot particularbot released this Jan 18, 2017

As part of this release we had 15 commits which resulted in 4 issues being closed.

Bug Fixes

  • 898 - ServiceControl hangs on shutdown
  • 887 - Management utility assumes registry read rights on all services
  • 882 - External Integration Events get stuck until the next one arrives
  • 878 - ServiceControl crashes because of TimeoutException

Where to get it

You can download this release from website.

Downloads

1.32.0

@particularbot particularbot released this Jan 1, 2017 · 15 commits to master since this release

As part of this release we had 3 commits which resulted in 1 issue being closed.

Bug Fixes

  • 883 - Add Instance in Management Utility throws Null Reference Exception if Audit Forwarding is not set

Where to get it

You can download this release from website.

Downloads

1.31.0

@particularbot particularbot released this Dec 19, 2016 · 18 commits to master since this release

As part of this release we had 7 commits which resulted in 4 issues being closed.

Improvements

  • 869 - Warn user that SQL Integrated Security uses Installing Users credentials not ServiceAccount credentials when creating queues

Bug Fixes

  • 875 - Instance list not refreshing when Advanced View is closed
  • 874 - Edit instance does not create required forwarding queue
  • 873 - Update instance port number fails - Queue already used by another instance

Where to get it

You can download this release from website.

Downloads

1.30.0

@particularbot particularbot released this Dec 15, 2016 · 25 commits to master since this release

As part of this release we had 34 commits which resulted in 1 issue being closed.

New Features

  • 862 - Track failure group retry request progress
    Support for tracking progress on retry requests performed on failure groups.

    Retry requests can sometimes take quite a while to finish. ServicePulse now lets users monitor the state and progress of retry request operations from failed message groups. Users can now also monitor retry request operations across different browser sessions.

Other

Our Privacy Policy has been updated to accommodate the reporting of first time installations of Particular products on a machine. No personal data is reported. This reporting only occurs once during initial installation. For more information please read the Evaluation License Agreement and the updated Privacy Policy.

Where to get it

You can download this release from website.

Downloads

1.29.0

@particularbot particularbot released this Dec 7, 2016 · 59 commits to master since this release

As part of this release we had 20 commits which resulted in 2 issues being closed.

Improvements

  • 852 - Only create forwarding queue if option is enabled
  • 867 - Update bundled NServiceBus RabbitMQ Transport to 3.5.1

Where to get it

You can download this release from website.

Downloads

1.28.0

@particularbot particularbot released this Nov 29, 2016 · 79 commits to master since this release

As part of this release we had 16 commits which resulted in 5 issues being closed.

Improvements

  • 788 - Improve the contrast of disabled buttons
  • 726 - Endpoints with no heartbeat plugin should not be automatically added to monitoring groups

Bug Fixes

  • 865 - Migration step of splitting documents can skip documents

Where to get it

You can download this release from website.

Downloads

1.27.0

@particularbot particularbot released this Nov 23, 2016 · 95 commits to master since this release

As part of this release we had 58 commits which resulted in 5 issues being closed.

This release resolves a bug that in certain scenarios caused ServiceControl to hide failed messages from the users and could lead to their deletion after Error Retention Period.

Upgrade Immediately

All users are advised to upgrade to this version of ServiceControl immediately.

Critical Fixes

  • 842 - Event failing on multiple logical subscribers can results in data loss

How to know if you are affected

Anyone using ServiceControl and performing publish-subscribe with multiple logical subscribers running on NServiceBus version 5 and earlier is affected. Users who recently upgraded to V6 from earlier versions should also consider themselves affected.

Symptoms

When event processing fails on multiple logical subscribers, ServiceControl treats them all as a single failing message. All failed messages are presented as a single entry through the ServiceControl API and, as a result, in the ServicePulse UI as well.

During the installation of ServiceControl 1.27.0, all incorrectly merged messages will be split and any problems found will be written to a log file located in the ServiceControl installation path called nsb_log_yyyy-MM-dd_seq.txt.

The log entry has the following structure: Applying migration [Split Failed Message Documents] complete: Found {x} issue(s) in {y} Failed Message document(s). Created {z} new document(s). Deleted {d} old document(s). For any issue found, an original document will be split into multiple documents, each holding a subset of the failed messages. All new documents will have their status set to Unresolved regardless of their current values. This will prevent any potential data loss caused by the Error Retention Process.

If new documents get created, users should expect changes to their current failed messages data, specifically:

  • Some failed message groups may decrease in size - this can happen when some failed messages are moved to different groups
  • Some failed message groups may be gone - this can happen when all failed messages are moved to different groups
  • New failed message groups will be created - newly created messages will be moved from their original groups and assigned to groups prefixed with Issue 842 - {endpoint_name} -.

Retry messages that are in-flight when the upgrade happens are handled gracefully. If the retry fails then the new failure will be matched with the original failed message document and it will be added to a failure group as usual. On the other hand, if the retry succeeds, then the audited success will be matched with the original failed message document and marked as successfully retried.

Should you upgrade immediately

Yes, all affected users should upgrade immediately.

If you are unable to upgrade immediately, we urge you to extend the Error Retention Period to the maximum value of 45 days to delay a potential message loss scenario until the upgrade can be done.

ServiceControl Management Utility - Max Error Retention

After upgrading users should examine all newly created groups prefixed with Issue 842 - and for each decide whether it should be retried or archived.

Improvements

  • 844 - Blank entry in Add Instance dropdown changed to "Please Select ..."
  • 841 - Limit TransportMessage access
  • 840 - I/O improvements for retry pipeline

Where to get it

You can download this release from website.

Downloads

1.26.0

@particularbot particularbot released this Nov 7, 2016 · 153 commits to master since this release

As part of this release we had 4 commits which resulted in 2 issues being closed.

Improvements

  • 833 - Standardize naming of ServiceControl Management Utility across all components

Bug Fixes

  • 837 - Disabling monitoring of endpoints does not persist changes

Where to get it

You can download this release from website.

Downloads

1.25.0

@particularbot particularbot released this Nov 3, 2016 · 157 commits to master since this release

As part of this release we had 28 commits which resulted in 7 issues being closed.

New Features

  • 827 - Expire EventLogItems documents
    We are now purging expired EventLogItems documents from RavenDB.

    By default we purge every 14 days, this default can be changed see documentation.

  • 825 - Added metrics.net
    We have now include the metrics dashboard for diagnostics purpose.
    To access it, navigate to /metrics/, eg http://localhost:33333/metrics/

Improvements

  • 826 - Using changes api in EventDispatcher
  • 824 - Use batch api to create FailedMessageRetry documents
  • 822 - Remove raven unit of work
  • 821 - Cache subscriptions

Where to get it

You can download this release from website.

Downloads

1.24.0

@particularbot particularbot released this Oct 26, 2016 · 185 commits to master since this release

As part of this release we had 63 commits which resulted in 12 issues being closed.

New Features

  • 781 - Added support for MessageType groups for failure messages
    This release adds support for viewing failed messages grouped by Message Type.

    I modified the existing GET/HEAD /recoverability/groups/{classifier?Exception Type and Stack Trace} actions to support a new parameter to set the classifier. The existing Exception Type and Stack Trace is set as the default grouping to maintain compatibility with the current version of ServicePulse. The new classifier is Message Type.

    I have also added GET /recoverability/classifiers to retrieve a list of the currently implemented classifiers to make it easier for ServicePulse to implement this feature.

Improvements

  • 808 - Update ServiceControl to RabbitMq transport v3.5.0
  • 807 - Update ServiceControl to .Net v4.5.2
  • 806 - Update ServiceControl to NServiceBus v5.2.19
  • 783 - Improve license reporting to ServicePulse

Bug Fixes

  • 796 - Setting error retention throws exception
  • 794 - CorrelationId is set to null when missing in failed message
  • 790 - Duplicate messages in error queue import can crash ServiceControl
  • 789 - License reporting in ServiceControl does not refresh
  • 786 - Disabled fields in SCMU instance config should not have underline
  • 782 - Management Utility does not handle upgrade protection correctly.

Where to get it

You can download this release from website.

Downloads