[jira] [Created] (QPID-4917) [AMQP 1.0] allow for shared topic subscriptions
Gordon Sim created QPID-4917: Summary: [AMQP 1.0] allow for shared topic subscriptions Key: QPID-4917 URL: https://issues.apache.org/jira/browse/QPID-4917 Project: Qpid Issue Type: Bug Components: C++ Broker Affects Versions: 0.22 Reporter: Gordon Sim Assignee: Gordon Sim Fix For: 0.23 One of the things that could be done over 0-10 that is generally useful. -- 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: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (QPID-4918) Python client does not enforce SSL certificate validation even if CAs configured
Ken Giusti created QPID-4918: Summary: Python client does not enforce SSL certificate validation even if CAs configured Key: QPID-4918 URL: https://issues.apache.org/jira/browse/QPID-4918 Project: Qpid Issue Type: Bug Components: Python Client Affects Versions: 0.20 Reporter: Ken Giusti Assignee: Ken Giusti Priority: Blocker Fix For: 0.22 With SSL, the Python client allows the application to specify the trusted CAs that should be used to validate the remote broker's certificate. However, there is a bug in the implementation that does not enforce the validation. This bug allows the SSL connection to be established even if the remote does not provide a valid certificate. This bug is a security risk. The application has configured a CA to use to validate the remote, but that CA is silently ignored and the remote is allowed to connect without validation. To the application, it appears as if the remote certificate has been verified and the remote has been authorized, when in fact that hasn't happened. A CVE has been created for this issue: CVE-2013-1909 -- 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: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (QPID-4918) Python client does not enforce SSL certificate validation even if CAs configured
[ https://issues.apache.org/jira/browse/QPID-4918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ken Giusti resolved QPID-4918. -- Resolution: Fixed The fix has been submitted: http://svn.apache.org/viewvc?view=revision&revision=1460013 The fix include validation of the common name included in the remote's certificate. This is now turned on by default - turning it off opens the possibility for attack via a valid certificate issued to a non-trusted 3rd party. A connection option to disable common name checking has been provided - from the patch: +@type ssl_skip_hostname_check: bool +@param ssl_skip_hostname_check: disable verification of hostname in +certificate. Use with caution - disabling hostname checking leaves you +vulnerable to Man-in-the-Middle attacks. > Python client does not enforce SSL certificate validation even if CAs > configured > > > Key: QPID-4918 > URL: https://issues.apache.org/jira/browse/QPID-4918 > Project: Qpid > Issue Type: Bug > Components: Python Client >Affects Versions: 0.20 >Reporter: Ken Giusti >Assignee: Ken Giusti >Priority: Blocker > Fix For: 0.22 > > > With SSL, the Python client allows the application to specify the trusted CAs > that should be used to validate the remote broker's certificate. > However, there is a bug in the implementation that does not enforce the > validation. This bug allows the SSL connection to be established even if the > remote does not provide a valid certificate. > This bug is a security risk. The application has configured a CA to use to > validate the remote, but that CA is silently ignored and the remote is > allowed to connect without validation. To the application, it appears as if > the remote certificate has been verified and the remote has been authorized, > when in fact that hasn't happened. > A CVE has been created for this issue: CVE-2013-1909 -- 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: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-4357) If an exception is received while the client is blocked on sync, the client should return immediately rather than timing out.
[ https://issues.apache.org/jira/browse/QPID-4357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajith Attapattu updated QPID-4357: --- Fix Version/s: (was: 0.21) Future > If an exception is received while the client is blocked on sync, the client > should return immediately rather than timing out. > - > > Key: QPID-4357 > URL: https://issues.apache.org/jira/browse/QPID-4357 > Project: Qpid > Issue Type: Bug > Components: Java Client >Affects Versions: 0.10, 0.12, 0.14, 0.16, 0.18, 0.20 >Reporter: Rajith Attapattu >Assignee: Rajith Attapattu > Fix For: Future > > > Currently if the client receives an execution-exception while blocked on > sync, it doesn't get notified. Instead the client times out with an exception > as given bellow. > This is less than ideal as it sometimes masks the real error and users need > to go through the logs to figure out what really happens. > This also adds a lot of time to our test suite when errors happen, prolonging > the run time. > org.apache.qpid.AMQException: timed out waiting for sync: complete = 37, > point = 43 [error code 541: internal error] > at > org.apache.qpid.client.AMQSession_0_10.setCurrentException(AMQSession_0_10.java:1074) > at > org.apache.qpid.client.AMQSession_0_10.sync(AMQSession_0_10.java:1051) -- 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: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-4574) [JMS] Deadlock involving _failoverMutex and _messageDeliveryLock
[ https://issues.apache.org/jira/browse/QPID-4574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13681283#comment-13681283 ] Rajith Attapattu commented on QPID-4574: Currently the following solution is being looked at https://reviews.apache.org/r/10738/ > [JMS] Deadlock involving _failoverMutex and _messageDeliveryLock > > > Key: QPID-4574 > URL: https://issues.apache.org/jira/browse/QPID-4574 > Project: Qpid > Issue Type: Bug > Components: Java Client >Affects Versions: 0.14, 0.16, 0.18, 0.20 >Reporter: Rajith Attapattu >Assignee: Rajith Attapattu > Labels: deadlock > Fix For: Future > > Attachments: Test_00782235.java > > > This deadlock can manifest when a you have a producer sending messages inside > an onMessage() call. > This is a common enough pattern, and is used by intermediaries like Message > Bridges, ESB's etc.. > "Dispatcher-0-Conn-1": > at > org.apache.qpid.client.BasicMessageProducer.send(BasicMessageProducer.java:309) > - waiting to lock <0xecfd15a8> (a java.lang.Object) > at Test_00782235$1.onMessage(Test_00782235.java:29) > at > org.apache.qpid.client.BasicMessageConsumer.notifyMessage(BasicMessageConsumer.java:751) > at > org.apache.qpid.client.BasicMessageConsumer_0_10.notifyMessage(BasicMessageConsumer_0_10.java:141) > at > org.apache.qpid.client.BasicMessageConsumer.notifyMessage(BasicMessageConsumer.java:725) > at > org.apache.qpid.client.BasicMessageConsumer_0_10.notifyMessage(BasicMessageConsumer_0_10.java:186) > at > org.apache.qpid.client.BasicMessageConsumer_0_10.notifyMessage(BasicMessageConsumer_0_10.java:54) > at > org.apache.qpid.client.AMQSession$Dispatcher.notifyConsumer(AMQSession.java:3479) > at > org.apache.qpid.client.AMQSession$Dispatcher.dispatchMessage(AMQSession.java:3418) > - locked <0xecfd16c8> (a java.lang.Object) > - locked <0xecfd16d8> (a java.lang.Object) > at > org.apache.qpid.client.AMQSession$Dispatcher.access$1000(AMQSession.java:3205) > at org.apache.qpid.client.AMQSession.dispatch(AMQSession.java:3198) > at > org.apache.qpid.client.message.UnprocessedMessage.dispatch(UnprocessedMessage.java:54) > at > org.apache.qpid.client.AMQSession$Dispatcher.run(AMQSession.java:3341) > at java.lang.Thread.run(Thread.java:679) > "main": > at > org.apache.qpid.client.BasicMessageConsumer.close(BasicMessageConsumer.java:598) > - waiting to lock <0xecfd16c8> (a java.lang.Object) > - locked <0xecfd15a8> (a java.lang.Object) > at > org.apache.qpid.client.BasicMessageConsumer.close(BasicMessageConsumer.java:558) > at Test_00782235.(Test_00782235.java:62) > at Test_00782235.main(Test_00782235.java:12) -- 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: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-4574) [JMS] Deadlock involving _failoverMutex and _messageDeliveryLock
[ https://issues.apache.org/jira/browse/QPID-4574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajith Attapattu updated QPID-4574: --- Fix Version/s: (was: 0.21) Future > [JMS] Deadlock involving _failoverMutex and _messageDeliveryLock > > > Key: QPID-4574 > URL: https://issues.apache.org/jira/browse/QPID-4574 > Project: Qpid > Issue Type: Bug > Components: Java Client >Affects Versions: 0.14, 0.16, 0.18, 0.20 >Reporter: Rajith Attapattu >Assignee: Rajith Attapattu > Labels: deadlock > Fix For: Future > > Attachments: Test_00782235.java > > > This deadlock can manifest when a you have a producer sending messages inside > an onMessage() call. > This is a common enough pattern, and is used by intermediaries like Message > Bridges, ESB's etc.. > "Dispatcher-0-Conn-1": > at > org.apache.qpid.client.BasicMessageProducer.send(BasicMessageProducer.java:309) > - waiting to lock <0xecfd15a8> (a java.lang.Object) > at Test_00782235$1.onMessage(Test_00782235.java:29) > at > org.apache.qpid.client.BasicMessageConsumer.notifyMessage(BasicMessageConsumer.java:751) > at > org.apache.qpid.client.BasicMessageConsumer_0_10.notifyMessage(BasicMessageConsumer_0_10.java:141) > at > org.apache.qpid.client.BasicMessageConsumer.notifyMessage(BasicMessageConsumer.java:725) > at > org.apache.qpid.client.BasicMessageConsumer_0_10.notifyMessage(BasicMessageConsumer_0_10.java:186) > at > org.apache.qpid.client.BasicMessageConsumer_0_10.notifyMessage(BasicMessageConsumer_0_10.java:54) > at > org.apache.qpid.client.AMQSession$Dispatcher.notifyConsumer(AMQSession.java:3479) > at > org.apache.qpid.client.AMQSession$Dispatcher.dispatchMessage(AMQSession.java:3418) > - locked <0xecfd16c8> (a java.lang.Object) > - locked <0xecfd16d8> (a java.lang.Object) > at > org.apache.qpid.client.AMQSession$Dispatcher.access$1000(AMQSession.java:3205) > at org.apache.qpid.client.AMQSession.dispatch(AMQSession.java:3198) > at > org.apache.qpid.client.message.UnprocessedMessage.dispatch(UnprocessedMessage.java:54) > at > org.apache.qpid.client.AMQSession$Dispatcher.run(AMQSession.java:3341) > at java.lang.Thread.run(Thread.java:679) > "main": > at > org.apache.qpid.client.BasicMessageConsumer.close(BasicMessageConsumer.java:598) > - waiting to lock <0xecfd16c8> (a java.lang.Object) > - locked <0xecfd15a8> (a java.lang.Object) > at > org.apache.qpid.client.BasicMessageConsumer.close(BasicMessageConsumer.java:558) > at Test_00782235.(Test_00782235.java:62) > at Test_00782235.main(Test_00782235.java:12) -- 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: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (QPID-4608) JMS client authorization failure throws JMSException instead of JMSSecurityException
[ https://issues.apache.org/jira/browse/QPID-4608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajith Attapattu resolved QPID-4608. Resolution: Fixed The relevant commits are http://svn.apache.org/viewvc?view=revision&revision=r1451047 http://svn.apache.org/viewvc?view=revision&revision=1451362 > JMS client authorization failure throws JMSException instead of > JMSSecurityException > > > Key: QPID-4608 > URL: https://issues.apache.org/jira/browse/QPID-4608 > Project: Qpid > Issue Type: Bug > Components: Java Client >Affects Versions: 0.18, 0.20 >Reporter: Rajith Attapattu >Assignee: Rajith Attapattu >Priority: Minor > Labels: jms, jmsexception > Fix For: 0.21 > > > When ACLs doen't authorize a user to perform an action, Java client raises > JMSException while JMSSecurityException should be raised. > From the java docs for JMSSecurityException, > "This exception must be thrown when a provider rejects a user name/password > submitted by a client. It may also be thrown for any case where a security > restriction prevents a method from completing." -- 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: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (QPID-4496) [Java client] Improve error reporting for invalid addresses
[
https://issues.apache.org/jira/browse/QPID-4496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rajith Attapattu resolved QPID-4496.
Resolution: Fixed
> [Java client] Improve error reporting for invalid addresses
> ---
>
> Key: QPID-4496
> URL: https://issues.apache.org/jira/browse/QPID-4496
> Project: Qpid
> Issue Type: Bug
> Components: Java Client
>Affects Versions: 0.18, 0.20
>Reporter: Rajith Attapattu
>Assignee: Rajith Attapattu
> Labels: addressing, jms
> Fix For: 0.21
>
>
> In the following example, the second address should throw an exception
> notifying that the request type is different from the already present object
> 1. java -cp ${CLASSPATH} org.apache.qpid.example.Spout "ex;{create:sender,
> node: {type:topic,x-declare:{type:topic}}}"
> 2. java -cp ${CLASSPATH} org.apache.qpid.example.Spout "ex;{create:sender,
> node: {type:topic,x-declare:{type:fanout}}}"
> Also we need to provide a clear messages when an assertion is false.
> Ex.
> 1. java -cp ${CLASSPATH} org.apache.qpid.example.Spout "ex;{create:sender,
> node: {type:topic,x-declare:{type:topic}}}"
> 2. java -cp ${CLASSPATH} org.apache.qpid.example.Spout "ex;{assert:sender,
> node: {type:topic,x-declare:{type:fanout}}}"
> All though we currently throw an exception, the message is not very useful.
--
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: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Closed] (QPID-3769) NPE in client AMQDestination.equals()
[ https://issues.apache.org/jira/browse/QPID-3769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajith Attapattu closed QPID-3769. -- Resolution: Fixed Committed to both trunk and 0.22 branch. > NPE in client AMQDestination.equals() > - > > Key: QPID-3769 > URL: https://issues.apache.org/jira/browse/QPID-3769 > Project: Qpid > Issue Type: Bug > Components: Java Client >Affects Versions: 0.12 >Reporter: Jan Bareš >Assignee: Rajith Attapattu > Labels: addressing > Fix For: 0.22 > > > Code of org.apache.qpid.client.AMQDestination.equals(Object) is buggy, it > should test for null on _exchangeClass and _exchangeName before dereferencing > them, lines 522 and 526. -- 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: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (QPID-4540) The subscription queue should only be deleted by the consumer.
[ https://issues.apache.org/jira/browse/QPID-4540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajith Attapattu resolved QPID-4540. Resolution: Fixed A fix was committed at http://svn.apache.org/viewvc?rev=1434492&view=rev > The subscription queue should only be deleted by the consumer. > -- > > Key: QPID-4540 > URL: https://issues.apache.org/jira/browse/QPID-4540 > Project: Qpid > Issue Type: Bug > Components: Java Client >Affects Versions: 0.20 >Reporter: Rajith Attapattu >Assignee: Rajith Attapattu >Priority: Minor > Labels: Addressing > Fix For: 0.21 > > > The removal of subscription queue is handled in the wrong method call and is > causing issues as this method can be called from a producer as well. -- 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: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-4637) 0.22 release tasks
[ https://issues.apache.org/jira/browse/QPID-4637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13681301#comment-13681301 ] ASF subversion and git services commented on QPID-4637: --- Commit 1492230 from [~justi9] [ https://svn.apache.org/r1492230 ] QPID-4637: Tag the 0.22 release > 0.22 release tasks > -- > > Key: QPID-4637 > URL: https://issues.apache.org/jira/browse/QPID-4637 > Project: Qpid > Issue Type: Task > Components: Packaging >Affects Versions: 0.21 >Reporter: Justin Ross >Assignee: Justin Ross > -- 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: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-4637) 0.22 release tasks
[ https://issues.apache.org/jira/browse/QPID-4637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13681317#comment-13681317 ] ASF subversion and git services commented on QPID-4637: --- Commit 1492236 from [~justi9] [ https://svn.apache.org/r1492236 ] QPID-4637: Add 0.22 release notes > 0.22 release tasks > -- > > Key: QPID-4637 > URL: https://issues.apache.org/jira/browse/QPID-4637 > Project: Qpid > Issue Type: Task > Components: Packaging >Affects Versions: 0.21 >Reporter: Justin Ross >Assignee: Justin Ross > -- 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: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (QPID-4497) [Java client] Exclusive property for the subscription queue cannot be overridden using the address string
[
https://issues.apache.org/jira/browse/QPID-4497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rajith Attapattu resolved QPID-4497.
Resolution: Fixed
> [Java client] Exclusive property for the subscription queue cannot be
> overridden using the address string
> -
>
> Key: QPID-4497
> URL: https://issues.apache.org/jira/browse/QPID-4497
> Project: Qpid
> Issue Type: Bug
> Components: Java Client
>Affects Versions: 0.18, 0.20
>Reporter: Rajith Attapattu
>Assignee: Rajith Attapattu
>Priority: Minor
> Labels: addressing
> Fix For: 0.21
>
>
> There have been requests to allow the customization of the subscription
> queue. However there was an issue as the exclusive property wasn't set
> properly due to a bug.
> amq.topic/test; {link: {name:my-queue, durable:true,
> x-declare:{exclusive:false, auto-delete:false}
--
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: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-3966) Add missing license headers to project files
[ https://issues.apache.org/jira/browse/QPID-3966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated QPID-3966: -- Fix Version/s: (was: 0.21) 0.23 > Add missing license headers to project files > > > Key: QPID-3966 > URL: https://issues.apache.org/jira/browse/QPID-3966 > Project: Qpid > Issue Type: Improvement > Components: Packaging >Affects Versions: 0.16 >Reporter: Justin Ross >Assignee: Justin Ross > Fix For: 0.23 > > Attachments: 0.16rc2_rat_output.txt > > > To make it easier to audit the project for license headers, add at least > minimal license headers to many of the project files. See attachment. -- 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: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (QPID-4919) [AMQP 1.0] provide means of configuring subscription queues for 'topics'
Gordon Sim created QPID-4919: Summary: [AMQP 1.0] provide means of configuring subscription queues for 'topics' Key: QPID-4919 URL: https://issues.apache.org/jira/browse/QPID-4919 Project: Qpid Issue Type: Improvement Components: C++ Broker Affects Versions: 0.22 Reporter: Gordon Sim Assignee: Gordon Sim Fix For: 0.23 -- 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: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-4766) [AMQP 1.0] provide a way of specifying an xquery for receivers from an xml exchange
[ https://issues.apache.org/jira/browse/QPID-4766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13681434#comment-13681434 ] ASF subversion and git services commented on QPID-4766: --- Commit 1492310 from [~gsim] [ https://svn.apache.org/r1492310 ] QPID-4766: Added generic filter support to address handling in qpid::messaging. Added support for legacy-headers-binding and newly defined xquery filters. > [AMQP 1.0] provide a way of specifying an xquery for receivers from an xml > exchange > --- > > Key: QPID-4766 > URL: https://issues.apache.org/jira/browse/QPID-4766 > Project: Qpid > Issue Type: Bug > Components: C++ Broker, C++ Client >Affects Versions: 0.22 >Reporter: Gordon Sim >Assignee: Gordon Sim > -- 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: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-4917) [AMQP 1.0] allow for shared topic subscriptions
[ https://issues.apache.org/jira/browse/QPID-4917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13681435#comment-13681435 ] ASF subversion and git services commented on QPID-4917: --- Commit 1492311 from [~gsim] [ https://svn.apache.org/r1492311 ] QPID-4917: allow shared topic subscriptions > [AMQP 1.0] allow for shared topic subscriptions > --- > > Key: QPID-4917 > URL: https://issues.apache.org/jira/browse/QPID-4917 > Project: Qpid > Issue Type: Bug > Components: C++ Broker >Affects Versions: 0.22 >Reporter: Gordon Sim >Assignee: Gordon Sim > Fix For: 0.23 > > > One of the things that could be done over 0-10 that is generally useful. -- 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: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
Review Request: provide means of configuring subscription queues for 'topics' over AMQP 1.0
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/11840/ --- Review request for qpid, Ted Ross and Fraser Adams. Description --- The approach here is to allow a topic node to be defined at the broker level (though only seen by AMQP 1.0 connections) that encompasses a given exchange and queue configuration information to be used with all subscription queues created for outgoing links from that node. You can have different topics mapped (with different names) to the same exchange, allowing different sets of policy to be applied. This addresses bug QPID-4919. https://issues.apache.org/jira/browse/QPID-4919 Diffs - /trunk/qpid/cpp/src/Makefile.am 1492311 /trunk/qpid/cpp/src/amqp.cmake 1492311 /trunk/qpid/cpp/src/qpid/broker/amqp/BrokerContext.h PRE-CREATION /trunk/qpid/cpp/src/qpid/broker/amqp/BrokerContext.cpp PRE-CREATION /trunk/qpid/cpp/src/qpid/broker/amqp/Connection.h 1492311 /trunk/qpid/cpp/src/qpid/broker/amqp/Connection.cpp 1492311 /trunk/qpid/cpp/src/qpid/broker/amqp/Domain.h 1492311 /trunk/qpid/cpp/src/qpid/broker/amqp/Domain.cpp 1492311 /trunk/qpid/cpp/src/qpid/broker/amqp/Interconnect.h 1492311 /trunk/qpid/cpp/src/qpid/broker/amqp/Interconnect.cpp 1492311 /trunk/qpid/cpp/src/qpid/broker/amqp/Interconnects.h 1492311 /trunk/qpid/cpp/src/qpid/broker/amqp/Interconnects.cpp 1492311 /trunk/qpid/cpp/src/qpid/broker/amqp/ProtocolPlugin.cpp 1492311 /trunk/qpid/cpp/src/qpid/broker/amqp/Sasl.h 1492311 /trunk/qpid/cpp/src/qpid/broker/amqp/Sasl.cpp 1492311 /trunk/qpid/cpp/src/qpid/broker/amqp/Session.h 1492311 /trunk/qpid/cpp/src/qpid/broker/amqp/Session.cpp 1492311 /trunk/qpid/cpp/src/qpid/broker/amqp/Topic.h PRE-CREATION /trunk/qpid/cpp/src/qpid/broker/amqp/Topic.cpp PRE-CREATION Diff: https://reviews.apache.org/r/11840/diff/ Testing --- make check passes, basic test of new behaviour works as expected Thanks, Gordon Sim
[jira] [Commented] (QPID-4919) [AMQP 1.0] provide means of configuring subscription queues for 'topics'
[ https://issues.apache.org/jira/browse/QPID-4919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13681453#comment-13681453 ] Gordon Sim commented on QPID-4919: -- A prototype of a suggested approach available for review here: https://reviews.apache.org/r/11840/ > [AMQP 1.0] provide means of configuring subscription queues for 'topics' > > > Key: QPID-4919 > URL: https://issues.apache.org/jira/browse/QPID-4919 > Project: Qpid > Issue Type: Improvement > Components: C++ Broker >Affects Versions: 0.22 >Reporter: Gordon Sim >Assignee: Gordon Sim > Fix For: 0.23 > > -- 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: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (QPID-4917) [AMQP 1.0] allow for shared topic subscriptions
[ https://issues.apache.org/jira/browse/QPID-4917?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gordon Sim resolved QPID-4917. -- Resolution: Fixed > [AMQP 1.0] allow for shared topic subscriptions > --- > > Key: QPID-4917 > URL: https://issues.apache.org/jira/browse/QPID-4917 > Project: Qpid > Issue Type: Bug > Components: C++ Broker >Affects Versions: 0.22 >Reporter: Gordon Sim >Assignee: Gordon Sim > Fix For: 0.23 > > > One of the things that could be done over 0-10 that is generally useful. -- 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: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-4766) [AMQP 1.0] provide a way of specifying an xquery for receivers from an xml exchange
[
https://issues.apache.org/jira/browse/QPID-4766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13681464#comment-13681464
]
Gordon Sim commented on QPID-4766:
--
This can be done by specifying an xquery filter in the address string e.g.
my-xml-exchange; {link:{filter:{value:"declare variable $colour external;
$colour = 'red'",name:x,descriptor:"apache.org:xquery-filter:string"}}}.
Note this can be used to specify any set of filters supported by the broker in
use. The value of the filter opption is a single map or a list of maps, each of
which defines a filter by providing a name, a descriptor (either a numeric code
or a symbolic value) and the value of the filter (e.g. an xquery string as
above or a nested map of headers to match against for a headers binding filter).
> [AMQP 1.0] provide a way of specifying an xquery for receivers from an xml
> exchange
> ---
>
> Key: QPID-4766
> URL: https://issues.apache.org/jira/browse/QPID-4766
> Project: Qpid
> Issue Type: Bug
> Components: C++ Broker, C++ Client
>Affects Versions: 0.22
>Reporter: Gordon Sim
>Assignee: Gordon Sim
>
--
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: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (QPID-4766) [AMQP 1.0] provide a way of specifying an xquery for receivers from an xml exchange
[ https://issues.apache.org/jira/browse/QPID-4766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gordon Sim resolved QPID-4766. -- Resolution: Fixed > [AMQP 1.0] provide a way of specifying an xquery for receivers from an xml > exchange > --- > > Key: QPID-4766 > URL: https://issues.apache.org/jira/browse/QPID-4766 > Project: Qpid > Issue Type: Bug > Components: C++ Broker, C++ Client >Affects Versions: 0.22 >Reporter: Gordon Sim >Assignee: Gordon Sim > -- 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: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-4920) CLONE - Cannot complete the package build on RHEL 5: compilation and install issues
[
https://issues.apache.org/jira/browse/QPID-4920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Darryl L. Pierce updated QPID-4920:
---
Affects Version/s: (was: 0.20)
> CLONE - Cannot complete the package build on RHEL 5: compilation and install
> issues
> ---
>
> Key: QPID-4920
> URL: https://issues.apache.org/jira/browse/QPID-4920
> Project: Qpid
> Issue Type: Bug
> Components: Build Tools
>Reporter: Darryl L. Pierce
>Assignee: Darryl L. Pierce
>
> Use "cmake -DCMAKE_BUILD_TYPE=RelWithDebInfo" or "cmake
> -DCMAKE_BUILD_TYPE=Release", in both cases there are compilation warnings
> treated as errors that stop the build.
> Use "make install" and get this error:
> $ grep cproton.so results_qpid-proton/0.4/2.2.el5/build.log
> Linking C shared module _cproton.so
> /usr/bin/gcc -fPIC -shared -Wl,-soname,_cproton.so -o _cproton.so
> CMakeFiles/_cproton.dir/pythonPYTHON_wrap.c.o ../../libqpid-proton.so.1.0.0
> /usr/lib64/python2.4/config/libpython2.4.a -luuid -lssl -lrt
> Linking C shared module _cproton.so
> /usr/bin/gcc -fPIC -shared -Wl,-soname,_cproton.so -o _cproton.so
> CMakeFiles/_cproton.dir/pythonPYTHON_wrap.c.o ../../libqpid-proton.so.1.0.0
> /usr/lib64/python2.4/config/libpython2.4.a -luuid -lssl -lrt
> -- Installing: %{buildroot}/usr/lib64/python2.4/site-packages/_cproton.so
> + chmod +x '%{buildroot}%{python_sitearch}/_cproton.so'
> chmod: cannot access `%{buildroot}%{python_sitearch}/_cproton.so': No such
> file or directory
> Version-Release number of selected component (if applicable):
> proton-0.4 and trunk
> How reproducible:
> 100%
--
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: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (QPID-4920) CLONE - Cannot complete the package build on RHEL 5: compilation and install issues
Darryl L. Pierce created QPID-4920:
--
Summary: CLONE - Cannot complete the package build on RHEL 5:
compilation and install issues
Key: QPID-4920
URL: https://issues.apache.org/jira/browse/QPID-4920
Project: Qpid
Issue Type: Bug
Components: Build Tools
Affects Versions: 0.20
Reporter: Darryl L. Pierce
Assignee: Darryl L. Pierce
Use "cmake -DCMAKE_BUILD_TYPE=RelWithDebInfo" or "cmake
-DCMAKE_BUILD_TYPE=Release", in both cases there are compilation warnings
treated as errors that stop the build.
Use "make install" and get this error:
$ grep cproton.so results_qpid-proton/0.4/2.2.el5/build.log
Linking C shared module _cproton.so
/usr/bin/gcc -fPIC -shared -Wl,-soname,_cproton.so -o _cproton.so
CMakeFiles/_cproton.dir/pythonPYTHON_wrap.c.o ../../libqpid-proton.so.1.0.0
/usr/lib64/python2.4/config/libpython2.4.a -luuid -lssl -lrt
Linking C shared module _cproton.so
/usr/bin/gcc -fPIC -shared -Wl,-soname,_cproton.so -o _cproton.so
CMakeFiles/_cproton.dir/pythonPYTHON_wrap.c.o ../../libqpid-proton.so.1.0.0
/usr/lib64/python2.4/config/libpython2.4.a -luuid -lssl -lrt
-- Installing: %{buildroot}/usr/lib64/python2.4/site-packages/_cproton.so
+ chmod +x '%{buildroot}%{python_sitearch}/_cproton.so'
chmod: cannot access `%{buildroot}%{python_sitearch}/_cproton.so': No such file
or directory
Version-Release number of selected component (if applicable):
proton-0.4 and trunk
How reproducible:
100%
--
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: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
