[jira] [Commented] (ARTEMIS-853) Support for exclusive consumers
[ https://issues.apache.org/jira/browse/ARTEMIS-853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16343639#comment-16343639 ] Gary Tully commented on ARTEMIS-853: 5.x has: allConsumersExclusiveByDefault destination policy[1]; if we implement that on a queue, then we cover 90% of the use cases. It does not need to be dynamic, ie: initiated by the first exclusive consumer... mixing exclusive and not exclusive is not the norm. [1] http://activemq.apache.org/per-destination-policies.html > Support for exclusive consumers > --- > > Key: ARTEMIS-853 > URL: https://issues.apache.org/jira/browse/ARTEMIS-853 > Project: ActiveMQ Artemis > Issue Type: New Feature > Components: Broker >Reporter: Matt Pavlovich >Priority: Major > > Artemis should support a consumer feature where a single consumer receives > all messages, even when multiple consumers are present. This capability > maintains message ordering while allowing a HA consumer. > ActiveMQ 5.x supports this, as does IBM MQ, Tibco EMS, etc. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (ARTEMIS-550) Add support for virtual topic consumers
[ https://issues.apache.org/jira/browse/ARTEMIS-550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16343491#comment-16343491 ] ASF GitHub Bot commented on ARTEMIS-550: Github user michaelandrepearce commented on the issue: https://github.com/apache/activemq-artemis/pull/1820 @gtully agreed. I think it be great if @mattrpav for the use cases we think we can't cover today, theyre detailed each in a JIRA, this way we can tackle one by one, or if they are possible today, then we can create Documents in how. > Add support for virtual topic consumers > --- > > Key: ARTEMIS-550 > URL: https://issues.apache.org/jira/browse/ARTEMIS-550 > Project: ActiveMQ Artemis > Issue Type: Improvement > Components: Broker >Affects Versions: 1.3.0 >Reporter: Benjamin Graf >Assignee: Martyn Taylor >Priority: Major > Attachments: image-2018-01-26-09-02-08-192.png > > > Artemis should support virtual topic consumers as alternative to topic > subscriptions as ActiveMQ itself does. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMQ-5669) Update Karaf feature files to add required namespace
[
https://issues.apache.org/jira/browse/AMQ-5669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16343443#comment-16343443
]
Martin Lichtin commented on AMQ-5669:
-
It's likely just the "name" attribute missing on these feature files. Should be
trivial to add.
> Update Karaf feature files to add required namespace
>
>
> Key: AMQ-5669
> URL: https://issues.apache.org/jira/browse/AMQ-5669
> Project: ActiveMQ
> Issue Type: Improvement
>Affects Versions: 5.11.1
>Reporter: Martin Lichtin
>Assignee: Hadrian Zbarcea
>Priority: Major
>
> Getting a warning from Karaf:
> FeatureValidationUtil| 20 - org.apache.karaf.features.core -
> 3.0.3 | Old style feature file without namespace found (URI:
> mvn:org.apache.activemq/activemq-karaf/5.11.1/xml/features-core). This format
> is deprecated and support for it will soon be removed
> The feature files should be changed from, e.g.:
> {noformat}{noformat}
> to
> {noformat} xmlns="http://karaf.apache.org/xmlns/features/v1.2.1;>{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (ARTEMIS-550) Add support for virtual topic consumers
[ https://issues.apache.org/jira/browse/ARTEMIS-550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16343413#comment-16343413 ] ASF GitHub Bot commented on ARTEMIS-550: Github user gtully commented on the issue: https://github.com/apache/activemq-artemis/pull/1820 Hope we don't lose the pictures, but this PR as it stands is too simplistic and the use case is already covered by a shared durable sub. the prefixed fqqn will be the way to go if we need to improve in this area. https://activemq.apache.org/artemis/docs/2.3.0/address-model.html#configuring-a-prefix-to-connect-to-a-specific-routing-type thanks for the feedback :-) > Add support for virtual topic consumers > --- > > Key: ARTEMIS-550 > URL: https://issues.apache.org/jira/browse/ARTEMIS-550 > Project: ActiveMQ Artemis > Issue Type: Improvement > Components: Broker >Affects Versions: 1.3.0 >Reporter: Benjamin Graf >Assignee: Martyn Taylor >Priority: Major > Attachments: image-2018-01-26-09-02-08-192.png > > > Artemis should support virtual topic consumers as alternative to topic > subscriptions as ActiveMQ itself does. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (ARTEMIS-550) Add support for virtual topic consumers
[ https://issues.apache.org/jira/browse/ARTEMIS-550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16343414#comment-16343414 ] ASF GitHub Bot commented on ARTEMIS-550: Github user gtully closed the pull request at: https://github.com/apache/activemq-artemis/pull/1820 > Add support for virtual topic consumers > --- > > Key: ARTEMIS-550 > URL: https://issues.apache.org/jira/browse/ARTEMIS-550 > Project: ActiveMQ Artemis > Issue Type: Improvement > Components: Broker >Affects Versions: 1.3.0 >Reporter: Benjamin Graf >Assignee: Martyn Taylor >Priority: Major > Attachments: image-2018-01-26-09-02-08-192.png > > > Artemis should support virtual topic consumers as alternative to topic > subscriptions as ActiveMQ itself does. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (ARTEMIS-550) Add support for virtual topic consumers
[
https://issues.apache.org/jira/browse/ARTEMIS-550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16343407#comment-16343407
]
ASF GitHub Bot commented on ARTEMIS-550:
Github user gtully commented on a diff in the pull request:
https://github.com/apache/activemq-artemis/pull/1820#discussion_r164445884
--- Diff:
artemis-jms-client/src/main/java/org/apache/activemq/artemis/jms/client/ActiveMQSession.java
---
@@ -698,8 +699,17 @@ private ActiveMQMessageConsumer createConsumer(final
ActiveMQDestination dest,
*/
if (!response.isExists() ||
!response.getQueueNames().contains(dest.getSimpleAddress())) {
if (response.isAutoCreateQueues()) {
+ SimpleString queueNameToUse = dest.getSimpleAddress();
+ SimpleString addressToUse = queueNameToUse;
+ RoutingType routingTypeToUse = RoutingType.ANYCAST;
+ if
(CompositeAddress.isFullyQualified(queueNameToUse.toString())) {
+ CompositeAddress compositeAddress =
CompositeAddress.getQueueName(queueNameToUse.toString());
+ addressToUse = new
SimpleString(compositeAddress.getAddress());
+ queueNameToUse = new
SimpleString(compositeAddress.getQueueName());
+ routingTypeToUse = RoutingType.MULTICAST;
--- End diff --
@michaelandrepearce I agree with you, I will close out this PR.
The discussion is the valuable bit.
For this use case, SDS is the answer.
For the more general CORE FQQN scenario, using a prefix with a FQQN would
be the other approach. It probably should support the prefix notation via the
acceptor.
```multicast://VirtualTopic.Orders::Consumer.A```
This says, create me a sub queue called ```Consumer.A`` that is bound using
```multicast``` routing to address ```VirtualTopic.Orders```.
> Add support for virtual topic consumers
> ---
>
> Key: ARTEMIS-550
> URL: https://issues.apache.org/jira/browse/ARTEMIS-550
> Project: ActiveMQ Artemis
> Issue Type: Improvement
> Components: Broker
>Affects Versions: 1.3.0
>Reporter: Benjamin Graf
>Assignee: Martyn Taylor
>Priority: Major
> Attachments: image-2018-01-26-09-02-08-192.png
>
>
> Artemis should support virtual topic consumers as alternative to topic
> subscriptions as ActiveMQ itself does.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMQ-5669) Update Karaf feature files to add required namespace
[
https://issues.apache.org/jira/browse/AMQ-5669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16343350#comment-16343350
]
Christopher L. Shannon commented on AMQ-5669:
-
Reverted these commits as they break all of the Karak integration tests. More
work needs to be done to make sure the tests pass.
> Update Karaf feature files to add required namespace
>
>
> Key: AMQ-5669
> URL: https://issues.apache.org/jira/browse/AMQ-5669
> Project: ActiveMQ
> Issue Type: Improvement
>Affects Versions: 5.11.1
>Reporter: Martin Lichtin
>Assignee: Hadrian Zbarcea
>Priority: Major
>
> Getting a warning from Karaf:
> FeatureValidationUtil| 20 - org.apache.karaf.features.core -
> 3.0.3 | Old style feature file without namespace found (URI:
> mvn:org.apache.activemq/activemq-karaf/5.11.1/xml/features-core). This format
> is deprecated and support for it will soon be removed
> The feature files should be changed from, e.g.:
> {noformat}{noformat}
> to
> {noformat} xmlns="http://karaf.apache.org/xmlns/features/v1.2.1;>{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMQ-6873) Update dependencies
[ https://issues.apache.org/jira/browse/AMQ-6873?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christopher L. Shannon updated AMQ-6873: Fix Version/s: (was: 5.15.3) > Update dependencies > --- > > Key: AMQ-6873 > URL: https://issues.apache.org/jira/browse/AMQ-6873 > Project: ActiveMQ > Issue Type: Task > Components: Distribution >Affects Versions: 5.15.2 >Reporter: Hadrian Zbarcea >Assignee: Hadrian Zbarcea >Priority: Major > Fix For: 5.14.6, 5.16.0, 5.15.4 > > > Again there are a few inconsistencies in dependency management and a few > dependencies that have newer versions. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMQ-6873) Update dependencies
[ https://issues.apache.org/jira/browse/AMQ-6873?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christopher L. Shannon updated AMQ-6873: Fix Version/s: 5.15.4 > Update dependencies > --- > > Key: AMQ-6873 > URL: https://issues.apache.org/jira/browse/AMQ-6873 > Project: ActiveMQ > Issue Type: Task > Components: Distribution >Affects Versions: 5.15.2 >Reporter: Hadrian Zbarcea >Assignee: Hadrian Zbarcea >Priority: Major > Fix For: 5.14.6, 5.16.0, 5.15.4 > > > Again there are a few inconsistencies in dependency management and a few > dependencies that have newer versions. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMQ-6893) Security vulnerabilities in AMQ (black-duck)
Matan Keret created AMQ-6893: Summary: Security vulnerabilities in AMQ (black-duck) Key: AMQ-6893 URL: https://issues.apache.org/jira/browse/AMQ-6893 Project: ActiveMQ Issue Type: Bug Components: activemq-camel, activemq-leveldb-store, activemq-pool, AMQP Affects Versions: 5.15.2, 5.15.1 Reporter: Matan Keret In our organization's black-duck scan some critical security alerts came up, regarding several components used within the latest versions of AMQ. Here is the list: |Apache Camel2.0-M1| |Apache Camel2.19.0| |Apache Camel2.19.1| |Apache Commons Net3.6| |Apache Tomcat8.0.24| |Apache Tomcat8.0.33| |Apache Tomcat8.0.22| |Apache Tomcat1.2.3| |Apache Velocity1.7| |jackson-databind2.6.7| |Jetspeed-2 Enterprise Portal2.1.4| |log4j1.2.17| The majority of the issues are resolved within the latest versions of these dependencies. Is it planned to resolve these vulnerabilities in some upcoming version? -- This message was sent by Atlassian JIRA (v7.6.3#76005)
