Article information
Written by Mikael Henriksson and published on 1 April 2010 at 15:50. This is part five in the Conquering NServiceBus series.
Topic
NServiceBus relies on the Distributed Transactions Coordinator to handle messages from queue arrival through handling completion, including saga storage. The author describes difficulties when storage resides on another server and shares how DTC was made to work over the internet.
Tools and utilities mentioned
- msmqutils folder containing the Runner executable for uninstalling and reinstalling DTC and MSMQ
- DTCPing for tracking down DTC issues
- RunMeFirst.bat
- dcomcnfg for component services configuration
Configuration steps described
The post covers adjusting DTC properties, opening ports, modifying the registry, restarting the computer, configuring the firewall, and verifying DNS resolution with ping. The database server was moved from TCP port 5000 to port 4000 to achieve transactional operation.
Related series posts
- Conquering NServiceBus part 1 – Getting Started
- Conquering NServiceBus part 2 – Initial configuration
- Conquering NServiceBus part 3 – A simple Saga
- Conquering NServiceBus part 4 – Testing
- Conquering NServiceBus part 5 – Troubleshooting DTC
- Conquering NServiceBus part 6 – Upgrading StructureMap