Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Feb 09 07:31
    hengestone starred NimbusAPI/Nimbus
  • Dec 18 2019 07:48

    uglybugger on netcore-take2

    Rename .nuspec file to match pr… Package projects as part of bui… Remove AssemblyInfo.cs generati… and 8 more (compare)

  • Dec 13 2019 00:42
    DamianMac edited #285
  • Dec 13 2019 00:24
    DamianMac edited #285
  • Dec 12 2019 20:20
    pmcilreavy edited #277
  • Dec 12 2019 20:18
    pmcilreavy edited #280
  • Dec 12 2019 13:33

    DamianMac on add-node-conflict-detection

    (compare)

  • Dec 12 2019 13:33

    DamianMac on amqp-transport

    (compare)

  • Dec 12 2019 13:31
    DamianMac milestoned #284
  • Dec 12 2019 13:31
    DamianMac milestoned #283
  • Dec 12 2019 13:23
    DamianMac opened #285
  • Dec 12 2019 13:22
    DamianMac edited #283
  • Dec 12 2019 13:21
    DamianMac opened #284
  • Dec 12 2019 13:20
    DamianMac opened #283
  • Dec 12 2019 13:17
    DamianMac closed #168
  • Dec 12 2019 13:17
    DamianMac closed #137
  • Dec 12 2019 13:17
    DamianMac closed #127
  • Dec 12 2019 13:17
    DamianMac closed #105
  • Dec 12 2019 13:17
    DamianMac closed #100
  • Dec 12 2019 13:17
    DamianMac closed #99
Kannan
@shreekannan
Hi guys , Im trying to use Nimbs window service bus , just wondering any service bus explorer tools available to view the queue and topic ?
Drew Freyling
@drewfreyling
@shreekannan try
A webui that uses nimbus under the hood
Disclaimer: slightly biased as I'm a dev on it
Kannan
@shreekannan
Thanks @drewfreyling i'll try this
Kannan
@shreekannan
Im using windows service bus 2.1 and try to start the bus service uisng unity IOC Container. Not sure what is missing here. DependencyResolutionException: Failed to construct type
DependencyResolutionException: No registration for type Nimbus.Transports.WindowsServiceBus.Filtering.ISqlFilterExpressionGenerator
Kannan
@shreekannan
Ive fixed the dependency issue
Drew Freyling
@drewfreyling
@ma499 do you think it is worth cherry picking NimbusAPI/Nimbus#270
for v2
given v3 hasn't made its way onto nuget yet and with no .net core support (plus a major lack of v2 updates over the years even though fixes were merged), i'm questioning whether it is worth supporting this project anymore
Ruaan Kruger
@KrugerRuaan_twitter
Hi everyone, is this project still alive and what's cooking with v3 that started radio silence in 2016?
Shingi Mutandwa
@shingi
Anyone know how support for long running handlers is handled in v3?
https://www.uglybugger.org/software/post/support_for_long_running_handlers_in_nimbus
Shingi Mutandwa
@shingi
@uglybugger @DamianMac How is support for long running handlers handled in v3? Planning to upgrade an existing site which is using this feature in v2.
Eddie Stanley
@flakey-bit
On Nimbus 2.0.0.98 in combination with Autofac 3.5.2 - I have an issue where my event is being handled multiple times (event handler is being instantiated multiple times) . I tried changing the event handler from IHandleMulticastEvent to IHandleCompetingEvent however the same problem occurs. Is this a known issue? Any workarounds?
@DamianMac @uglybugger ^^^
Drew Freyling
@drewfreyling
@flakey-bit are you reaching the message lock timeout?
unfortunately the thread still runs while a new message gets popped back on the queue
@KrugerRuaan_twitter see my message from earlier. might be time to fork!
Eddie Stanley
@flakey-bit
@drewfreyling reaching the message lock timeout was indeed the problem.
Drew Freyling
@drewfreyling
@flakey-bit what did you do to get around it?
so lets says you are trying to stitch together some pdfs (think 100s) and this always takes longer than the longest peeklock you can have in WSB (5 mins)
the messages will forever be popped back on the queue....
and if they are large messages and you are storing them on the file system you will run out of disk space :)
this sounds like a hypothetical but i can assure you it is not!
philtts
@philtts

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.

Drew Freyling
@drewfreyling
I've only seen this when your sb nodes have clock drift. Check all the nodes?
Damian Maclennan
@DamianMac
...and I'm alive! been making some changes. Sorry for radio silence, life happens
@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
Drew Freyling
@drewfreyling
@DamianMac definitely.
Drew Freyling
@drewfreyling
well this is interesting
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()
Damian Maclennan
@DamianMac
wow
that's not one i've seen before
binupabraham
@binupabraham
Hi guys.. with ver 2.0.0.98, is there a way to retry sending commands after a delay?
Drew Freyling
@drewfreyling
Yes there is a .SendAfter extension on ibus
binupabraham
@binupabraham
Thanks @drewfreyling . If there is an error in the command handler (ex:smtp exception) and I want to retry the same command after 5 minutes , do I add the .SendAfter logic in the IInboundInterface.OnCommandHandlerError method?
Sorry I meant IInboundInterceptor.OnCommandHandlerError
Drew Freyling
@drewfreyling
Or just try catch and SendAfter in the handler body, up to you
Mustafa Arif
@ma499
Is there a way to set the message label when publishing using Nimbus?
Jason Yannos
@Jyannos_twitter
hey is there a link anywehre to the ECDC berlin videos
?
Joel Dickson
@dicko2
@DamianMac did you get far with netcore take2? i noticed there is issue 275 branch, was that the first attempt?
Tomino
@Tomino2112
Hi guys, we are getting 502s from Nimbus this morning, any known issues ?
Tomino
@Tomino2112
@DamianMac :wave:
Tomino
@Tomino2112
Sorry guys, wrong Nimbus :(
Damian Maclennan
@DamianMac
hehe I did wonder what you meant :)
dighesachin
@dighesachin
Can we integrate it with nodejs?