[
https://issues.apache.org/jira/browse/AMQ-4506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dejan Bosanac resolved AMQ-4506.
--------------------------------
Resolution: Not A Problem
I just checked and it seems this is already implemented. There's also a unit
test that covers this use case (sends a message via JMX with ttl and then
browse it in dlq).
https://github.com/apache/activemq/blob/trunk/activemq-unit-tests/src/test/java/org/apache/activemq/security/SecurityJMXTest.java#L73
> sendTextMessage() in JMX should support specifying timeToLive (like Camel /
> Spring-JMS) or JMSExpiration headers
> ----------------------------------------------------------------------------------------------------------------
>
> Key: AMQ-4506
> URL: https://issues.apache.org/jira/browse/AMQ-4506
> Project: ActiveMQ
> Issue Type: Improvement
> Affects Versions: 5.8.0
> Reporter: james strachan
> Assignee: Dejan Bosanac
> Fix For: 5.9.0
>
>
> It would be nice to be able to send a message with a TTL via hawtio
> (http://hawt.io/) or any other JMX tool. Since its not a JMS API we don't
> have to follow the (slightly crap) JMS spec in relation to TTL /
> JMSExpiration so if a timeToLive or JMSExpiration header is specified we
> could actually use it, which would be great.
> Then sending TTL messages would be a nice easy way for folks to get stuff
> onto a DLQ when demoing/testing DLQ tooling in things like hawtio.
> e.g. this JMX Method:
> sendTextMessage(java.util.Map, java.lang.String, java.lang.String,
> java.lang.String)
> it'd be nice to look for timeToLive (say 1000 for 1 second TTL) or
> JMSExpiration (which is a timestamp based thing)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
