Home/ Questions/Q 1095235
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-17T00:05:32+00:00

When we use System.Messaging to send a message remotely, it work correctly i.e. I

  • 0

When we use System.Messaging to send a message remotely, it work correctly i.e. I can see the message on the queue in the remore machine.

However when we attempt to perform the same task i.e. send a message remotely using NServiceBus, the message does not appear in the remote queue, it seems the message disappears

Note, we have the following configuration in the clients app.config file:

<UnicastBusConfig>
 <MessageEndpointMappings>
  <add Messages="CCSMessage.ITaskCompleted, CCSMessage" Endpoint="transactionalQueue@dev014.ccs.local" />
 </MessageEndpointMappings>
</UnicastBusConfig>

We bootstrap the client using the following fluent configuration:

Configure.With()
 .CastleWindsorBuilder(_container)
 .XmlSerializer()
 .MsmqTransport()
  .IsTransactional(true)
  .PurgeOnStartup(false)
 .UnicastBus()
  .ImpersonateSender(false)
 .CreateBus()
 .Start();

Is there anything that we are obviously doing incorrectly?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Given that the client and server are on different machines, you should see the message in the internal outbound queue of the client(if they are on the same machine you will not). The message will be held there until it can be delivered to the server. Make sure the Distributed Transaction Coordinator is running on both machines. Also make sure that the InputQueue in the app.config of the server matches. Also make sure the the server NSB queue is local and transactional.

    • 0