I should be possible as Camel Headers are translated to JMS Headers when
sending to an ActiveMQ queue or topic. This can be tricky though as
sometimes JMS Headers are not set by the client but by the broker (for
example JMSTimestamp), so you can't use all headers.
You can check this page with the
Hello.
In fact I think I'd only need to set one header for expiration time.
Something like that :
${date:now+30m}
But it seems that for overriding the default JMSExpiration another
change must be done on the endpoint (otherwise the JMSExpira
Can you set the parameter globally like this:
ActiveMQComponent activeMQComponent = new ActiveMQComponent();
activeMQComponent.setPreserveMessageQos(true);
context.addComponent("activemq2",activeMQComponent);
On Mon, Apr 3, 2023 at 12:27 PM Ephemeris Lappis
wrote:
> Hello.
>
> In fact I think
The Camel PMC is pleased to announce the release of Apache Camel 3.18.6 (LTS).
Apache Camel is an open source integration framework that empowers you
to quickly and easily integrate various systems consuming or producing
data.
This new patch release contains 26 bug fixes and improvements.
The re
No, I can't : we work on a Red-Hat Fuse cluster, and the brokers and
the related configured components are provided by the cluster (in
groups including Karaf instances), and are shared for all our business
bundles and their queues. We'd want to set time to live (expiration)
only for some queues, no
I think setting "JMSExpiration" from a header isn't supported. Only these
four:
CamelJMSDestinationName (producer)
CamelJmsRequestTimeout (producer)
JMSCorrelationID (producer)
JMSReplyTo (producer)
Don't know why, but other ones have no effect. The component does some
message mapping though
Hello again !
The code I've given before, setting the header "JMSExpiration" with a
computed date ("now+30m", it seems that Camel takes the timestamp's
long value, and not the date string, to set the sent message header)
works if and only if I add "preserveMessageQos=true" to the endpoint's
URI.
T
