Thomas Stollenwerk created QPIDJMS-447:
------------------------------------------

             Summary: Make Source.setDurable available 
                 Key: QPIDJMS-447
                 URL: https://issues.apache.org/jira/browse/QPIDJMS-447
             Project: Qpid JMS
          Issue Type: Improvement
          Components: qpid-jms-client
    Affects Versions: 0.40.0, 0.39.0
         Environment: Broker: RabbitMQ 3.7.5 with amqpv1 plugin

Client: QPID-JMS 0.39, 0.40

 
            Reporter: Thomas Stollenwerk


Right now it is not possible to set the "durable" field of an amqp "target" by 
QPID-JMS

[http://docs.oasis-open.org/amqp/core/v1.0/os/amqp-core-messaging-v1.0-os.html#type-terminus-durability]

We are using RabbitMQ 3.7.5 with it's amqp v1.0 plugin. Without this option 
it's not possible to produce messages with to a durable queue using QPID-JMS. 

Attaching to a durable queue results in:

{{{'v1_0.error',\{symbol,<<"amqp:precondition-failed">>},{utf8,<<"PRECONDITION_FAILED
 - inequivalent arg 'durable' for queue 'HOST' in vhost '/': 
{color:#FF0000}received 'false' but current is 'true'{color}">>},undefined}}}

{{Using qpid or amqpnetlite with durable = *TerminusDurability.CONFIGURATION* 
(1) works fine.}}

 

*AmqpProducerBuilder.createEndpoint* should set the *Source.setDurable* option 
like 

*AmqpConsumerBuilder.configureSource* does. Maybe by adding *setDurable* to 

*JmsDestination* passed to *JmsProducerInfo*.

 

Setting it to "false" by default should not break any existing implementations.

 

 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

Reply via email to