Hi,
I have been looking in an application using ActiveMQ and have a situation
where a producer is blocked with this log message due to the temp usage
limit being hit:
[ActiveMQ Transport: tcp:///aaa.bbb.ccc.ddd:65119@64759] 82567721 INFO
org.apache.activemq.broker.region.Queue -
Usage(Main:temp:q
I assume you're asking about ActiveMQ Artemis. If that's the case, it's
worth noting that
org.apache.activemq.artemis.spi.core.protocol.RemotingConnection#getSubject
is only implemented for AMQP connections and it was added when Kerberos
support was implemented. Nothing else in the broker utilizes
Hello,
I am trying to get a java subject (connection.getSubject()) in a remote
interceptor and it is always null. Ultimately, I would like to prevent
messages from being consumed if the subject's associated principals do not
match what is required by the message (as defined in the message).
-
Hello,
I have a configuration with one virtualtopic and three queues.
I send multiples messages on the virtualtopic and they all have a expiration
date.
Sometime, when the queue has no consumer, the expired messages on the queue
are not removed properly and remain on the queue, but this does not
True, we were under the wrong assumption that ActiveMQ in this case meant
Artemis.
Right now we don't have any plans to implement this.
Am Samstag, 20. Oktober 2018, 02:57:32 MESZ hat Justin Bertram
Folgendes geschrieben:
The documentation you referenced [1] is for ActiveMQ 5.x, not Ac