SC failed to import failed message from Send-Only endpoint

[cedricfronteau]

Service Control (1.0.0) cannot import a failed message issued by a send only endpoint. It seems to be because ReplyToAddress is null.

Exception:
Object reference not set to an instance of an object.
StackTrace:
   at ServiceControl.Contracts.Operations.PhysicalMessage..ctor(TransportMessage message) in c:\BuildAgent\work\b7f882efc2cd360b\src\ServiceControl\Contracts\Operations\PhysicalMessage.cs:line 14
   at ServiceControl.Contracts.Operations.ImportMessage..ctor(TransportMessage message) in c:\BuildAgent\work\b7f882efc2cd360b\src\ServiceControl\Contracts\Operations\ImportMessage.cs:line 15
   at ServiceControl.Contracts.Operations.ImportFailedMessage..ctor(TransportMessage message) in c:\BuildAgent\work\b7f882efc2cd360b\src\ServiceControl\Contracts\Operations\ImportFailedMessage.cs:line 10
   at ServiceControl.Operations.ErrorQueueImport.InnerHandle(TransportMessage message) in c:\BuildAgent\work\b7f882efc2cd360b\src\ServiceControl\Operations\ErrorQueueImport.cs:line 36
   at ServiceControl.Operations.ErrorQueueImport.Handle(TransportMessage message) in c:\BuildAgent\work\b7f882efc2cd360b\src\ServiceControl\Operations\ErrorQueueImport.cs:line 29
   at NServiceBus.Satellites.SatelliteLauncher.HandleMessageReceived(Object sender, TransportMessageReceivedEventArgs e, ISatellite satellite) in c:\BuildAgent\work\31f8c64a6e8a2d7c\src\NServiceBus.Core\Satellites\SatelliteLauncher.cs:line 92
   at NServiceBus.Unicast.Transport.TransportReceiver.OnTransportMessageReceived(TransportMessage msg) in c:\BuildAgent\work\31f8c64a6e8a2d7c\src\NServiceBus.Core\Unicast\Transport\TransportReceiver.cs:line 453   at NServiceBus.Unicast.Transport.TransportReceiver.ProcessMessage(TransportMessage message) in c:\BuildAgent\work\31f8c64a6e8a2d7c\src\NServiceBus.Core\Unicast\Transport\TransportReceiver.cs:line 390
   at NServiceBus.Unicast.Transport.TransportReceiver.TryProcess(TransportMessage message) in c:\BuildAgent\work\31f8c64a6e8a2d7c\src\NServiceBus.Core\Unicast\Transport\TransportReceiver.cs:line 260
   at NServiceBus.Transports.Msmq.MsmqDequeueStrategy.Action() in c:\BuildAgent\work\31f8c64a6e8a2d7c\src\NServiceBus.Core\Transports\Msmq\MsmqDequeueStrategy.cs:line 210
Source:
ServiceControl
TargetSite:
Void .ctor(NServiceBus.TransportMessage)

[johnsimons]

First bug report :)
Can we send @cedricfronteau a tshirt @andreasohlund ?

[johannesg]

I believe I'm affected by the same bug. I send a message from a send only bus, it fails and then the message is lost.

What's particularly nasty is that the message is nowhere to be found. Not in error.log, not in the DB.

I see that there is a queue called "particular.servicecontrol.errors" on my machine. This is also empty.

This is quite alarming to me. Can I trust ServiceControl to not loose any messages?

[andreasohlund]

They are safe, we store them on disk:

C:/windows/system32/config/systemprofile/local/...

Error.log is only for successful messages

Sent from my iPhone

On 17 apr 2014, at 16:10, Johannes Gustafsson notifications@github.com wrote:

I believe I'm affected by the same bug. I send a message from a send only bus, it fails and then the message is lost.

What's particularly nasty is that the message is nowhere to be found. Not in error.log, not in the DB.

I see that there is a queue called "particular.servicecontrol.errors" on my machine. This is also empty.

This is quite alarming to me. Can I trust ServiceControl to not loose any messages?

—
Reply to this email directly or view it on GitHub.

[johnsimons]

We have a fix for SendOnly but we also need to try to reimport these
messages from disk.
I'll write something from cmdline to do that.

On Friday, April 18, 2014, Andreas Öhlund notifications@github.com wrote:

They are safe, we store them on disk:

C:/windows/system32/config/systemprofile/local/...

Error.log is only for successful messages

Sent from my iPhone

On 17 apr 2014, at 16:10, Johannes Gustafsson <notifications@github.comjavascript:_e(%7B%7D,'cvml','notifications@github.com');>
wrote:

I believe I'm affected by the same bug. I send a message from a send
only bus, it fails and then the message is lost.

What's particularly nasty is that the message is nowhere to be found.
Not in error.log, not in the DB.

I see that there is a queue called "particular.servicecontrol.errors" on
my machine. This is also empty.

This is quite alarming to me. Can I trust ServiceControl to not loose
any messages?

Reply to this email directly or view it on GitHub.

Reply to this email directly or view it on GitHubhttps://github.com//issues/313#issuecomment-40723317
.

[johnsimons]

@cedricfronteau @johannesg
What version of NServiceBus are you on?
What transport are you using?

[johnsimons]

They are safe, we store them on disk

No we don't, we store them on the database 😉

[johannesg]

What version of NServiceBus are you on?
What transport are you using?

4.4.2, MSMQ

[johannesg]

Ok, found them under FailedErrorImports.

1. How do I know that there are failed messages in here? Am I supposed to monitor the RavenDB myself?
2. How do I retry these messages?

[johnsimons]

@johannesg see #317

[cedricfronteau]

I'm also on NServiceBus 4.4.2 and MSMQ.

[Grendel]

Hi Guys,

I've hit this also. Is there a fix in the pipeline or should I step away from SendOnly for our Web client?

I'm on 4.6.1 and MSMQ

Thanks

[andreasohlund]

The fix ready for a hotfix

1306f64

Expect a release in the next few days