We need this one badly because it breaks all possibilities for message
expiration on durable topics. I would provide a fix but I am lacking
sufficient understanding of the code flow around cursors and the message
store ;-)
--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f234180
That's great, thank you.
Although we welcome all bug reports, we especially appreciate when the
submitter provides a detailed analysis and/or a test to reproduce the
problem, so thank you for that.
Tim
On Nov 15, 2017 8:54 AM, "tpavelka" wrote:
> Thanks for the confirmation, I have opened
> ht
Thanks for the confirmation, I have opened
https://issues.apache.org/jira/browse/AMQ-6863 and added a Java class that
reproduces the issue.
Tomas
--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
Tomas,
This does appear to be a bug, and I concur with your assessment of how the
null reference is getting passed in. Can you please submit a bug in JIRA?
Thanks,
Tim
On Wed, Nov 1, 2017 at 5:58 AM, tpavelka wrote:
> I am using a file based cursor with durable topic subscriptions because in
>
I am using a file based cursor with durable topic subscriptions because in my
tests the broker would run out of memory when dealing with large numbers of
messages without an active consumer.
I have run into a NullPointerException when the messages meant for the topic
with an active durable subscrip
