There are a couple of tests in the test suite which use both last-value and
non-destructive queue attributes (e.g. in
org.apache.activemq.artemis.tests.integration.amqp.JMSNonDestructiveTest).
These work without issue. I also took the code you pasted and tried to
reproduce the failure, but everythi
Thank you for the feedback.
I apologize for misreading the documentation. Google doesn't do a great job
of delineating between 5.X and Artemis, and the ActiveMQ homepage says
there's a high-degree of feature parity between the two, so I assumed that
Artemis supported retroactive queues.
I have de
Hello
I am getting an error "AMQ224039: Failed to ack old reference:
java.lang.IllegalStateException: Cannot find add info 5698 on compactor or
current records" after every publish of a message to a Last Value Queue
except the first time.
I am on ActiveMQ Artemis 2.8.1. I know there's a more rece
As was noted in the answers to your StackOverflow question, 5.x does
support retroactive consumption and Artemis does not.
Just to make sure, you would only need a new consumer to have access to the
most recent message, not any before it, right? If you need access to the
full recent history of the
It certainly sounds like OWASP Dependency-Check didn't mark the 2018 CVE as
resolved, which implies that there's a good chance that the same is true
for the 2016 CVE.
For you to be sure of that, I think you'd need to find the JIRA issues
under which we resolved each CVE, look at the code changes t
The answer is pointing me in the direction of durable subscriptions. However,
to my knowledge, durable subscriptions only ensure that topics published
while a subscriber is down are received when it comes back up. Durable
subscriptions don't ensure that a late-joiner receives the latest copy of a
t
Hi Tim,
Thankyou for your reply. So my question here is that will the vulnerability
be shown always in the latest version as well unless we change the
configuration in activemq.xml as you mentioned ?
Also, I am just running a dummy project to scan the vulnerabilities using
owasp dependency-check.
