Closed PeterKottas closed 7 years ago
As a side note, is raw rabbit thread safe? Cause this method in fact can be called from different threads.
I think I found the problem. It appears I might have been referencing different versions of my DTOs across different services. I am doing some more tests but as long as it goes well, I'll probably close this within next few days.
Hello @PeterKottas - all well 👌 ! Sounds like you might have found the source of the problem. I'll wait to hear back from you before further investigation. Version 1.10.3 has been around for a while, so my gut feeling is that it just might be related to other changes in your application 🙂.
RawRabbit is theadsafe and we're regularly use it for batch work with hundreds concurrent operations.
Have a great evening!
Glad to hear that. Yep it was version missmatch. One of the services connecting to rabbit had old version of binaries. That was it. Deserialization then obviously didn't work. It's quite reassuring to hear that raw rabbit is thread safe, I was almost sure of it but it never hurts to double check :) Carry on with the good work and thanks for the help.
Hi mate, hope you are well. I've been using this lib for a while and only recently have I started seeing these mysterious exceptions. I'll try to provide more info if needed but I was wondering it might ring a bell just seeing this
The code isn't anything special, it looks like this and the exception is thrown and catched here:
Line 52 mentioned in the exception is the one where I call the client. Version of your lib is 1.10.3, the client is a wrapper that basically just call your client directly.
I'll continue looking into it but it might be a banality that can catch other people so I figured it's best to ask the author ;)