[jira] [Created] (QPID-3829) [Java broker] no-local checking for published messages can prevent 0-8/0-9/0-9-1 connections being garbage collected after they are closed

[Java broker] no-local checking for published messages can prevent 0-8/0-9/0-9-1 connections being garbage collected after they are closed --

[jira] [Created] (QPID-3830) remove confusing old client examples

remove confusing old client examples Key: QPID-3830 URL: https://issues.apache.org/jira/browse/QPID-3830 Project: Qpid Issue Type: Improvement Components: Java Client Affects Versions: 0.14

[jira] [Created] (QPID-3831) the 0-10 Java client should use AcquireMode=PRE_ACQUIRED when using selectors on a Queue destination and server-side selectors are in use

the 0-10 Java client should use AcquireMode=PRE_ACQUIRED when using selectors on a Queue destination and server-side selectors are in use -

[jira] [Assigned] (QPID-3829) [Java broker] no-local checking for published messages can prevent 0-8/0-9/0-9-1 connections being garbage collected after they are closed

[ https://issues.apache.org/jira/browse/QPID-3829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell reassigned QPID-3829: Assignee: Keith Wall (was: Robbie Gemmell) [Java broker] no-local checking for

[jira] [Commented] (QPID-3829) [Java broker] no-local checking for published messages can prevent 0-8/0-9/0-9-1 connections being garbage collected after they are closed

[ https://issues.apache.org/jira/browse/QPID-3829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13206587#comment-13206587 ] Robbie Gemmell commented on QPID-3829: -- Hi Keith, could you review these changes

[jira] [Updated] (QPID-3829) [Java broker] no-local checking for published messages can prevent 0-8/0-9/0-9-1 connections being garbage collected after they are closed

[ https://issues.apache.org/jira/browse/QPID-3829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated QPID-3829: - Status: Ready To Review (was: In Progress) [Java broker] no-local checking for published

[jira] [Commented] (QPID-3829) [Java broker] no-local checking for published messages can prevent 0-8/0-9/0-9-1 connections being garbage collected after they are closed

[ https://issues.apache.org/jira/browse/QPID-3829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13206591#comment-13206591 ] Robbie Gemmell commented on QPID-3829: -- Actualy I changed my mind, that test probably

[jira] [Issue Comment Edited] (QPID-3829) [Java broker] no-local checking for published messages can prevent 0-8/0-9/0-9-1 connections being garbage collected after they are closed

[ https://issues.apache.org/jira/browse/QPID-3829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13206591#comment-13206591 ] Robbie Gemmell edited comment on QPID-3829 at 2/13/12 12:43 AM:

[jira] [Updated] (QPID-3440) the Destination cache in AMQMessageDelegate_0_10 does not work

[ https://issues.apache.org/jira/browse/QPID-3440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated QPID-3440: - Attachment: (was: QPID-3440_wip.patch) the Destination cache in AMQMessageDelegate_0_10

[jira] [Commented] (QPID-3440) the Destination cache in AMQMessageDelegate_0_10 does not work

[ https://issues.apache.org/jira/browse/QPID-3440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13206594#comment-13206594 ] Robbie Gemmell commented on QPID-3440: -- Added a test to verify the issue, and its

[jira] [Updated] (QPID-3440) the reply-to Destination cache in AMQMessageDelegate_0_10 does not work

[ https://issues.apache.org/jira/browse/QPID-3440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated QPID-3440: - Summary: the reply-to Destination cache in AMQMessageDelegate_0_10 does not work (was: the

[jira] [Updated] (QPID-3440) the Destination cache in AMQMessageDelegate_0_10 does not work

[ https://issues.apache.org/jira/browse/QPID-3440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated QPID-3440: - Affects Version/s: 0.14 0.13 Fix Version/s: (was: 0.13)

[jira] [Assigned] (QPID-3440) the reply-to Destination cache in AMQMessageDelegate_0_10 does not work

[ https://issues.apache.org/jira/browse/QPID-3440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell reassigned QPID-3440: Assignee: Keith Wall (was: Robbie Gemmell) Keith, could you review these changes please?

[jira] [Updated] (QPID-3440) the reply-to Destination cache in AMQMessageDelegate_0_10 does not work

[ https://issues.apache.org/jira/browse/QPID-3440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated QPID-3440: - Status: Ready To Review (was: In Progress) the reply-to Destination cache in

[jira] [Commented] (QPID-3803) System tests SortedQueueTest#testACK MODESortedQueue fail ocasionally on slow machines

[ https://issues.apache.org/jira/browse/QPID-3803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13206597#comment-13206597 ] Robbie Gemmell commented on QPID-3803: -- This failed yet again on the slow machine in

[jira] [Assigned] (QPID-3831) the 0-10 Java client should use AcquireMode=PRE_ACQUIRED when using selectors on a Queue destination and server-side selectors are in use

[ https://issues.apache.org/jira/browse/QPID-3831?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell reassigned QPID-3831: Assignee: Keith Wall (was: Robbie Gemmell) Keith, could you review this change please?

[jira] [Assigned] (QPID-3830) remove confusing old client examples

[ https://issues.apache.org/jira/browse/QPID-3830?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell reassigned QPID-3830: Assignee: Keith Wall (was: Robbie Gemmell) Keith, could you review these changes please?

[jira] [Updated] (QPID-3830) remove confusing old client examples

[ https://issues.apache.org/jira/browse/QPID-3830?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated QPID-3830: - Status: Ready To Review (was: In Progress) remove confusing old client examples

[jira] [Created] (QPID-3832) Qpid 0.14 broke transport connection setting

Qpid 0.14 broke transport connection setting Key: QPID-3832 URL: https://issues.apache.org/jira/browse/QPID-3832 Project: Qpid Issue Type: Bug Components: C++ Client Affects

[jira] [Commented] (QPID-3817) QueueBrowser does not work with the JNDI destination addressing scheme

[ https://issues.apache.org/jira/browse/QPID-3817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13206610#comment-13206610 ] Robbie Gemmell commented on QPID-3817: -- Hi Praveen, Given how long this bug seems to

[jira] [Resolved] (QPID-3817) QueueBrowser does not work with the JNDI destination addressing scheme

[ https://issues.apache.org/jira/browse/QPID-3817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell resolved QPID-3817. -- Resolution: Fixed Resolving, patch applied. QueueBrowser does not work with

[jira] [Updated] (QPID-3817) QueueBrowser creation does not work with Address syntax via 'destination.' entries in JNDI properties files

[ https://issues.apache.org/jira/browse/QPID-3817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated QPID-3817: - Summary: QueueBrowser creation does not work with Address syntax via 'destination.' entries in