[
https://issues.apache.org/jira/browse/QPID-4312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13570272#comment-13570272
]
Rob Godfrey commented on QPID-4312:
-----------------------------------
Validation checking already occurs when using a QueueSession/QueueSender.
Adding a system property and connection URL option to control checking whether
a Queue address is bound at the point of the message first being sent to a
given destination.
SystemProperty: ClientProperties.VERIFY_QUEUE_ON_SEND =
"qpid.verify_queue_on_send";
Connection URL Option: ConnectionURL.OPTIONS_VERIFY_QUEUE_ON_SEND =
"verifyQueueOnSend";
By default this validation is not enabled (although the validation on
QueueSenders is enabled by default).
> [Java client] [0-8/0-9/0-9-1] add option for performing verification of queue
> existence during creation of a MessageProducer for a Queue destination on a
> generic Session
> -------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: QPID-4312
> URL: https://issues.apache.org/jira/browse/QPID-4312
> Project: Qpid
> Issue Type: Bug
> Components: Java Client
> Reporter: Robbie Gemmell
> Assignee: Rob Godfrey
>
> If a MessageProducer is created against a Queue object on a generic Session
> on an 0-8/0-9/0-9-1 connection using Binding URLs and the queue does not
> actually exist on the broker, the client is not currently able to convey
> this. If however a QueueSender is created on a QueueSession and then used to
> call send() then the existence of the queue on the broker is validated during
> the send method the first time each Queue object is encountered.
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
