Solved implementing a plugin:
@Component
public class DlqBroker extends BrokerFilter {
@Override
public boolean sendToDeadLetterQueue(ConnectionContext context,
MessageReference messageReference,
Subscription subscription, Throwable poisonCause) {
This is piece of my configuration:
There a way to specify my own dead letter strategy?
Rationale behind this request is that my spring listener listen to
Consumer.XXX.VirtualTopic.*.alarms
and this is the queue related to the a virtual topic and the topic is where
mqtt client publishes:
client
I wrote both authentication and authorisation (authorisation base on
client-id and destination name) plugin that loads conf from db (postgresql)
I'm asking my company whether I can release them as open source.
--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
Hello,
I tried and tried and tried and I could not replicate the issues.
I modified and I could not rescue the configuration that exploited the
issue.
So let's say it is not an issue.
I will tell here and save the conf. if I'll get the issue again.
--
Sent from: http://activemq.2283324.n4.nabbl
I did some tests and outcome is that it is neither a matter of point 1) nor
point 2).
The issue arises when listening queue when ends with .>
I changed my topics and queues namespace and now I'm not getting advisory
message anymore.
Moreover I noted that in the activemq webconsole when advisory mes
Hello everyone,
I'm exploring ActiveMQ as mqtt broker.
I need an authorization plugin or map that loads ACL from db (postgresql is
welcome).
Is there is something ready to use?
Please read because I need that:
I need fine grained authorization per iot device (each device must produce
and consume
Hello everyone,
I have a consumer (spring default message listener) of queue mqtt.values.>
ActiveMq version is 5.15.8
Every time the listener starts it receive a message from topic
ActiveMQ.Advisory.MasterBroker
Is that right? Can you help me in order to not receiving such a message.
Meybe it
