+972 52-548-6969And now what?
time to read 1 min | 48 words
It looks like the entire MSMQ .NET stack is riddled with threading bugs. At least if you think about using the async methods such as BeginPeek.
Nasty!
Ayende @ Rahien
Ayende @ Rahien
Oren Eini aka Ayende Rahien
CEO of Hibernating Rhinos LTD,
which develops RavenDB,
a NoSQL Open Source Document Database.
FUTURE POSTS
- Integer compression: SIMD bit packing and unusual usages - 3 days from now
- Integer compression: Understanding FastPFor - 4 days from now
- Integer compression: The FastPFor code - 5 days from now
There are posts all the way to Jun 14, 2023
RECENT SERIES
-
Integer compression
(6):
08 Jun 2023 - Using SIMD bit packing in practice -
Talk
(7):
09 Jun 2023 - Scalable Architecture From the Ground Up -
Fight for every byte it takes
(6):
01 May 2023 - Decoding the entries -
Looking into Corax’s posting lists
(3):
17 Apr 2023 - Part III -
Recording
(8):
17 Feb 2023 - RavenDB Usage Patterns
RECENT COMMENTS
-
By peter on Integer compression: Understanding Simd Compression by Lemire
-
By Ryan Heath on Bug chasing, the process is more important than the result
-
By Oren Eini on Bug chasing, the process is more important than the result
-
By Ant on Bug chasing, the process is more important than the result
-
By Ant on Bug chasing, the process is more important than the result
Syndication
| Main feed | |
| Comments feed |
Comments
have you ever thought about joining Microsoft as a tester? :)
@J - haha - second that!
are you using PeekCompleted? i use this pattern for peeks and reads and it may be why i haven't encountered the set of problems you have.
msdn.microsoft.com/.../...queue.peekcompleted.aspx
shawn,
No, I am using the delegate passed to the async method
If you are going to make a statement like this, then shouldn't you at least show the situation under which the error occurred? From what you have shown us, it is hard to ascertain if your claims are indeed true, or you are doing something wrong and just blaming it on the .net MSMQ apis.
Justin,
Null Reference is almost always a bug.
In this case, I am access the AppSpecific property on a message, and it throws this error.
This is caused because of a bug in certain scenarios in which even though the queue is set to accept AppSpecific, it doesn't
An assert failing in production code means that some invariant somewhere is no longer true, and that the author of the code considered such a situation a bug.
Therefore Oren's statement is valid.
@Ayende Thanks for the clarification. I didn't doubt that it was a bug on their part, I just like seeing what caused them so that I know in the future where the dragons may be.
No, that is actually not an assert that is failing.
The assert is in my code.
The problem is that NRE.
choke JMS.... :-P
@Mr Anonymous
Hey no fair - you stole my handle.
Though context is and always would be helpful (or at least more informative ;) ) I'm with Oren on this one. NRE == bug.
You should stop relying in ObjectDisposedException and not touch an object after disposing it. Think of ObjectDisposedException as a debuging aide.
Comment preview