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
co
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]NmsTemp
Check your producer settings. The producer may override the message
setting. Think of this as a "persistent producer" or "non-persistent
producer". Whatever message is sent via a persistent producer, that message
will be flagged as persistent. I seem to remember coming across this a
while back,
semog wrote:
>
> consumer" situation. If the messages are flagged as non-persistent, then
> everything works fine. We are still working on narrowing down the
> problem.
>
I'm having the same problem as the OP, so we put a workaround in our
production system.
However, I am interested in purs
We have been encountering similar problems, but no definitive reproducible
steps. Our analysis is pointing towards having the persistent flag turned
on for messages. If the messages are flagged as persistent, then we can
encounter non-responsive consumers. Understand that the consumer is not the
