[ 
https://issues.apache.org/jira/browse/QPID-6759?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14933670#comment-14933670
 ] 

ASF subversion and git services commented on QPID-6759:
-------------------------------------------------------

Commit 1705736 from [~k-wall] in branch 'java/trunk'
[ https://svn.apache.org/r1705736 ]

QPID-6744/QPID-6759: [Java Client/Java Broker] 0-8..0-91 Correct handling of 
queue.delete and exchange.delete.

* Make client's use of the queue.delete nowait flag in line with the 
expectation for a response.
* Correct client's response class expectation when performing an exchange 
delete (previously awaited a ExchangeDeclareOkBody!)
* Make broker send a queue.delete/exchange.delete response only when nowait = 
false
* For backward compatibility, when the peer is identified as an older Qpid 
client, send an queue delete response regardless.  Identification is performed 
by checking the product name and product version, the latter can be overriden, 
which may be useful for private implementations.

> Java client 0-8..0-91 sends exchange.delete but then awaits the wrong 
> response (ExchangeDeclareOk)
> --------------------------------------------------------------------------------------------------
>
>                 Key: QPID-6759
>                 URL: https://issues.apache.org/jira/browse/QPID-6759
>             Project: Qpid
>          Issue Type: Bug
>          Components: Java Client
>    Affects Versions: 0.18, 0.22, 0.32
>            Reporter: Keith Wall
>            Assignee: Keith Wall
>
> The Java Client sends the AMQP exchange.delete but then awaits the wrong a 
> response of the wrong type (ExchangeDeclareOk).  This will always timeout.   
> This defect would affect a user trying to utilise ADDR support with a 
> 0-8..0-91 connection.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to