Great! Glad I was able to help. I was once mystified by the same thing. I think I made some changes inside NMS to handle this in a more coherent fashion. It didn't make sense that a message flagged as non-persistent was being sent as persistent. Like I said, I would have to go and check the code to remind myself as to how exactly I made the change. It might have been in my own client code in my applications rather than in NMS itself. It's been a while...
Best, Jim On Fri, Jan 30, 2009 at 9:48 AM, mkeenan <kee...@p2sol.com> wrote: > > > > semog wrote: > > > > Check your producer settings. The producer may override the message > > setting. Think of this as a "persistent producer" or "non-persistent > > producer". > > > > Thank you, that was it. > > For anyone using Spring.NET, please note that the [B]Persistent[/B] > property > on the [B]NmsTemplate[/B] class defaults to true and if you set it to false > you [B]MUST[/B] also set [B]ExplicitQosEnabled[/B] to true (default is > False) in order for your persistence setting to be used. Otherwise it will > be ignored. > -- > View this message in context: > http://www.nabble.com/NMS-and-non-responsive-queue-tp21692908p21752228.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. > >
