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
