at .AbandonMessageAsync(ServiceBusReceivedMessage message, IDictionary`2 propertiesToModify, CancellationToken cancellationToken) at .AbandonMessageAsync(Guid lockToken, IDictionary`2 propertiesToModify, CancellationToken cancellationToken) at .AmqpReceiver.AbandonAsync(Guid lockToken, IDictionary`2 propertiesToModify, CancellationToken cancellationToken) at .RunOperation(Func`4 operation, T1 t1, TransportConnectionScope scope, CancellationToken cancellationToken)
at .RunOperation(Func`4 operation, T1 t1, TransportConnectionScope scope, CancellationToken cancellationToken, Boolean logRetriesAsVerbose) at .AmqpReceiver.DisposeMessageAsync(Guid lockToken, Outcome outcome, TimeSpan timeout) at .AmqpReceiver.ThrowIfSessionLockLost() at .TlsTransport.HandleOperationComplete(IAsyncResult result, Boolean write, Boolean syncComplete) at .WriteAsyncInternal(TIOAdapter writeAdapter, ReadOnlyMemory`1 buffer) at .g_CompleteWriteAsync|177_1(ValueTask writeTask, Byte bufferToReturn) End of stack trace from previous location. at `1.FromAsyncCoreLogic(IAsyncResult iar, Func`2 endFunction, Action`1 endAction, Task`1 promise, Boolean requiresSynchronization) at .TransportStream.EndWrite(IAsyncResult asyncResult) > (10054): An existing connection was forcibly closed by the remote host. > System.IO.IOException: The write operation failed, see inner exception. ErrorCode: ConnectionReset (ServiceCommunicationProblem) > : The write operation failed, see inner exception. The consumer shall not crash, other queued messages shall get consumed. In overall, this looks very similar to the changes in 730d6af, but you also should handle ServiceBusFailureReason.SessionLockLost. Also, the consumer crashes and more messages are consumed until you restart the application. When control goes back to MassTransit/ASB SDK, the 3 log entries as listed below are produced. The consumer receives the message and takes due to a bug a very long time to complete (54 mins). With a queue on Azure Service Bus that has sessions enabled.
calling AbandonMessage() when you have lost the session lock). But I have logs, and far as I can see, the issue is still there on latest master (i.e. I am on 7.3.1, and unfortunately I was not able to create a minimal reproduction snippet. Yes Can you also reproduce the problem with the latest version? In version 7.3.1, the command object looked like this: Maybe its worth mentioning that I have manually simplified my Command json object and changed names on things to be nonsense. I will not paste the whole FutureState json object, but only the Command object within it. I started to suspect something went wrong in the deserialisation of the SomeCommand and started looking into what was stored in the DB. In our case, we store the FutureState in Postgres.
This works well when running unit tests and using the TestHarness. The line: context.GetCommand() generates a System.InvalidOperationException: Operation is not valid due to the current state of the object. In MassTransit v.7.3.1 the initial command (SomeCommand) was fetched without issues and we could read its properties. The issue only appears to us when using Postgres for the state handling. Know that this is not reproducible using the InMemoryTestHarness. WhenAllCompleted(x => x.SetCompletedUsingFactory(context => new SomeCommandCompleted
0 kommentar(er)
