Thank you, actually we searched but not found any bug fix on inactivity
monitor. there is only one bug which is
https://issues.apache.org/jira/browse/AMQ-6877 on http connector with queue
prefetch 0. this we applied and queue-prefetch is working fine.
can you please help us. because in our case
I can't comment on any plans for addressing the CVE itself within ActiveMQ,
but the CVE appears to apply only when the c3p0 database connection pooling
library is in use in the same JVM as the ActiveMQ code. ActiveMQ doesn't
ship with c3p0, so if I've understood this correctly, you're only at risk
I just realized that the OP seems to have created a new thread about the
same issue at
http://activemq.2283324.n4.nabble.com/Inactivity-Monitor-closing-connection-exactly-at-given-timeout-even-keepalive-true-td4738132.html,
so I'm abandoning this one unless he replies with information that's
The OP sent the following message to me directly late last week, after he
was unable to post it to the mailing list. I think it could be confusing to
anyone following the thread later for me to reply directly to it as the
first time it hits the mailing list, so I'm forwarding it to the list now,
If using HTTP transport then I recall there might have been a bug fixed
for the inactivity and lack of ping commands getting marshaled. That
would probably mean you need to upgrade to a later release though.
Otherwise you'd need to analyze the network traffic and see if a
firewall or
Hello
We have broker -> client environment. we have set 5 minutes as inactivity
monitor timeout. using 5.12.3 version of activemq [ service mix 5.6.0 ]
my question is : we have set connecttimeout to 5 minutes and also keepalive
as true, still always after 5 minutes channel is closed by
