Take a look at the TimeStampPlugin which has an option to set a TTL on
messages that arrive without one.
http://activemq.apache.org/timestampplugin.html
On 03/18/2016 12:38 AM, Tim Bain wrote:
Time to live must be set by the producer; I'm not aware of a built-in way
to set it from the broker.
I thought (assumed, I guess) STOMP was just the transfer protocol but that
once the message made it to the broker it would be treated like any other
message. So I had assumed you would set the same headers as for an
OpenWire message, including JMSExpiration. Did I assume wrongly?
On Mar 18, 2016
Thanks i intercepted the message and added an expires header to the STOMP ,
ActiveMQ stomp doesn't support ttl right ?
On Fri, Mar 18, 2016 at 4:38 AM Tim Bain [via ActiveMQ] <
ml-node+s2283324n4709663...@n4.nabble.com> wrote:
> Time to live must be set by the producer; I'm not aware of a built-i
Time to live must be set by the producer; I'm not aware of a built-in way
to set it from the broker. The one thing you might be able to do is use an
embedded Camel route to set that attribute on each message as they are
received by the broker, but I've never tried that so I can't promise it'll
wor
I'd never noticed that option on the plugin; thanks for pointing it out!
On Mar 18, 2016 6:57 AM, "Timothy Bish" wrote:
> Take a look at the TimeStampPlugin which has an option to set a TTL on
> messages that arrive without one.
> http://activemq.apache.org/timestampplugin.html
>
> On 03/18/2016
If i got you correct , some headers on stomp are translated into JMSheaders
, here they are http://activemq.apache.org/stomp.html specifically in
*"Stomp extensions for JMS message semantics"*
BR
Shahbour
On Fri, Mar 18, 2016 at 1:21 PM Tim Bain [via ActiveMQ] <
ml-node+s2283324n4709675...@n4.na
On 03/18/2016 09:41 AM, Tim Bain wrote:
More fundamentally, I'm saying that I have always assumed that when a STOMP
message comes to a broker, it's translated into a JMS message and it stays
in that format until it is delivered to a STOMP consumer. If that's
accurate, it means that all JMS heade
More fundamentally, I'm saying that I have always assumed that when a STOMP
message comes to a broker, it's translated into a JMS message and it stays
in that format until it is delivered to a STOMP consumer. If that's
accurate, it means that all JMS headers are available to be set, and they
will
STOMP Message expiration in action:
https://github.com/apache/activemq/blob/master/activemq-stomp/src/test/java/org/apache/activemq/transport/stomp/StompTest.java#L1810
On 03/18/2016 08:57 AM, shahbour wrote:
If i got you correct , some headers on stomp are translated into JMSheaders
, here the
