activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Timothy Bish (JIRA)" <>
Subject [jira] [Resolved] (AMQ-4726) Text information of ant producer durable option is not correct
Date Wed, 18 Sep 2013 18:37:56 GMT


Timothy Bish resolved AMQ-4726.

       Resolution: Fixed
    Fix Version/s: 5.9.0

Updated the verbiage to be clear what this options means to producers.  Didn't change the
option name so as not to break current users.  
> Text information of ant producer durable option is not correct
> --------------------------------------------------------------
>                 Key: AMQ-4726
>                 URL:
>             Project: ActiveMQ
>          Issue Type: Bug
>            Reporter: Charles Moulliard
>             Fix For: 5.9.0
> The ant build.xml file of activemq reports that "durable option" will create a durable
> {code}
>      [echo]             ant producer <options> - Creates a producer publishing
a number of messages
>      [echo]
>      [echo]             Producer Options:
>      [echo]                             url - Used to specify acustom URL for the broker,
>      [echo]                                   e.g., tcp://hostname:1234
>      [echo]                           topic - A boolean to determine whether to use topics
>      [echo] 		                        or queues
>      [echo]                         subject - Used to specify a custom destination name,
>      [echo]                                   e.g. MyDestination
>      [echo]                         durable - A boolean to specify that you want to create
>      [echo]                                   a durable topic subscriber?
> {code}
> Obviously, this is a mistake as the "durable" option for the producer allows to change
DeliveryMode of the message ('PERSISTENT' or 'NON-PERSISTENT')
> Maybe, we should use 'persistent' as property name but then the build.xml file and java
class need to be changed

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:

View raw message