OK, I compiled the following against a recent-ish version of NMS. I haven't
done a more recent compile because as I pointed out in the NMS issue tracker
there was a bug in the use of selectors which I had fixed in my source but
which hadn't been fixed in the SVN Repo (though it might have been ver
Can you post a piece of code like the one in your original post, but
including your cleanup code (I can't see the calls to dispose etc. in the
original post). I will compile it and run it on my set up (4.1.1 + some
fairly recent version of NMS) and see what happens.
Chris
--
View this message
Not really. Actually on looking at it I am closing and disposing of sessions
and consumers, and just disposing of producers and connections so I don't
have your connection.Stop and connection.Close in mine. I would be surprised
if that made a diff though. I had the issue until I added the
connecti
Have you tried explicitly calling connection.Dispose() before exiting your
program? To get round this problem I just called Close() and Dispose() on
every NMS object that exposed either or both those methods and it seemed to
work for me. I suspect that just disposing of the connection may be enoug
I am using message groups with 4.1.1 and NMS. I am finding that
JMSXGroupFirstForConsumer is not being set reliably for the first message
with a given groupId. I cannot as yet see any pattern in the failures. I
have tried just setting the groupId to i.ToString() in a loop for example
and after get
I think the issue with selectors not working is a bug in NMS. I posted a fix
to the Issuer Tracker for NMS a while back, but I'm not sure if anyone has
had a chance to look at it. As far as I can see the selector is being set to
null before being used, so it never works. I just changed my source c
