Record retrying before completion of the currently running request

[sunil kumar]

Hi 

Currently we are facing the below issue from nginn

While one of the record is processing the execution before completion of this request nginn is processing the same record again for execution.

Can you please let us know how to handle this scenario. We are facing this issue only some times

[Rafal Gwizdala]

This is not supposed to happen - if you're handling transactions correctly SQL server guarantees the record is locked and nginn can't pick it up again

So i suppose you've got a long transaction and there's a transaction timeout in the middle of processing, 

Can you verify this/provide more info about how long the first record processing takes before the message is picked up again?

R

--
You received this message because you are subscribed to the Google Groups "nginn-messagebus" group.
To unsubscribe from this group and stop receiving emails from it, send an email to nginn-messageb...@googlegroups.com.
To post to this group, send email to nginn-me...@googlegroups.com.
Visit this group at https://groups.google.com/group/nginn-messagebus.

[sunil kumar]

I am getting below error in the sqlserver.

System.Exception: Current transaction has aborted without an exception (probably because inner TransactionScope has aborted)

   at NGinnBPM.MessageBus.Impl.SqlMessageTransport2.ProcessNextMessage(SqlConnection conn)

Can you please help me with this.

[Rafal Gwizdala]

When configuring the message bus, use this method

MessageBusConfigurator.SetReceiveTransactionTimeout(TimeSpan ts)

and specify a timeout long enough to complete the transaction.

But please tell me how long your typical transaction takes? Because if it's in the range of minutes, maybe a better idea would be to split it into two transactions.

R

[Rafal Gwizdala]

btw a default timeout is 1 minute