[jira] [Resolved] (AMQ-7146) Support Spring 5 in OSGi
[ https://issues.apache.org/jira/browse/AMQ-7146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet resolved AMQ-7146. -- Resolution: Fixed Fix Version/s: 5.15.9 > Support Spring 5 in OSGi > > > Key: AMQ-7146 > URL: https://issues.apache.org/jira/browse/AMQ-7146 > Project: ActiveMQ > Issue Type: Task > Components: OSGi/Karaf >Reporter: Guillaume Nodet >Assignee: Guillaume Nodet >Priority: Major > Fix For: 5.15.9 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMQ-7146) Support Spring 5 in OSGi
Guillaume Nodet created AMQ-7146: Summary: Support Spring 5 in OSGi Key: AMQ-7146 URL: https://issues.apache.org/jira/browse/AMQ-7146 Project: ActiveMQ Issue Type: Task Components: OSGi/Karaf Reporter: Guillaume Nodet Assignee: Guillaume Nodet -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMQ-7060) Remove deprecated features from camel ActiveMQComponent
[ https://issues.apache.org/jira/browse/AMQ-7060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet updated AMQ-7060: - Fix Version/s: (was: 5.15.7) 5.15.8 > Remove deprecated features from camel ActiveMQComponent > --- > > Key: AMQ-7060 > URL: https://issues.apache.org/jira/browse/AMQ-7060 > Project: ActiveMQ > Issue Type: Task > Components: activemq-camel >Reporter: Guillaume Nodet >Assignee: Guillaume Nodet >Priority: Major > Fix For: 5.16.0, 5.15.8 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMQ-7060) Remove deprecated features from camel ActiveMQComponent
[ https://issues.apache.org/jira/browse/AMQ-7060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet updated AMQ-7060: - Fix Version/s: 5.15.7 > Remove deprecated features from camel ActiveMQComponent > --- > > Key: AMQ-7060 > URL: https://issues.apache.org/jira/browse/AMQ-7060 > Project: ActiveMQ > Issue Type: Task > Components: activemq-camel >Reporter: Guillaume Nodet >Assignee: Guillaume Nodet >Priority: Major > Fix For: 5.16.0, 5.15.7 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMQ-7060) Remove deprecated features from camel ActiveMQComponent
[ https://issues.apache.org/jira/browse/AMQ-7060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet resolved AMQ-7060. -- Resolution: Fixed Fix Version/s: 5.16.0 https://github.com/apache/activemq/commit/8cbc2080a737aad063bde7260ba8e7963ec0b206 > Remove deprecated features from camel ActiveMQComponent > --- > > Key: AMQ-7060 > URL: https://issues.apache.org/jira/browse/AMQ-7060 > Project: ActiveMQ > Issue Type: Task > Components: activemq-camel >Reporter: Guillaume Nodet >Assignee: Guillaume Nodet >Priority: Major > Fix For: 5.16.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMQ-7060) Remove deprecated features from camel ActiveMQComponent
Guillaume Nodet created AMQ-7060: Summary: Remove deprecated features from camel ActiveMQComponent Key: AMQ-7060 URL: https://issues.apache.org/jira/browse/AMQ-7060 Project: ActiveMQ Issue Type: Task Components: activemq-camel Reporter: Guillaume Nodet Assignee: Guillaume Nodet -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (ARTEMIS-1630) Create Artemis Client Karaf features
[ https://issues.apache.org/jira/browse/ARTEMIS-1630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet resolved ARTEMIS-1630. -- Resolution: Fixed Fix Version/s: 2.5.0 > Create Artemis Client Karaf features > > > Key: ARTEMIS-1630 > URL: https://issues.apache.org/jira/browse/ARTEMIS-1630 > Project: ActiveMQ Artemis > Issue Type: Improvement > Components: osgi >Affects Versions: 2.5.0 >Reporter: John Poth >Assignee: Guillaume Nodet >Priority: Major > Fix For: 2.5.0 > > > It would be nice to create Artemis client features that don't depend on > server side artifacts. > I'll submit a PR. Thanks! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (ARTEMIS-1630) Create Artemis Client Karaf features
[ https://issues.apache.org/jira/browse/ARTEMIS-1630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet reassigned ARTEMIS-1630: Assignee: Guillaume Nodet > Create Artemis Client Karaf features > > > Key: ARTEMIS-1630 > URL: https://issues.apache.org/jira/browse/ARTEMIS-1630 > Project: ActiveMQ Artemis > Issue Type: Improvement > Components: osgi >Affects Versions: 2.5.0 >Reporter: John Poth >Assignee: Guillaume Nodet >Priority: Major > > It would be nice to create Artemis client features that don't depend on > server side artifacts. > I'll submit a PR. Thanks! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (AMQ-6894) Excessive number of connections by failover transport with priorityBackup
[
https://issues.apache.org/jira/browse/AMQ-6894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guillaume Nodet reassigned AMQ-6894:
Assignee: Jean-Baptiste Onofré
> Excessive number of connections by failover transport with priorityBackup
> -
>
> Key: AMQ-6894
> URL: https://issues.apache.org/jira/browse/AMQ-6894
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
>Affects Versions: 5.14.5
>Reporter: Andrei Shakirin
>Assignee: Jean-Baptiste Onofré
>Priority: Major
> Attachments: activemq-part.zip
>
>
> My clients connect to AMQ with this connection string:
> (tcp://amq1:61616,tcp://amq2:61616)?randomize=false=true
> It works - for some time. But sooner or later my AMQ server becomes
> unresponsive because the host it runs on runs out of resources (threads).
> Suddenly AMQ Server log explodes with the messages like:
> {code}
> 2018-01-26 09:26:16,909 | WARN | Failed to register MBean
> org.apache.activemq
> :type=Broker,brokerName=activemq-vm-primary,connector=clientConnectors,connect
> orName=default,connectionViewType=clientId,connectionName=ID_ca8f70e115d0-3708
> 7-1516883370639-0_22 | org.apache.activemq.broker.jmx.ManagedTransportConnecti
> on | ActiveMQ Transport: tcp:///172.10.7.56:55548@61616
> 2018-01-26 09:26:21,375 | WARN | Ignoring ack received before dispatch;
> result of failover with an outstanding ack. Acked messages will be replayed
> if present on this broker. Ignored ack: MessageAck \{commandId = 157,
> responseRequired = false, ackType = 2, consumerId =
> ID:ca8f70e115d0-37087-1516883370639-1:22:10:1, firstMessageId =
> ID:a95345a9c0df-33771-1516883685728-1:17:5:1:23, lastMessageId =
> ID:a95345a9c0df-33771-1516883685728-1:17:5:1:23, destination =
> queue://MY_QUEUE_OUT, transactionId = null, messageCount = 1, poisonCause =
> null} | org.apache.activemq.broker.region.PrefetchSubscription | ActiveMQ
> Transport: tcp:///172.16.6.56:55464@61616
> 2018-01-26 09:26:39,211 | WARN | Transport Connection to:
> tcp://172.10.6.56:55860 failed: java.net.SocketException: Connection reset |
> org.apache.activemq.broker.TransportConnection.Transport | ActiveMQ
> InactivityMonitor Worker
> 2018-01-26 09:26:47,175 | WARN | Transport Connection to:
> tcp://172.10.6.56:57012 failed: java.net.SocketException: Broken pipe (Write
> failed) | org.apache.activemq.broker.TransportConnection.Transport | ActiveMQ
> InactivityMonitor Worker
> {code}
> After short period of time AMQ server comes out of resources with
> "java.lang.OutOfMemoryError: unable to create new native thread" error. The
> AMQ service process in this case has a huge number of threads (some thousands)
>
> The client side log contains a lot of reconnection attempts messages like:
> {code}
> 2018-01-26 00:10:31,387 WARN
> [\{{bundle.name,org.apache.activemq.activemq-osgi}{bundle.version,5.14.1}\{bundle.id,181}}]
> [null] org.apache.activemq.transport.failover.FailoverTransport
> Failed to connect to [tcp://activemq-vm-primary:61616,
> tcp://activemq-vm-secondary:61616] after: 810 attempt(s) continuing to retry.
> {code}
> It seems that client creates a huge number of connections by failover retry
> and after some time kills the server.
> Issue looks very similar to described in
> https://issues.apache.org/jira/browse/AMQ-6603, however server isn't
> configured with access control settings.
> I found the description of similar problem into
> [http://activemq.2283324.n4.nabble.com/ActiveMQ-5-2-OutOfMemoryError-unable-to-create-new-native-thread-td2366585.html],
> but without concrete suggestion.
>
> Part of server log is attached
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (ARTEMIS-1197) Missing browse permission on Karaf
[ https://issues.apache.org/jira/browse/ARTEMIS-1197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet resolved ARTEMIS-1197. -- Resolution: Fixed https://github.com/apache/activemq-artemis/commit/71fc3a8bb5e6d0da4a1ba889a6c7e62e7143a60f > Missing browse permission on Karaf > -- > > Key: ARTEMIS-1197 > URL: https://issues.apache.org/jira/browse/ARTEMIS-1197 > Project: ActiveMQ Artemis > Issue Type: Bug >Reporter: Guillaume Nodet >Assignee: Guillaume Nodet > Fix For: 2.2.0 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (ARTEMIS-1196) Unusable JSON api on Karaf
[ https://issues.apache.org/jira/browse/ARTEMIS-1196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet resolved ARTEMIS-1196. -- Resolution: Fixed https://github.com/apache/activemq-artemis/commit/b6dcff039f6c735d7ce89aa29ac001e91b88383d > Unusable JSON api on Karaf > -- > > Key: ARTEMIS-1196 > URL: https://issues.apache.org/jira/browse/ARTEMIS-1196 > Project: ActiveMQ Artemis > Issue Type: Bug >Reporter: Guillaume Nodet >Assignee: Guillaume Nodet > Fix For: 2.2.0 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (ARTEMIS-1176) Use text messages for management reply messages
[ https://issues.apache.org/jira/browse/ARTEMIS-1176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet resolved ARTEMIS-1176. -- Resolution: Fixed > Use text messages for management reply messages > --- > > Key: ARTEMIS-1176 > URL: https://issues.apache.org/jira/browse/ARTEMIS-1176 > Project: ActiveMQ Artemis > Issue Type: Improvement >Reporter: Guillaume Nodet >Assignee: Guillaume Nodet > Fix For: 2.2.0 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (ARTEMIS-1197) Missing browse permission on Karaf
Guillaume Nodet created ARTEMIS-1197: Summary: Missing browse permission on Karaf Key: ARTEMIS-1197 URL: https://issues.apache.org/jira/browse/ARTEMIS-1197 Project: ActiveMQ Artemis Issue Type: Bug Reporter: Guillaume Nodet Assignee: Guillaume Nodet Fix For: 2.2.0 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (ARTEMIS-1196) Unusable JSON api on Karaf
Guillaume Nodet created ARTEMIS-1196: Summary: Unusable JSON api on Karaf Key: ARTEMIS-1196 URL: https://issues.apache.org/jira/browse/ARTEMIS-1196 Project: ActiveMQ Artemis Issue Type: Bug Reporter: Guillaume Nodet Assignee: Guillaume Nodet Fix For: 2.2.0 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (ARTEMIS-1176) Use text messages for management reply messages
[
https://issues.apache.org/jira/browse/ARTEMIS-1176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16028813#comment-16028813
]
Guillaume Nodet commented on ARTEMIS-1176:
--
So the problem seems to be that the ActiveMQTextMessage which is built for the
response eagerly reads the body as a string, so that the ManagementHelper which
uses the ICoreMessage body can't work anymore as the body has been read already.
I see a few options:
* keep the response as a text message and fix the management layer to support
it (see patch below)
* investigate changing the JMS messages to lazily read the body (but this
could change some behavior)
* don't fix the issue (the original issue is that the management layer can't
be used with pure JMS api)
Patch for management layer:
{code}
diff --git
a/artemis-core-client/src/main/java/org/apache/activemq/artemis/api/core/management/ManagementHelper.java
b/artemis-core-client/src/main/java/org/apache/activemq/artemis/api/core/management/ManagementHelper.java
index 946285da8..20c0cd076 100644
---
a/artemis-core-client/src/main/java/org/apache/activemq/artemis/api/core/management/ManagementHelper.java
+++
b/artemis-core-client/src/main/java/org/apache/activemq/artemis/api/core/management/ManagementHelper.java
@@ -197,7 +197,16 @@ public final class ManagementHelper {
public static Object[] getResults(final ICoreMessage message) throws
Exception {
SimpleString sstring =
message.getBodyBuffer().readNullableSimpleString();
String jsonString = (sstring == null) ? null : sstring.toString();
+ return getResults(jsonString);
+ }
+ /**
+* Returns the result of an operation invocation or an attribute value.
+*
+* If an error occurred on the server, {@link
#hasOperationSucceeded(Message)} will return {@code false}.
+* and the result will be a String corresponding to the server exception.
+*/
+ public static Object[] getResults(final String jsonString) throws Exception
{
if (jsonString != null) {
JsonArray jsonArray = JsonUtil.readJsonArray(jsonString);
return JsonUtil.fromJsonArray(jsonArray);
@@ -233,6 +242,22 @@ public final class ManagementHelper {
}
/**
+* Returns the result of an operation invocation or an attribute value.
+*
+* If an error occurred on the server, {@link
#hasOperationSucceeded(Message)} will return {@code false}.
+* and the result will be a String corresponding to the server exception.
+*/
+ public static Object getResult(final String message, Class desiredType)
throws Exception {
+ Object[] res = ManagementHelper.getResults(message);
+
+ if (res != null) {
+ return JsonUtil.convertJsonValue(res[0], desiredType);
+ } else {
+ return null;
+ }
+ }
+
+ /**
* Returns whether the invocation of the management operation on the server
resource succeeded.
*/
public static boolean hasOperationSucceeded(final Message message) {
diff --git
a/artemis-jms-client/src/main/java/org/apache/activemq/artemis/api/jms/management/JMSManagementHelper.java
b/artemis-jms-client/src/main/java/org/apache/activemq/artemis/api/jms/management/JMSManagementHelper.java
index 4d0306ba5..b7ba4a695 100644
---
a/artemis-jms-client/src/main/java/org/apache/activemq/artemis/api/jms/management/JMSManagementHelper.java
+++
b/artemis-jms-client/src/main/java/org/apache/activemq/artemis/api/jms/management/JMSManagementHelper.java
@@ -18,6 +18,7 @@ package org.apache.activemq.artemis.api.jms.management;
import javax.jms.JMSException;
import javax.jms.Message;
+import javax.jms.TextMessage;
import org.apache.activemq.artemis.api.core.client.ClientMessage;
import org.apache.activemq.artemis.api.core.management.ManagementHelper;
@@ -147,7 +148,11 @@ public class JMSManagementHelper {
* and the result will be a String corresponding to the server exception.
*/
public static Object getResult(final Message message, Class desiredType)
throws Exception {
- return
ManagementHelper.getResult(JMSManagementHelper.getCoreMessage(message),
desiredType);
+ if (message instanceof TextMessage) {
+ return ManagementHelper.getResult(((TextMessage) message).getText(),
desiredType);
+ } else {
+ return
ManagementHelper.getResult(JMSManagementHelper.getCoreMessage(message),
desiredType);
+ }
}
private JMSManagementHelper() {
{code}
> Use text messages for management reply messages
> ---
>
> Key: ARTEMIS-1176
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1176
> Project: ActiveMQ Artemis
> Issue Type: Improvement
>Reporter: Guillaume Nodet
>Assignee: Guillaume Nodet
> Fix For: 2.2.0
>
>
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (ARTEMIS-1176) Use text messages for management reply messages
[ https://issues.apache.org/jira/browse/ARTEMIS-1176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16018317#comment-16018317 ] Guillaume Nodet commented on ARTEMIS-1176: -- PR https://github.com/apache/activemq-artemis/pull/1284 > Use text messages for management reply messages > --- > > Key: ARTEMIS-1176 > URL: https://issues.apache.org/jira/browse/ARTEMIS-1176 > Project: ActiveMQ Artemis > Issue Type: Improvement >Reporter: Guillaume Nodet >Assignee: Guillaume Nodet > Fix For: 2.2.0 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (ARTEMIS-1176) Use text messages for management reply messages
Guillaume Nodet created ARTEMIS-1176: Summary: Use text messages for management reply messages Key: ARTEMIS-1176 URL: https://issues.apache.org/jira/browse/ARTEMIS-1176 Project: ActiveMQ Artemis Issue Type: Improvement Reporter: Guillaume Nodet Assignee: Guillaume Nodet Fix For: 2.2.0 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (ARTEMIS-1141) Validate Karaf features using the karaf plugin
[
https://issues.apache.org/jira/browse/ARTEMIS-1141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15996269#comment-15996269
]
Guillaume Nodet commented on ARTEMIS-1141:
--
Yeah, this comes from the {{artemis-server-osgi}} bundle which exports the
{{io.netty.buffer}} package.
That's a bit weird. I'll fix it.
> Validate Karaf features using the karaf plugin
> --
>
> Key: ARTEMIS-1141
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1141
> Project: ActiveMQ Artemis
> Issue Type: Improvement
> Components: osgi
>Affects Versions: 2.0.0
>Reporter: Guillaume Nodet
>Assignee: Guillaume Nodet
> Fix For: 2.next
>
>
> The Karaf maven plugin provides a validation goal which run the OSGi resolver
> to ensure that the features can actually be installed in Karaf.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (ARTEMIS-1141) Validate Karaf features using the karaf plugin
[
https://issues.apache.org/jira/browse/ARTEMIS-1141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15995641#comment-15995641
]
Guillaume Nodet commented on ARTEMIS-1141:
--
Yeah, I was about to fix the missing {{netty-transport-native-epoll}} bundle
issue when I realized it was already fix, but then decided to leverage the
plugin in order to detect those problems at build time.
> Validate Karaf features using the karaf plugin
> --
>
> Key: ARTEMIS-1141
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1141
> Project: ActiveMQ Artemis
> Issue Type: Improvement
> Components: osgi
>Affects Versions: 2.0.0
>Reporter: Guillaume Nodet
>Assignee: Guillaume Nodet
> Fix For: 2.next
>
>
> The Karaf maven plugin provides a validation goal which run the OSGi resolver
> to ensure that the features can actually be installed in Karaf.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Comment Edited] (ARTEMIS-1141) Validate Karaf features using the karaf plugin
[ https://issues.apache.org/jira/browse/ARTEMIS-1141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15995615#comment-15995615 ] Guillaume Nodet edited comment on ARTEMIS-1141 at 5/3/17 8:35 PM: -- I ran the built with tests with no problems. Did I miss something ? I missed the ArtemisFeatureTest, but the feature could not be installed, so the test is definitely not working very well to detect failures. To the "how can that be used", the build ensures that you can't break the feature installation. Try removing an important bundle from a feature and you'll see the build will break. If a new package dependency is added which cause a new import to be added to one of the bundles, the build will also fail fast. was (Author: gnt): I ran the built with tests with no problems. Did I miss something ? I missed the ArtemisFeatureTest, but the feature can't be installed, so the test is definitely not working very well to detect failures. To the "how can that be used", the build ensures that you can't break the feature installation. Try removing an important bundle from a feature and you'll see the build will break. If a new package dependency is added which cause a new import to be added to one of the bundles, the build will also fail fast. > Validate Karaf features using the karaf plugin > -- > > Key: ARTEMIS-1141 > URL: https://issues.apache.org/jira/browse/ARTEMIS-1141 > Project: ActiveMQ Artemis > Issue Type: Improvement > Components: osgi >Affects Versions: 2.0.0 >Reporter: Guillaume Nodet >Assignee: Guillaume Nodet > Fix For: 2.next > > > The Karaf maven plugin provides a validation goal which run the OSGi resolver > to ensure that the features can actually be installed in Karaf. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (ARTEMIS-1141) Validate Karaf features using the karaf plugin
[ https://issues.apache.org/jira/browse/ARTEMIS-1141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15995615#comment-15995615 ] Guillaume Nodet commented on ARTEMIS-1141: -- I ran the built with tests with no problems. Did I miss something ? I missed the ArtemisFeatureTest, but the feature can't be installed, so the test is definitely not working very well to detect failures. To the "how can that be used", the build ensures that you can't break the feature installation. Try removing an important bundle from a feature and you'll see the build will break. If a new package dependency is added which cause a new import to be added to one of the bundles, the build will also fail fast. > Validate Karaf features using the karaf plugin > -- > > Key: ARTEMIS-1141 > URL: https://issues.apache.org/jira/browse/ARTEMIS-1141 > Project: ActiveMQ Artemis > Issue Type: Improvement > Components: osgi >Affects Versions: 2.0.0 >Reporter: Guillaume Nodet >Assignee: Guillaume Nodet > Fix For: 2.next > > > The Karaf maven plugin provides a validation goal which run the OSGi resolver > to ensure that the features can actually be installed in Karaf. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (ARTEMIS-1141) Validate Karaf features using the karaf plugin
[ https://issues.apache.org/jira/browse/ARTEMIS-1141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet resolved ARTEMIS-1141. -- Resolution: Fixed https://git-wip-us.apache.org/repos/asf?p=activemq-artemis.git;a=commitdiff;h=9e165d17336f23d86dbe34c2c910abfa17cc78c4 > Validate Karaf features using the karaf plugin > -- > > Key: ARTEMIS-1141 > URL: https://issues.apache.org/jira/browse/ARTEMIS-1141 > Project: ActiveMQ Artemis > Issue Type: Improvement > Components: osgi >Affects Versions: 2.0.0 >Reporter: Guillaume Nodet >Assignee: Guillaume Nodet > Fix For: 2.next > > > The Karaf maven plugin provides a validation goal which run the OSGi resolver > to ensure that the features can actually be installed in Karaf. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
