Hey all .. we're getting this message repeatedly in production: "Lock for message c1e4f985949849b6812d55650bdc0def appears to have already expired so we're not dispatching it. Watch out for clock drift between your service bus server and DESKTOP-R6O92KC!"
Obviously we've checked the clocks and there is no drift. We're currently not able to pull any messages off the queue because of this. Anyone else come across this? Cheers.
@drewfreyling you up for a coffee at some point? Would love to chat with you about what you're up to and how we can do this better
3.0 is on Nuget, there's a new sample app on github, have done a bunch of wiki updates with some more to come
.net standard / core support is definitely on the radar, and I've started on a ampq transport
System.IndexOutOfRangeException: Probable I/O race condition detected while copying memory. The I/O package is not thread safe by default. In multithreaded applications, a stream must be accessed in a thread-safe way, such as a thread-safe wrapper returned by TextReader's or TextWriter's Synchronized methods. This also applies to classes like StreamWriter and StreamReader.
at System.Buffer.InternalBlockCopy(Array src, Int32 srcOffsetBytes, Array dst, Int32 dstOffsetBytes, Int32 byteCount)
at System.IO.StreamWriter.Write(Char[] buffer, Int32 index, Int32 count)
at System.IO.TextWriter.SyncTextWriter.Write(Char[] buffer, Int32 index, Int32 count)
at System.Diagnostics.TextWriterTraceListener.WriteLine(String message)
at System.Diagnostics.TraceInternal.WriteLine(String message, String category)
at Nimbus.Configuration.GarbageMan.Add(Object component)
at Nimbus.Infrastructure.NimbusMessagingFactory.CreateTopicSender(String topicPath)
at Nimbus.ConcurrentCollections.ThreadSafeDictionary`2.GetOrAdd(TKey key, Func`2 valueFunc)
at Nimbus.Infrastructure.Events.BusEventSender.<Publish>d__0`1.MoveNext()
that's not one i've seen before
Sorry I meant IInboundInterceptor.OnCommandHandlerError
?
Hi everyone! We are using Nimbus API as Windows Services. I am trying to confirm, do the actual Windows Services need any special permissions to run? Can they just run as Local System? Do we need to create a service account that has local Administrator permissions?
Any info most appreciated :)
We also use Nimbus as Windows Services @RTTrickster. IIRC they can run under any service account, including Local System. The service account does not need local admin permissions but you do need local admin permission for the user that registers the service at installation time.
