Skip to content

1.7.0
Compare
Choose a tag to compare
@particularbot particularbot released this 28 Oct 06:52
· 5688 commits to master since this release
1.7.0
40e7e9a

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

New Features

#570 Remove ServiceControl.exe command line options for install/uninstall/confguring service

The new ServiceControl Management utility supercedes command line switches provided by the ServiceControl.exe. So in 1.7 the only command line option that will be retained will be option to run the servicecontrol.exe in maintenance mode. This will also be removed at a later date when the management utility presents this option

#459 Allows to override the default "dbo" schema that is used by the SqlServerTransport when creating the queue tables

NServiceBus.SqlServer recently released a new version that allows to override the default "dbo" schema that is used by the SqlServerTransport when creating the queue tables.

#289 Add multi database support for SqlServerTransport feature

Adding multi-database support to ServiceControl, following the same feature added to the SqlTransport (see http://docs.particular.net/nservicebus/sqlserver/multiple-databases).

#572 Redevelopment of ServiceControl Installation

The ServiceControl Installation has been redeveloped to address many of the the limitations of the old installer. The installation now includes a management application which is launched at installation time and is also available from the Start Menu.

Critical Fixes

#501 Retry batching consumes too many resources and crashes ServiceControl

When retrying a large number of messages, ServiceControl maxes the HDD utilization and then memory until a Raven error occurs. This is caused by an unbounded parallel execution during retry batch creation.
If your system deals with large messages you may also need to also adjust Raven/Esent/MaxVerPages setting to a value higher than 512MB (default). If retrying messages in batches of 1000 and each is 2MB on average then a setting of at least 2048 should be used.

#566 Retries get stuck on a batch when any of the messages fails to be sent

The issue is that if the Send back to endpoint queue fails (it could be because the queue no longer exists because the user has decommission it, or Azure is having a temporary glitch) that causes the batch to never finish and therefore any subsquent batches do not get processed.

How to tell if you are affected?

Read these instructions.

What to do if you are affected

Upgrade ServiceControl to version 1.7.0 or higher.
Download ResetMessageRetry.zip to reset message retries.

Bug Fixes

#527 Allow to override number of maximum concurrent HTTP connections executed under ServiceControl

#568 Corrected sorting of failed messages inside an error group

Where to get it

You can download this release from our website

Assets 4
Loading