Is this for Artemis or for 5.x?
For 5.x, there is no way to do this via STOMP without writing a custom
plugin that will first publish the information as a message so it can be
consumed as well as having your client request the creation of that message
so it can be consumed, and doing that is at le
Thank art.licis
I used mqtt.getOriginalDestination()
--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
On 08/13/2018 07:12 PM, Dan Langford wrote:
some of my users are attempting a pattern to deduplicate messages based on
a time window instead of a fixed amount of space (a duplicate id cache)
so far the concept has been working very well. So they send their AMQP
messages (qpid-jms-client) into a
It is certainly possible to set the JMS client ID via the core JMS client.
Simply invoke javax.jms.Connection.setClientID(String) on the client and
that will be set in the metadata on the corresponding
org.apache.activemq.artemis.core.server.ServerSession on the broker using
the key "jms-client-id"
If someone has unauthorized access to the broker such that they can change
its configuration then he *already* has access to the unencrypted data in
memory and on disk (i.e. in the journal). I see this mainly as a problem
to be solved at one of the many other security layers before the broker is
e
Thank you Tim. Same thing happens when messages are settled as "Modified",
activemq continuously retries the messages without respecting the redelivery
config.
Are there examples or documentation anywhere that detail how to get
redelivery working with python clients ?
--
Sent from: http://acti
Hi,
Thanks for the reply. I still have an issue with threads.
I delete all the related data on disconnect ie., connection,
topics,destination, sessions that are created and then reestablish all of it
in the reconnect function.
I don't see a problem in reconnect, send and receive messages, But its
On 08/14/2018 10:25 AM, areddy wrote:
I'm using qpid proton (python) to connect to activemq and receive messages. I
noticed that, whenever my client "releases" a message, activemq immediately
retries without incrementing the retry count and without respecting the
redelivery policy.
That is doin
I'm using qpid proton (python) to connect to activemq and receive messages. I
noticed that, whenever my client "releases" a message, activemq immediately
retries without incrementing the retry count and without respecting the
redelivery policy.
amq traces
INFO | jvm 1| 2018/08/14 10:14:3
