[jira] [Created] (QPID-3833) Only string values for LVQ key are accepted

2012-02-13 Thread Gordon Sim (Created) (JIRA)
Only string values for LVQ key are accepted --- Key: QPID-3833 URL: https://issues.apache.org/jira/browse/QPID-3833 Project: Qpid Issue Type: Improvement Components: C++ Broker Affects

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

2012-02-13 Thread Gordon Sim (Assigned) (JIRA)
[ https://issues.apache.org/jira/browse/QPID-3832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gordon Sim reassigned QPID-3832: Assignee: Gordon Sim Qpid 0.14 broke transport connection setting

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

2012-02-13 Thread Gordon Sim (Commented) (JIRA)
[ https://issues.apache.org/jira/browse/QPID-3832?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13206884#comment-13206884 ] Gordon Sim commented on QPID-3832: -- Sorry, that was my fault. Great analysis though! I'll

[jira] [Assigned] (QPID-3833) Only string values for LVQ key are accepted

2012-02-13 Thread Gordon Sim (Assigned) (JIRA)
[ https://issues.apache.org/jira/browse/QPID-3833?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gordon Sim reassigned QPID-3833: Assignee: Gordon Sim Only string values for LVQ key are accepted

[jira] [Created] (QPID-3835) [Java broker] DurableSubscriptions without a selector on 0-10 connections will initially be unsubscribed at reconnect following upgrade of a legacy message store

2012-02-13 Thread Robbie Gemmell (Created) (JIRA)
[Java broker] DurableSubscriptions without a selector on 0-10 connections will initially be unsubscribed at reconnect following upgrade of a legacy message store

[jira] [Created] (QPID-3836) no-local does not work for Qpid 0-10 JMS client

2012-02-13 Thread Rajith Attapattu (Created) (JIRA)
no-local does not work for Qpid 0-10 JMS client --- Key: QPID-3836 URL: https://issues.apache.org/jira/browse/QPID-3836 Project: Qpid Issue Type: Bug Components: Java Client Affects

[jira] [Commented] (QPID-3836) no-local does not work for Qpid 0-10 JMS client

2012-02-13 Thread Rajith Attapattu (Commented) (JIRA)
[ https://issues.apache.org/jira/browse/QPID-3836?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13206998#comment-13206998 ] Rajith Attapattu commented on QPID-3836: The fix provided in QPID-3539 only works

handling no-local for existing queues

2012-02-13 Thread Rajith Attapattu
IIRC the no-local argument is passed on during queue-declare. But if you create a subscription with no-local=true on an existing queue how should we handle this situation ? Perhaps there is also a way to pass no-local in the arguments map when creating a subscription ? Regards, Rajith

[jira] [Commented] (QPID-3836) no-local does not work for Qpid 0-10 JMS client

2012-02-13 Thread Robbie Gemmell (Commented) (JIRA)
[ https://issues.apache.org/jira/browse/QPID-3836?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13207008#comment-13207008 ] Robbie Gemmell commented on QPID-3836: -- I think the title is perhaps a little

Re: handling no-local for existing queues

2012-02-13 Thread Robbie Gemmell
I cross-posted this on the JIRA so I'll report it here incase anyone wants a discussion :) I think the JIRA title is perhaps a little misleading, given the number of tests running that show it does work to an extent. Perhaps 'doesn't work when used on queues not originally declared no-local'

[jira] [Updated] (QPID-3835) [Java broker] DurableSubscriptions without a selector on 0-10 connections will initially be unsubscribed at reconnect following upgrade of a legacy message store

2012-02-13 Thread Robbie Gemmell (Updated) (JIRA)
[ https://issues.apache.org/jira/browse/QPID-3835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated QPID-3835: - Status: Ready To Review (was: In Progress) [Java broker] DurableSubscriptions without a

[jira] [Updated] (QPID-3836) no-local does not work for Qpid 0-10 JMS client when using address strings

2012-02-13 Thread Rajith Attapattu (Updated) (JIRA)
[ https://issues.apache.org/jira/browse/QPID-3836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajith Attapattu updated QPID-3836: --- Summary: no-local does not work for Qpid 0-10 JMS client when using address strings (was:

[jira] [Commented] (QPID-3547) qpid-config currently doesn't display useful information about headers exchange bindings

2012-02-13 Thread jirapos...@reviews.apache.org (Commented) (JIRA)
[ https://issues.apache.org/jira/browse/QPID-3547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13207103#comment-13207103 ] jirapos...@reviews.apache.org commented on QPID-3547: -

Re: handling no-local for existing queues

2012-02-13 Thread Rajith Attapattu
On Mon, Feb 13, 2012 at 12:53 PM, Robbie Gemmell robbie.gemm...@gmail.com wrote: I cross-posted this on the JIRA so I'll report it here incase anyone wants a discussion :) I think the JIRA title is perhaps a little misleading, given the number of tests running that show it does work to an

[jira] [Assigned] (QPID-3638) incompatibility with new boost version 1.48

2012-02-13 Thread Ted Ross (Assigned) (JIRA)
[ https://issues.apache.org/jira/browse/QPID-3638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross reassigned QPID-3638: -- Assignee: Ted Ross incompatibility with new boost version 1.48

[jira] [Resolved] (QPID-3638) incompatibility with new boost version 1.48

2012-02-13 Thread Ted Ross (Resolved) (JIRA)
[ https://issues.apache.org/jira/browse/QPID-3638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross resolved QPID-3638. Resolution: Fixed Fix Version/s: 0.15 incompatibility with new boost version 1.48

Re: handling no-local for existing queues

2012-02-13 Thread Robbie Gemmell
On 13 February 2012 19:42, Rajith Attapattu rajit...@gmail.com wrote: On Mon, Feb 13, 2012 at 12:53 PM, Robbie Gemmell robbie.gemm...@gmail.com wrote: I cross-posted this on the JIRA so I'll report it here incase anyone wants a discussion :) I think the JIRA title is perhaps a little

Re: handling no-local for existing queues

2012-02-13 Thread Rob Godfrey
*snip* The client currently only sends the no-local argument during queue creation as you mentioned, but there is support in the protocol for adding arguments to subscriptions so it could potentially be added there too (The protocol actually has a no-local field on the file and stream

Re: handling no-local for existing queues

2012-02-13 Thread Robbie Gemmell
On 13 February 2012 21:59, Rob Godfrey rob.j.godf...@gmail.com wrote: *snip* The client currently only sends the no-local argument during queue creation as you mentioned, but there is support in the protocol for adding arguments to subscriptions so it could potentially be added there too

Re: handling no-local for existing queues

2012-02-13 Thread Rob Godfrey
One could argue that the no-local should be treated the same way as selectors on a durable subscription - that is that the no-localness is somehow encoded into the binding (if queue has exclusive consumer and consumer connection == producer consumer then don't enqueue) Certainly seems wrong to be

[jira] [Updated] (QPID-3466) The toString() method for JMSDestination and JMSReplyTo is not formatted properly according to the destination syntax.

2012-02-13 Thread Rajith Attapattu (Updated) (JIRA)
[ https://issues.apache.org/jira/browse/QPID-3466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajith Attapattu updated QPID-3466: --- Fix Version/s: (was: 0.14) 0.15 The toString() method for

[jira] [Updated] (QPID-3583) 0.14 release tasks

2012-02-13 Thread Rajith Attapattu (Updated) (JIRA)
[ https://issues.apache.org/jira/browse/QPID-3583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajith Attapattu updated QPID-3583: --- Fix Version/s: (was: 0.14) 0.15 0.14 release tasks

[jira] [Updated] (QPID-3462) Failover is not transparent when using CLIENT_ACK mode

2012-02-13 Thread Rajith Attapattu (Updated) (JIRA)
[ https://issues.apache.org/jira/browse/QPID-3462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajith Attapattu updated QPID-3462: --- Fix Version/s: (was: 0.14) 0.15 Failover is not transparent when

[jira] [Updated] (QPID-3461) A SessionException is thrown (instead of a JMSException) when an error occurs during a commit.

2012-02-13 Thread Rajith Attapattu (Updated) (JIRA)
[ https://issues.apache.org/jira/browse/QPID-3461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajith Attapattu updated QPID-3461: --- Fix Version/s: (was: 0.14) 0.15 A SessionException is thrown

[jira] [Updated] (QPID-3401) Refactor address resolution code

2012-02-13 Thread Rajith Attapattu (Updated) (JIRA)
[ https://issues.apache.org/jira/browse/QPID-3401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajith Attapattu updated QPID-3401: --- Fix Version/s: (was: 0.14) 0.15 Refactor address resolution code

[jira] [Updated] (QPID-3388) Implement producer capacity to leverage producer flow control implemented by the C++ broker

2012-02-13 Thread Rajith Attapattu (Updated) (JIRA)
[ https://issues.apache.org/jira/browse/QPID-3388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajith Attapattu updated QPID-3388: --- Fix Version/s: (was: 0.14) 0.15 Implement producer capacity to

[jira] [Updated] (QPID-3350) Python federation tests (federation.FederationTests.*) leak connections

2012-02-13 Thread Rajith Attapattu (Updated) (JIRA)
[ https://issues.apache.org/jira/browse/QPID-3350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajith Attapattu updated QPID-3350: --- Fix Version/s: (was: 0.14) 0.15 Python federation tests

[jira] [Updated] (QPID-3398) LegacyLVQ should not impose extra semantics on remove function

2012-02-13 Thread Rajith Attapattu (Updated) (JIRA)
[ https://issues.apache.org/jira/browse/QPID-3398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajith Attapattu updated QPID-3398: --- Fix Version/s: (was: 0.14) 0.15 LegacyLVQ should not impose extra

[jira] [Updated] (QPID-3380) Allow to get/set encoding type for JMS messages

2012-02-13 Thread Rajith Attapattu (Updated) (JIRA)
[ https://issues.apache.org/jira/browse/QPID-3380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajith Attapattu updated QPID-3380: --- Fix Version/s: (was: 0.14) 0.15 Allow to get/set encoding type

[jira] [Updated] (QPID-2643) Support Visual Studio 2010

2012-02-13 Thread Rajith Attapattu (Updated) (JIRA)
[ https://issues.apache.org/jira/browse/QPID-2643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajith Attapattu updated QPID-2643: --- Fix Version/s: (was: 0.14) 0.15 Support Visual Studio 2010

[jira] [Commented] (QPID-3838) [JMS] Vendor specific properties should be prefixed with JMS_

2012-02-13 Thread Rajith Attapattu (Commented) (JIRA)
[ https://issues.apache.org/jira/browse/QPID-3838?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13207335#comment-13207335 ] Rajith Attapattu commented on QPID-3838: Simply changing the existing behaviour can