You are viewing a plain text version of this content. The canonical link for it is here.

Posted to users@activemq.apache.org by um...@comcast.net on 2008/06/06 08:20:13 UTC

AMQ4.1.1: Effect of maxInactivityDuration

Env: Jre 1.6,
        ActiveMQ 4.1.1
        Linux

I have a couple of applications connecting to a single external broker
using TCP transport.

  (app1) <========> External Broker <=========> (app2)


If I have maxInactivityDuration configured to 0 (inactivity monitor disabled), as in

    tcp://<host>:61616?wireFormat.maxInactivityDuration =0

I find that the clients (app1 and app2) stop receiving each other's messages
after idling for a a period of few hours.

If I use default values for maxInactivityDuration as in

   tcp://<host>:61616?trace=true

things work fine. This is counterintuitive to me - why does maxInactivityDuration
break connections after a loing idle period?

Regards

/U