First thing would be to test against 5.12.1 On 11/25/2015 10:01 AM, xabhi wrote: > I am using ActiveMQ v5.11.1 > > Below are the STOMP frames sent/received from client/server. > > # Net::STOMP::Client->connect() > # encoded CONNECT frame > # H client-id:test_perl_consumer_huygens01-test_stomp_consumer > # H passcode: > # H host:mqbrokerdev > # H accept-version:1.0,1.1 > # H login: > # sent 141 bytes > # received 135 bytes > # decoding CONNECTED frame > # H server:ActiveMQ/5.11.1 > # H heart-beat:0,0 > # H session:test_perl_consumer_huygens01-test_stomp_consumer > # H version:1.1 > > # Net::STOMP::Client->subscribe() > # encoded SUBSCRIBE frame > # H activemq.prefetchSize:10000 > # H > activemq.subscriptionName:test_perl_consumer_huygens01-test_stomp_consumer > # H ack:client > # H destination:/topic/test > # H callback:CODE(0x33a1188) > # H id:/topic/test-huygens01-15146-stomp_consumer.pl > # sent 254 bytes > Subscribed to /topic/test > > Thanks, > Abhi > > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/Understanding-ActiveMQ-Inactivity-timeout-monitor-in-STOMP-tp4704227p4704280.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. >
-- Tim Bish Sr Software Engineer | RedHat Inc. tim.b...@redhat.com | www.redhat.com twitter: @tabish121 blog: http://timbish.blogspot.com/
