by default the broker retains the sub in memory for an offline durable sub, that can be disabled with keepDurableSubsActive=false broker attribute. That may sort out the behaviour because the sub will be replayed from the store. One other thought, there was an issue with the default advisory consumer on a jms connection (tracking temps) using a sync consumer, so that if it blocked for some reason, that could filter back to the broker. That could impact advisory messages. jms.watchTopicAdvisories=false would avoid that. But as ever, a test case that can reproduce (on trunk) is the best way to find the root cause. good luck.
On 22 January 2015 at 14:41, mclaudio76 <[email protected]> wrote: > It's a standalone broker. Unfortunately, I cannot reproduce the problem in a > test enviroment, mainly because I cannot generate all the traffic the > production broker has to support. Anyway, within the limits of a test > simulation, the presence or not of Advisory topics seemed not to influence > the behaviour of the test broker. > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/Messages-are-kept-in-Pending-queue-for-durable-topic-subscribers-tp4690015p4690273.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com.
