Hi Robbie,

Thanks for your response. I raised it as QPID-5342.

Thanks & Regards
Jakub


On Thu, Nov 14, 2013 at 9:44 PM, Robbie Gemmell <[email protected]>wrote:

> Hi Jakub,
>
> That sounds like a bug, please raise a JIRA. From a very quick squint at it
> I would guess it has been that way since 0.20.
>
> Robbie
>
> On 14 November 2013 09:31, Jakub Scholz <[email protected]> wrote:
>
> > In C++ Messaging API, the heartbeat seems to work both ways. If the
> client
> > isn't responding to the heartbeats, it is disconnected by the broker (C++
> > broker). But also in case the client doesn't receive the heartbeat from
> the
> > broker for two intervals, it closes the connection and reports an error.
> >
> > But with the Java JMS API (AMQP 0.10) only the first part seems to be
> true.
> > The broker is still disconnecting the clients. But the Java client it
> self
> > doesn't seem to care whether it received the heartbeat from the broker or
> > not. If I suspend the broker and it stops sending the heartbeat, the
> client
> > never timeouts the connection.
> >
> > Is that intentional behavior or is that a bug?
> >
> > Thanks & Regards
> > Jakub
> >
>

Reply via email to