If you haven't already, I'd turn logging up to DEBUG on both the broker and
your client and see if there is any useful information in either log at the
time that the state changes.
Also, can you characterize in more detail what happens to the consumer
during the test? Presumably it starts in an
The KahaDB index does not drop in size after increasing. It just keeps
track of free pages and will re-use them. So the index tends to grow as
large as it needs and hits a consistent point. A large backlog of messages
will cause the index to increase to track all of the messages. There was at
Good advice.: ) For the future generations, the JIRA ticket is AMQ-6769. Let
us see how far we can get.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/PageFile-is-not-loaded-rebooting-AMQ-every-few-days-tp4727386p4728486.html
Sent from the ActiveMQ - User mailing list
Yes JMX Still shown connection is open. I am not getting any exception for
same. Previously I was receiving exception for same, So that time
connection automatically get reestablished.
Thanks & Regards,
Tejas Ramchandra Sawant
Tata Consultancy Services Ltd.
QBPL, Phase-2, Hinjewadi
Pune,
When your subscriber shows as being offline, does JMX still show that the
connection is open? Or are you indeed closing the connection?
Tim
On Jul 12, 2017 12:39 AM, "tejas13" wrote:
>
> Hi All,
>
> Thank in Advance.
>
> Previously we were using version 5.12.0. That time
Hi All,
Thank in Advance.
Previously we were using version 5.12.0. That time my code was working fine.
Subscriber never get offline automatically.
Recently we upgraded to version 5.14.5 as most stable version and new
features
I found that my Active Durable Subscriber status is changing
Unfortunately, I think the best path forward here is to submit a bug in
JIRA even though the information isn't enough to find a root cause. This
stack trace is new (no search results in Google other than your post), so
it's a new issue, and hopefully the developers will be able to solicit