nothing directly maps to JMS objects at the broker side, the addressing
schema is generic to be multi protocol, all of the JMS bits are just a
facade at the client. But in essence a message is sent to an address, if
its anycast it will pick 1 queue and if it is multicast it sends to all the
queues.
The problem got resolved when I set the keepalive=true on the client and
broker.
On Apr 2, 2017 10:26 AM, "Tim Bain" wrote:
> Connection reset errors mean that the far side (i.e. the client in this
> case) closed the connection. So those aren't the root cause of the behavior
> you're seeing.
>
>
Connection reset errors mean that the far side (i.e. the client in this
case) closed the connection. So those aren't the root cause of the behavior
you're seeing.
Is there any chance that a firewall or antivirus program could be
interfering with this traffic? That's the only thing I can think of t
