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

1.8.3

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

Feature

• #616 Remove the 60 day limit on HoursToKeepMessagesBeforeExpiring setting

Bugs

• #614 Validation of Service account fails on non-english versions of Windows
• #612 Messages with TTBR set cannot be forwarded to Audit / Error Log

Where to get it

You can download this release from our website

1.8.2

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

This release patches some issues with the ServiceControl Management utility and Management Powershell module The ServiceControl service is unchanged from 1.8.1. Unless you are experiencing the bugs outlined in this patch there is no need to update at this time

Bugs

• #611 Powershell cmdlet to add ServiceControlInstance is not correctly passing values for forwarding queues
• #610 Cannot re-use queue names for different SC instance with different connection string
• #580 Add instance validation can cause audit forwarding setting to be cleared

Where to get it

You can download this release from our website

1.8.1

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

Bugs

• #606 Handling failures when publishing to external integrations
• #605 SignalR enums payloads are serialized as numbers
• #603 Cancelling configuring an instance in the installer can lead to an empty list of instances being displayed

Where to get it

You can download this release from our website

1.8.0

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

Feature

• #600 External integration dependencies updated

Bug

• #599 Checkboxes do not display correctly in the Management UI over Remote Desktop Connection

Where to get it

You can download this release from our website

1.7.6

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

Bugs

#595 Incorrect serialization of json SignalR stream

An change in ServiceControl 1.7 caused the JSON payload to being serialized using the default SignalR serializer (Pascal case). It should be Camel case.

#593 Management Utility treats Queue Schema parameter in connection string as a validation error

When configuring the SQL transport the connection string is validated as a standard SQL connection string. This means the NSB specific 'Queue Schema' parameter would cause a validation failure

Where to get it

You can download this release from our website

1.7.5

As part of this release we had 2 issues closed.

Bugs Fixed

• #590 SignalR component of ServiceControl not publishing events
• #589 A null reference exception is raised when a retry is issued for a non existing failuremessage id

Where to get it

You can download this release from our website