Perhaps the options wireFormat.maxInactivityDuration and wireFormat.maxInactivityDurationInitalDelay might help?
http://activemq.apache.org/configuring-wire-formats.html Thanks, Paul On Wed, Jun 5, 2013 at 3:12 PM, manua <[email protected]> wrote: > HI, > > I am using ActiveMQ 5.8.0 setup on Amazon EC2 Ubuntu instance. The inactive > consumer connected from external networks got disconnected after some time, > but the same consumers when running internally works fine. > > The external consumer works fine until there is flow of requests but if no > requests went through in last 1 hour, they disconnected. My transport > connector seconds are, > > <transportConnector name="stomp" > uri="stomp:// > 0.0.0.0:61612?wireFormat.maxInactivityDuration=0&wireformat.maxFrameSize=1048576000&transport.keepAliveResponseRequired=true > "/> > <transportConnector name="stomp+nio" > uri="stomp+nio:// > 0.0.0.0:61613?wireFormat.maxInactivityDuration=0&wireformat.maxFrameSize=1048576000&transport.keepAliveResponseRequired=true > "/> > > Please let me know if you feel there is something wrong with the settings > or > if we have to enable something else on Amazon ec2 instance. > > Thanks > Manu > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/Amazon-EC2-and-ActiveMQ-Inactive-client-disconnects-tp4667929.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. >
