This content has been marked as final. Show 3 replies
Either it did or it didn't! If it did, it is certainly a bug.
Decide one way or the other and use "READ THIS FIRST" to get some trace
logging and please ALWAYS post the full exception.
I'm using 4.0.0.RC1 and 4.0.1 so they are affected by the bug. I'll wait for release 4.0.2. And by the way, testQueue DID (not just it seems) get the message.