1.17.0

As part of this release we had 47 commits which resulted in 10 issues being closed.

Improvements

• #666 ServiceControl Management Utility improve layout for form error and warning messages
• #719 ServiceControl Management Utility MSMQ unsupported features message is badly worded
• #713 Slider for audit and retention period is not precise
• #712 Better error message format
• #678 Add/Edit instance dialog should auto-scroll to the error fields
• #602 Enable to copy ServiceControl's URI in ServiceControl Management Utility

Bugs

• #738 Password validation fails for some Windows 10 users
• #733 Nested path check fails when the directories are siblings with common prefix
• #730 ServiceControl should depend on MSMQ service when the selected transport is MSMQ
• #665 Dropshadow under tooltips in instance action buttons makes the text hard to read

Where to get it

You can download this release from our website

1.16.0

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

Bug

• #723 ServiceControl cannot be used through an ARR reverse proxy in ServicePulse

Where to get it

You can download this release from our website

1.15.0

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

Bug

• #722 Circuit-breaker in EventDispatcher is not being reset

Where to get it

You can download this release from our website

1.14.0

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

Critical Fixes

#717 User's culture is used to serialize objects sent through the REST API

ServiceControl running under non-English culture might return the json data formatted incorrectly. Running with Turkish culture settings as an example, accessing /api/messages REST api, the rendered json will have message_ıd instead of message_id for that property (notice the different i). This is not limited to any given endpoint and is applied through all the property names.

This impacts users of ServicePulse and ServiceInsight

Bug Fixes

• #716 Powershell cmdlet validation of Timespan is broken
• #707 Unable to start Particular.ServiceControl service after upgrading to 1.13.0
• #629 ServiceControl Management and ServiceControl report different license status
• #403 SagaUpdatedMessage handler can cause lots of concurrency exceptions

Where to get it

You can download this release from our website

1.13.0

As part of this release we had 42 commits which resulted in 3 issues being closed.

Improvements

ServiceControl now has a configurable retention period for resolved and archived error messages.
Prior to this improvement the data was never purged from the embedded database which led to some customers experiencing large database growth over time. It is now also possible to "unarchive" messages that have been archived by mistake if this version of ServiceControl is used in conjunction with ServicePulse 1.5

You can learn more about these improvements by reading the issue #694 and also by reviewing the Archived Message Management documentation

Bugs

• #694 Add a retention policy for error messages
• #688 Valid whitespace is not allowed in queue paths

Where to get it

You can download this release from our website

1.12.0

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

Improvements

• #693 Error message forwarding should be a mandatory choice during installation or upgrade

ServiceControl forwards a copy of every error message processed to a secondary error queue designated by the app configuration setting ServiceBus/ErrorLogQueue. If no third party utility is processing messages from the secondary error queue then the forwarding of messages can slowly fill the available storage. A new setting has been introduced to allow this behavior to be turned off. When upgrading to version 1.12 via the ServiceControl Management Utility the upgrade process will prompt to disable this behavior. If an upgrade is being done via the unattended install method or via PowerShell commands then refer to the installation documentation

Bugs

• #704 Update ServiceControl to SQL Server transport v2.2.3 to fix SQL 2008 compatibility
• #699 Endpoint Started message presents date in UTC
• #697 Console log entries which detail log file names are not rendered with date

Where to get it

You can download this release from our website

1.11.1

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

Bugs

• #689 Update ServiceControl to SQL Server transport v2.2.2
  SQL Server transport v2.2.2 has been released to address the issue of delayed endpoint startup caused by a backlog of expired messages at the front of the queue.
  For more information see https://github.com/Particular/NServiceBus.SqlServer/releases/tag/2.2.2.

Should I update?

Only users using Sql Server transport are required to update.

Where to get it

You can download this release from our website

1.11.0

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

Bugs

• #681 Recovery mode of retry batches optimized to not run more then needed.
• #639 Under high load heartbeats can cause concurrency issues.

Improvements

• #680 TimeoutManager does not need to be enabled
  ServiceControl does not use timeouts, having this feature on puts extra load on the RavenDB database.
• #668 Improved debug logging for Production support
  Logging API Calls to Debug log.
  Logging Retry Batch creation events.

Where to get it

You can download this release from our website

1.10.0

As part of this release we had 44 commits which resulted in 6 issues being closed.

Bugs

• #650 Archive All holds RavenDB resources for too long if there are too many failed messages to archive.

Improvements

• #663 Reduce data sent to ServicePulse using EventLog API
  /eventlogitems REST call was unbounded, and ServicePulse really only needs the top 10 documents.

• #655 Add recommended RavenDB settings to app.config on upgrades and installs
  The following settings are automatically added programatically:

  • Raven/Esent/MaxVerPages = 2048
  • gcServer enabled = true

  These can still be overridden via the app.config file:

  <configuration>
    <appSettings>
      <add key="Raven/Esent/MaxVerPages" value="2048" />
    </appSettings>
    <runtime>
      <gcServer enabled="true"/>
    </runtime>
  </configuration>

• #654 Separated RavenDB logging to new log file
  RavenDB logging is now saved independently into ravenlog.<date>.<sequence_number>.txt.
  Logging level is independent of ServiceControl logging.

• #641 Log file should roll over for large log files
  File names are now named logfile.<date>.<sequence_number>.txt.
  Log files are now rotated every 30MB.

• #652 Stop unbounded queries at shutdown
  This makes the shutdown times shorter and responsive.

Where to get it

You can download this release from our website

1.9.0

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

Feature

• #621 Set default logging level to WARN and enable customers to adjust logging level via config

Bugs

• #644 Reclassification of messages can take a long time
• #643 Every error message that is processed results in a INFO log statement
• #634 Configuration error not logged when running as a Windows Service
• #630 NLog configuration is incorrectly configured
• #628 NullReferenceException in LicenseDialog makes it impossible to install license
• #626 Validation of domain service account throws LDAP error for some users
• #624 TTBR is not supported on transactional MSMQ

Where to get it

You can download this release from our website