[ 
https://issues.apache.org/jira/browse/QPID-3422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alex Rudyy updated QPID-3422:
-----------------------------

          Description: 
"ring" and "ring_strict" queue policies are not implemented on a Java Broker.

Test AddressBasedDestinationTest.testBrowseMode fails against java broker 
because it uses a ring queue policy.

  was:
Test AddressBasedDestinationTest.testBrowseMode fails because it is implemented 
for a ring queue which is not implemented by a java broker. 

This issue is raised to track exclude entry in 0.10 profile

    Affects Version/s: 0.12
        Fix Version/s: Future
             Assignee: Alex Rudyy  (was: Robbie Gemmell)
           Issue Type: Task  (was: Bug)
              Summary: Implement ring queue on java broker  (was: Test 
AddressBasedDestinationTest.testBrowseMode fails in 0.10 test profile when run 
against java broker)
    
> Implement ring queue on java broker
> -----------------------------------
>
>                 Key: QPID-3422
>                 URL: https://issues.apache.org/jira/browse/QPID-3422
>             Project: Qpid
>          Issue Type: Task
>          Components: Java Broker, Java Client
>    Affects Versions: 0.10, 0.11, 0.12
>            Reporter: Alex Rudyy
>            Assignee: Alex Rudyy
>            Priority: Minor
>             Fix For: Future
>
>
> "ring" and "ring_strict" queue policies are not implemented on a Java Broker.
> Test AddressBasedDestinationTest.testBrowseMode fails against java broker 
> because it uses a ring queue policy.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project:      http://qpid.apache.org
Use/Interact: mailto:[email protected]

Reply via email to