[jira] [Commented] (ARTEMIS-1541) Make the JDBC Node Manager more resilient on failures

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/ARTEMIS-1541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16292159#comment-16292159
 ] 

ASF GitHub Bot commented on ARTEMIS-1541:
-

GitHub user franz1981 reopened a pull request:

https://github.com/apache/activemq-artemis/pull/1691

ARTEMIS-1541 Make the JDBC Node Manager more resilient on failures

In order to make the JDBC Node Manager more resilient has been implemented:
- recovering with fixed number of retries during the NodeId setup + 
unrecoverable failure otherwise
- unrecoverable fail on exceptions while renewing a lease lock

In addition, in different parts of these critical processes are added more 
log informations to help diagnose.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/franz1981/activemq-artemis 
jdbc_ha_improvements

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/activemq-artemis/pull/1691.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1691


commit 70b21725edae28b591b87bb4de0f51364e9cfd50
Author: Francesco Nigro 
Date:   2017-12-06T10:28:59Z

ARTEMIS-1541 Make the JDBC Node Manager more resilient on failures

In order to make the JDBC Node Manager more resilient has been implemented:
- recovering with fixed number of retries during the NodeId setup + 
unrecoverable failure otherwise
- unrecoverable fail on exceptions while renewing a lease lock

In addition, in different parts of these critical processes are added more 
log informations to help diagnose.




> Make the JDBC Node Manager more resilient on failures
> -
>
> Key: ARTEMIS-1541
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1541
> Project: ActiveMQ Artemis
>  Issue Type: Improvement
>  Components: Broker
>Reporter: Francesco Nigro
>Assignee: Francesco Nigro
>
> The JDBC Node Manager isn't showing (at any level) errors on setup and hasn't 
> any policy to fail or recover while executing certain critical operations.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Resolved] (ARTEMIS-1504) AMQP: Update Qpid JMS to latest 0.28.0 release and Proton-j to 0.24.0 to match

[Timothy Bish (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ARTEMIS-1504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Timothy Bish resolved ARTEMIS-1504.
---
Resolution: Fixed

> AMQP: Update Qpid JMS to latest 0.28.0 release and Proton-j to 0.24.0 to match
> --
>
> Key: ARTEMIS-1504
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1504
> Project: ActiveMQ Artemis
>  Issue Type: Task
>  Components: AMQP
>Affects Versions: 2.4.0
>Reporter: Timothy Bish
>Assignee: Timothy Bish
>Priority: Minor
> Fix For: 2.5.0
>
>
> Update to latest Qpid-JMS release and match its Proton-J dependency. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Resolved] (ARTEMIS-1558) Message Grouping Openwire Interoperability Issue

[Howard Gao (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ARTEMIS-1558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Howard Gao resolved ARTEMIS-1558.
-
Resolution: Fixed

> Message Grouping Openwire Interoperability Issue
> 
>
> Key: ARTEMIS-1558
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1558
> Project: ActiveMQ Artemis
>  Issue Type: Bug
>  Components: OpenWire
>Affects Versions: 2.4.0
>Reporter: Howard Gao
>Assignee: Howard Gao
> Fix For: 2.5.0
>
>
> Openwire message grouping doesn't work because the groupID of a message is 
> not passed correctly.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (ARTEMIS-1558) Message Grouping Openwire Interoperability Issue

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/ARTEMIS-1558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16291943#comment-16291943
 ] 

ASF subversion and git services commented on ARTEMIS-1558:
--

Commit 1c156e0d47c164e15fc5a469e2b26252b634a178 in activemq-artemis's branch 
refs/heads/master from [~gaohoward]
[ https://git-wip-us.apache.org/repos/asf?p=activemq-artemis.git;h=1c156e0 ]

ARTEMIS-1558 Message Grouping Openwire Interoperability Issue

Openwire message grouping doesn't work because the groupID of
a message is not passed correctly.


> Message Grouping Openwire Interoperability Issue
> 
>
> Key: ARTEMIS-1558
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1558
> Project: ActiveMQ Artemis
>  Issue Type: Bug
>  Components: OpenWire
>Affects Versions: 2.4.0
>Reporter: Howard Gao
>Assignee: Howard Gao
> Fix For: 2.5.0
>
>
> Openwire message grouping doesn't work because the groupID of a message is 
> not passed correctly.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (ARTEMIS-1558) Message Grouping Openwire Interoperability Issue

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/ARTEMIS-1558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16291944#comment-16291944
 ] 

ASF GitHub Bot commented on ARTEMIS-1558:
-

Github user asfgit closed the pull request at:

https://github.com/apache/activemq-artemis/pull/1710


> Message Grouping Openwire Interoperability Issue
> 
>
> Key: ARTEMIS-1558
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1558
> Project: ActiveMQ Artemis
>  Issue Type: Bug
>  Components: OpenWire
>Affects Versions: 2.4.0
>Reporter: Howard Gao
>Assignee: Howard Gao
> Fix For: 2.5.0
>
>
> Openwire message grouping doesn't work because the groupID of a message is 
> not passed correctly.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (ARTEMIS-1553) JSON values all being converted to String

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/ARTEMIS-1553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16291936#comment-16291936
 ] 

ASF GitHub Bot commented on ARTEMIS-1553:
-

Github user jbertram commented on the issue:

https://github.com/apache/activemq-artemis/pull/1704
  
BTW, this is related to 2f299334465d6acace1d856079f2f294d8a54914 which was 
done as part of ARTEMIS-1540.  It introduced this regression.


> JSON values all being converted to String
> -
>
> Key: ARTEMIS-1553
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1553
> Project: ActiveMQ Artemis
>  Issue Type: Bug
>Reporter: Justin Bertram
>Assignee: Justin Bertram
> Fix For: 2.5.0
>
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (ARTEMIS-1553) JSON values all being converted to String

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/ARTEMIS-1553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16291934#comment-16291934
 ] 

ASF GitHub Bot commented on ARTEMIS-1553:
-

Github user jbertram commented on the issue:

https://github.com/apache/activemq-artemis/pull/1704
  
I'm not sure what the failure was in the PR build as it's already been 
deleted.  I ran the PR build locally and it was successful.


> JSON values all being converted to String
> -
>
> Key: ARTEMIS-1553
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1553
> Project: ActiveMQ Artemis
>  Issue Type: Bug
>Reporter: Justin Bertram
>Assignee: Justin Bertram
> Fix For: 2.5.0
>
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (ARTEMIS-1555) MQTT - Unsubscribe topic in cluster environment leaves reference to the consumer

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/ARTEMIS-1555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16291931#comment-16291931
 ] 

ASF GitHub Bot commented on ARTEMIS-1555:
-

Github user jbertram commented on the issue:

https://github.com/apache/activemq-artemis/pull/1706
  
Couple of things...

- Brokers used in tests should be configured programmatically rather than 
using file-based XML config.
- There are lots of XSD changes which seem unrelated to the commit
- The commit message is incomplete.


> MQTT - Unsubscribe topic in cluster environment leaves reference to the 
> consumer
> 
>
> Key: ARTEMIS-1555
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1555
> Project: ActiveMQ Artemis
>  Issue Type: Bug
>Reporter: Raul Valdoleiros
>Priority: Blocker
>
> The use case is:
> * Subscribe queue A in broker 1
> * Subscribe queue A in broker 2
> * Send messages to queue A in broker 1
> * Process messages in the two subscribers
> * Unsubscribe queue A in broker 2
> * Send messages to queue A in broker 1
> * Some messages aren't delivered in subscriber of broker 1



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (ARTEMIS-1504) AMQP: Update Qpid JMS to latest 0.28.0 release and Proton-j to 0.24.0 to match

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/ARTEMIS-1504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16291924#comment-16291924
 ] 

ASF subversion and git services commented on ARTEMIS-1504:
--

Commit 5aacb502faf025c10a3de5d88627de73eabc610d in activemq-artemis's branch 
refs/heads/master from [~tabish121]
[ https://git-wip-us.apache.org/repos/asf?p=activemq-artemis.git;h=5aacb50 ]

ARTEMIS-1504 Update Qpid JMS to 0.28.0 and proton-j to 0.24.0

Updates to latest Qpid JMS and the latest Proton-J release 

> AMQP: Update Qpid JMS to latest 0.28.0 release and Proton-j to 0.24.0 to match
> --
>
> Key: ARTEMIS-1504
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1504
> Project: ActiveMQ Artemis
>  Issue Type: Task
>  Components: AMQP
>Affects Versions: 2.4.0
>Reporter: Timothy Bish
>Assignee: Timothy Bish
>Priority: Minor
> Fix For: 2.5.0
>
>
> Update to latest Qpid-JMS release and match its Proton-J dependency. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (ARTEMIS-1504) AMQP: Update Qpid JMS to latest 0.28.0 release and Proton-j to 0.24.0 to match

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/ARTEMIS-1504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16291925#comment-16291925
 ] 

ASF GitHub Bot commented on ARTEMIS-1504:
-

Github user asfgit closed the pull request at:

https://github.com/apache/activemq-artemis/pull/1714


> AMQP: Update Qpid JMS to latest 0.28.0 release and Proton-j to 0.24.0 to match
> --
>
> Key: ARTEMIS-1504
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1504
> Project: ActiveMQ Artemis
>  Issue Type: Task
>  Components: AMQP
>Affects Versions: 2.4.0
>Reporter: Timothy Bish
>Assignee: Timothy Bish
>Priority: Minor
> Fix For: 2.5.0
>
>
> Update to latest Qpid-JMS release and match its Proton-J dependency. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (ARTEMIS-1552) SASL GSSAPI IBM JDK - clients get authentication refused first time they connect to broker

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/ARTEMIS-1552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16291905#comment-16291905
 ] 

ASF subversion and git services commented on ARTEMIS-1552:
--

Commit b62e9875fed987f341b946082f4e28866e54b979 in activemq-artemis's branch 
refs/heads/master from [~gtully]
[ https://git-wip-us.apache.org/repos/asf?p=activemq-artemis.git;h=b62e987 ]

[ARTEMIS-1552] ensure gssapi sasl mech can deal with empty receive buffer


> SASL GSSAPI IBM JDK - clients get authentication refused first time they 
> connect to broker
> --
>
> Key: ARTEMIS-1552
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1552
> Project: ActiveMQ Artemis
>  Issue Type: Bug
>  Components: AMQP
>Affects Versions: 2.4.0
>Reporter: Gary Tully
>Assignee: Gary Tully
> Fix For: 2.5.0
>
>
> {code}
> [JGSS_DBG_WRAP]  Thread-18 
> (ActiveMQ-server-org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl$5@d7b0af0d)
>  GSSContextImpl.unwrap buffer (len=0, offset=0):
> [JGSS_DBG_WRAP]  Thread-18 
> (ActiveMQ-server-org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl$5@d7b0af0d)
>  
> [JGSS_DBG_WRAP]  Thread-18 
> (ActiveMQ-server-org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl$5@d7b0af0d)
>  Krb5Context.unwrap: buffer (len=0, offset=0):
> [JGSS_DBG_WRAP]  Thread-18 
> (ActiveMQ-server-org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl$5@d7b0af0d)
>  
> [JGSS_DBG_UNMARSH]  Thread-18 
> (ActiveMQ-server-org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl$5@d7b0af0d)
>  AES256WrapToken.decode: buffer :
> [JGSS_DBG_UNMARSH]  Thread-18 
> (ActiveMQ-server-org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl$5@d7b0af0d)
>  
> 14:23:14.955 INFO  
> [org.apache.activemq.artemis.protocol.amqp.sasl.GSSAPIServerSASL] Error on 
> sasl input: java.security.PrivilegedActionException: 
> javax.security.sasl.SaslException: Final handshake step failed [Caused by 
> org.ietf.jgss.GSSException, major code: 11, minor code: 0
>   major string: General failure, unspecified at GSSAPI level
>   minor string: Error while decoding token: 
> java.lang.ArrayIndexOutOfBoundsException: Array index out of range: 0]: 
> java.security.PrivilegedActionException: javax.security.sasl.SaslException: 
> Final handshake step failed [Caused by org.ietf.jgss.GSSException, major 
> code: 11, minor code: 0
>   major string: General failure, unspecified at GSSAPI level
>   minor string: Error while decoding token: 
> java.lang.ArrayIndexOutOfBoundsException: Array index out of range: 0]
>   at 
> java.security.AccessController.doPrivileged(AccessController.java:692) 
> [vm.jar:1.8.0]
>   at javax.security.auth.Subject.doAs(Subject.java:569) [rt.jar:1.8.0]
>   at 
> org.apache.activemq.artemis.protocol.amqp.sasl.GSSAPIServerSASL.processSASL(GSSAPIServerSASL.java:77)
>  []
>   at 
> org.apache.activemq.artemis.protocol.amqp.proton.handler.ProtonHandler.checkSASL(ProtonHandler.java:315)
>  []
>   at 
> org.apache.activemq.artemis.protocol.amqp.proton.handler.ProtonHandler.flush(ProtonHandler.java:274)
>  []
>   at 
> org.apache.activemq.artemis.protocol.amqp.proton.AMQPConnectionContext.flush(AMQPConnectionContext.java:178)
>  []
>   at 
> org.apache.activemq.artemis.protocol.amqp.broker.ActiveMQProtonRemotingConnection.flush(ActiveMQProtonRemotingConnection.java:136)
>  []
>   at 
> org.apache.activemq.artemis.core.remoting.server.impl.RemotingServiceImpl$FailureCheckAndFlushThread$1.run(RemotingServiceImpl.java:715)
>  []
>   at 
> org.apache.activemq.artemis.utils.actors.OrderedExecutor.doTask(OrderedExecutor.java:42)
>  []
>   at 
> org.apache.activemq.artemis.utils.actors.OrderedExecutor.doTask(OrderedExecutor.java:31)
>  []
>   at 
> org.apache.activemq.artemis.utils.actors.ProcessorBase$ExecutorTask.run(ProcessorBase.java:53)
>  []
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1160)
>  [rt.jar:1.8.0]
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
>  [rt.jar:1.8.0]
>   at java.lang.Thread.run(Thread.java:785) [vm.jar:2.6 (07-22-2017)]{code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (ARTEMIS-1552) SASL GSSAPI IBM JDK - clients get authentication refused first time they connect to broker

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/ARTEMIS-1552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16291906#comment-16291906
 ] 

ASF GitHub Bot commented on ARTEMIS-1552:
-

Github user asfgit closed the pull request at:

https://github.com/apache/activemq-artemis/pull/1703


> SASL GSSAPI IBM JDK - clients get authentication refused first time they 
> connect to broker
> --
>
> Key: ARTEMIS-1552
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1552
> Project: ActiveMQ Artemis
>  Issue Type: Bug
>  Components: AMQP
>Affects Versions: 2.4.0
>Reporter: Gary Tully
>Assignee: Gary Tully
> Fix For: 2.5.0
>
>
> {code}
> [JGSS_DBG_WRAP]  Thread-18 
> (ActiveMQ-server-org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl$5@d7b0af0d)
>  GSSContextImpl.unwrap buffer (len=0, offset=0):
> [JGSS_DBG_WRAP]  Thread-18 
> (ActiveMQ-server-org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl$5@d7b0af0d)
>  
> [JGSS_DBG_WRAP]  Thread-18 
> (ActiveMQ-server-org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl$5@d7b0af0d)
>  Krb5Context.unwrap: buffer (len=0, offset=0):
> [JGSS_DBG_WRAP]  Thread-18 
> (ActiveMQ-server-org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl$5@d7b0af0d)
>  
> [JGSS_DBG_UNMARSH]  Thread-18 
> (ActiveMQ-server-org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl$5@d7b0af0d)
>  AES256WrapToken.decode: buffer :
> [JGSS_DBG_UNMARSH]  Thread-18 
> (ActiveMQ-server-org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl$5@d7b0af0d)
>  
> 14:23:14.955 INFO  
> [org.apache.activemq.artemis.protocol.amqp.sasl.GSSAPIServerSASL] Error on 
> sasl input: java.security.PrivilegedActionException: 
> javax.security.sasl.SaslException: Final handshake step failed [Caused by 
> org.ietf.jgss.GSSException, major code: 11, minor code: 0
>   major string: General failure, unspecified at GSSAPI level
>   minor string: Error while decoding token: 
> java.lang.ArrayIndexOutOfBoundsException: Array index out of range: 0]: 
> java.security.PrivilegedActionException: javax.security.sasl.SaslException: 
> Final handshake step failed [Caused by org.ietf.jgss.GSSException, major 
> code: 11, minor code: 0
>   major string: General failure, unspecified at GSSAPI level
>   minor string: Error while decoding token: 
> java.lang.ArrayIndexOutOfBoundsException: Array index out of range: 0]
>   at 
> java.security.AccessController.doPrivileged(AccessController.java:692) 
> [vm.jar:1.8.0]
>   at javax.security.auth.Subject.doAs(Subject.java:569) [rt.jar:1.8.0]
>   at 
> org.apache.activemq.artemis.protocol.amqp.sasl.GSSAPIServerSASL.processSASL(GSSAPIServerSASL.java:77)
>  []
>   at 
> org.apache.activemq.artemis.protocol.amqp.proton.handler.ProtonHandler.checkSASL(ProtonHandler.java:315)
>  []
>   at 
> org.apache.activemq.artemis.protocol.amqp.proton.handler.ProtonHandler.flush(ProtonHandler.java:274)
>  []
>   at 
> org.apache.activemq.artemis.protocol.amqp.proton.AMQPConnectionContext.flush(AMQPConnectionContext.java:178)
>  []
>   at 
> org.apache.activemq.artemis.protocol.amqp.broker.ActiveMQProtonRemotingConnection.flush(ActiveMQProtonRemotingConnection.java:136)
>  []
>   at 
> org.apache.activemq.artemis.core.remoting.server.impl.RemotingServiceImpl$FailureCheckAndFlushThread$1.run(RemotingServiceImpl.java:715)
>  []
>   at 
> org.apache.activemq.artemis.utils.actors.OrderedExecutor.doTask(OrderedExecutor.java:42)
>  []
>   at 
> org.apache.activemq.artemis.utils.actors.OrderedExecutor.doTask(OrderedExecutor.java:31)
>  []
>   at 
> org.apache.activemq.artemis.utils.actors.ProcessorBase$ExecutorTask.run(ProcessorBase.java:53)
>  []
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1160)
>  [rt.jar:1.8.0]
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
>  [rt.jar:1.8.0]
>   at java.lang.Thread.run(Thread.java:785) [vm.jar:2.6 (07-22-2017)]{code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (ARTEMIS-1548) Support CRL

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/ARTEMIS-1548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16291632#comment-16291632
 ] 

ASF GitHub Bot commented on ARTEMIS-1548:
-

Github user jbertram commented on a diff in the pull request:

https://github.com/apache/activemq-artemis/pull/1715#discussion_r157065620
  
--- Diff: 
tests/integration-tests/src/test/java/org/apache/activemq/artemis/tests/integration/mqtt/imported/MQTTSecurityCRLTest.java
 ---
@@ -0,0 +1,357 @@
+/**
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements.  See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License.  You may obtain a copy of the License at
+ * 
+ * http://www.apache.org/licenses/LICENSE-2.0
+ * 
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+package org.apache.activemq.artemis.tests.integration.mqtt.imported;
+
+import java.io.ByteArrayInputStream;
+import java.io.ByteArrayOutputStream;
+import java.io.File;
+import java.io.FileInputStream;
+import java.io.IOException;
+import java.security.KeyStore;
+import java.security.ProtectionDomain;
+import java.util.HashSet;
+import java.util.Set;
+import java.util.concurrent.TimeUnit;
+import javax.net.ssl.KeyManager;
+import javax.net.ssl.KeyManagerFactory;
+import javax.net.ssl.SSLContext;
+import javax.net.ssl.SSLException;
+import javax.net.ssl.TrustManager;
+import javax.net.ssl.TrustManagerFactory;
+import org.apache.activemq.artemis.api.core.TransportConfiguration;
+import org.apache.activemq.artemis.core.config.Configuration;
+import org.apache.activemq.artemis.core.config.WildcardConfiguration;
+import org.apache.activemq.artemis.core.config.impl.FileConfiguration;
+import 
org.apache.activemq.artemis.core.remoting.impl.netty.NettyAcceptorFactory;
+import 
org.apache.activemq.artemis.core.remoting.impl.netty.TransportConstants;
+import org.apache.activemq.artemis.core.security.Role;
+import org.apache.activemq.artemis.core.server.ActiveMQServer;
+import org.apache.activemq.artemis.core.settings.HierarchicalRepository;
+import 
org.apache.activemq.artemis.spi.core.security.ActiveMQJAASSecurityManager;
+import org.apache.activemq.artemis.tests.util.ActiveMQTestBase;
+import org.fusesource.mqtt.client.BlockingConnection;
+import org.fusesource.mqtt.client.MQTT;
+import org.fusesource.mqtt.client.Message;
+import org.fusesource.mqtt.client.QoS;
+import org.fusesource.mqtt.client.Topic;
+import org.junit.Test;
+
+public class MQTTSecurityCRLTest extends ActiveMQTestBase {
+
+
+   /**
+* These artifacts are required for testing mqtt with CRL
+* 
+* openssl genrsa -out ca.key 2048
+* openssl req -new -x509 -days 1826 -key ca.key -out ca.crt
+* touch certindex
+* echo 01 > certserial
+* echo 01 > crlnumber
+* 
+* Create ca.conf file with
+* 
+* # Mainly copied from:
+* # http://swearingscience.com/2009/01/18/openssl-self-signed-ca/
+* 
+* [ ca ]
+* default_ca = myca
+* 
+* [ crl_ext ]
+* # issuerAltName=issuer:copy #this would copy the issuer name to 
altname
+* authorityKeyIdentifier=keyid:always
+* 
+* [ myca ]
+* dir = ./
+* new_certs_dir = $dir
+* unique_subject = no
+* certificate = $dir/ca.crt
+* database = $dir/certindex
+* private_key = $dir/ca.key
+* serial = $dir/certserial
+* default_days = 730
+* default_md = sha1
+* policy = myca_policy
+* x509_extensions = myca_extensions
+* crlnumber = $dir/crlnumber
+* default_crl_days = 730
+* 
+* [ myca_policy ]
+* commonName = supplied
+* stateOrProvinceName = supplied
+* countryName = optional
+* emailAddress = optional
+* organizationName = supplied
+* organizationalUnitName = optional
+* 
+* [ myca_extensions ]
+* basicConstraints = CA:false
+* subjectKeyIdentifier = hash
+* authorityKeyIdentifier = keyid:always
+* keyUsage = digitalSignature,keyEncipherment
+* extendedKeyUsage = serverAuth, 

[jira] [Commented] (AMQ-6875) Virtual destination consumers can create invalid demand for Virtual Topics

[Christopher L. Shannon (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMQ-6875?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16291628#comment-16291628
 ] 

Christopher L. Shannon commented on AMQ-6875:
-

This is fixed.  Finding the correct topic requires a little bit of overhead but 
this is only done if useVirtualDestSubs is set to true and a new virtual topic 
demand advisory is sent (ie when the consumer comes online) so it shouldn't be 
run very often unless there are consumers constantly coming online/offline 
which would cause a lot more cpu in other places as well.  Also, the arrays 
that are being manipulated/copied are going to generally be very small as they 
are just the size of a tokenized destination name.  If for some reason this 
ends up being a performance hit then the resulting computed topics could be 
stored into a cache so they only have to get computed once per destination.

> Virtual destination consumers can create invalid demand for Virtual Topics
> --
>
> Key: AMQ-6875
> URL: https://issues.apache.org/jira/browse/AMQ-6875
> Project: ActiveMQ
>  Issue Type: Bug
>  Components: Broker, networkbridge
>Affects Versions: 5.15.2
>Reporter: Christopher L. Shannon
>Assignee: Christopher L. Shannon
> Fix For: 5.16.0, 5.15.3
>
>
> When testing out Virtual topics over a network bridge that has the virtual 
> destination consumers feature enabled I noticed that the consumer advisories 
> were wrong.  The destinations sent as part of the consumer advisories to 
> create demand over the bridge are using the name of the Virtual Topic.  
> This is causing extra demand to flow across the network bridge in some cases 
> because by default the VirtualTopic name is "VirtualTopic.>" .  So once one 
> Virtual Topic is created on a remote broker then any messages sent to 
> "VirtualTopic.>" on the local broker will be forwarded over to the other 
> broker even if there is no VirtualTopic matching.
> The solution is to make sure to use the actual topic that the VirtualTopic is 
> subscribed to as part of the advisory messags.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Resolved] (AMQ-6875) Virtual destination consumers can create invalid demand for Virtual Topics

[Christopher L. Shannon (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMQ-6875?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Christopher L. Shannon resolved AMQ-6875.
-
Resolution: Fixed

> Virtual destination consumers can create invalid demand for Virtual Topics
> --
>
> Key: AMQ-6875
> URL: https://issues.apache.org/jira/browse/AMQ-6875
> Project: ActiveMQ
>  Issue Type: Bug
>  Components: Broker, networkbridge
>Affects Versions: 5.15.2
>Reporter: Christopher L. Shannon
>Assignee: Christopher L. Shannon
> Fix For: 5.16.0, 5.15.3
>
>
> When testing out Virtual topics over a network bridge that has the virtual 
> destination consumers feature enabled I noticed that the consumer advisories 
> were wrong.  The destinations sent as part of the consumer advisories to 
> create demand over the bridge are using the name of the Virtual Topic.  
> This is causing extra demand to flow across the network bridge in some cases 
> because by default the VirtualTopic name is "VirtualTopic.>" .  So once one 
> Virtual Topic is created on a remote broker then any messages sent to 
> "VirtualTopic.>" on the local broker will be forwarded over to the other 
> broker even if there is no VirtualTopic matching.
> The solution is to make sure to use the actual topic that the VirtualTopic is 
> subscribed to as part of the advisory messags.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (ARTEMIS-1548) Support CRL

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/ARTEMIS-1548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16291624#comment-16291624
 ] 

ASF GitHub Bot commented on ARTEMIS-1548:
-

Github user jbertram commented on a diff in the pull request:

https://github.com/apache/activemq-artemis/pull/1715#discussion_r157064556
  
--- Diff: 
tests/integration-tests/src/test/java/org/apache/activemq/artemis/tests/integration/mqtt/imported/MQTTSecurityCRLTest.java
 ---
@@ -0,0 +1,357 @@
+/**
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements.  See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License.  You may obtain a copy of the License at
+ * 
+ * http://www.apache.org/licenses/LICENSE-2.0
+ * 
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+package org.apache.activemq.artemis.tests.integration.mqtt.imported;
+
+import java.io.ByteArrayInputStream;
+import java.io.ByteArrayOutputStream;
+import java.io.File;
+import java.io.FileInputStream;
+import java.io.IOException;
+import java.security.KeyStore;
+import java.security.ProtectionDomain;
+import java.util.HashSet;
+import java.util.Set;
+import java.util.concurrent.TimeUnit;
+import javax.net.ssl.KeyManager;
+import javax.net.ssl.KeyManagerFactory;
+import javax.net.ssl.SSLContext;
+import javax.net.ssl.SSLException;
+import javax.net.ssl.TrustManager;
+import javax.net.ssl.TrustManagerFactory;
+import org.apache.activemq.artemis.api.core.TransportConfiguration;
+import org.apache.activemq.artemis.core.config.Configuration;
+import org.apache.activemq.artemis.core.config.WildcardConfiguration;
+import org.apache.activemq.artemis.core.config.impl.FileConfiguration;
+import 
org.apache.activemq.artemis.core.remoting.impl.netty.NettyAcceptorFactory;
+import 
org.apache.activemq.artemis.core.remoting.impl.netty.TransportConstants;
+import org.apache.activemq.artemis.core.security.Role;
+import org.apache.activemq.artemis.core.server.ActiveMQServer;
+import org.apache.activemq.artemis.core.settings.HierarchicalRepository;
+import 
org.apache.activemq.artemis.spi.core.security.ActiveMQJAASSecurityManager;
+import org.apache.activemq.artemis.tests.util.ActiveMQTestBase;
+import org.fusesource.mqtt.client.BlockingConnection;
+import org.fusesource.mqtt.client.MQTT;
+import org.fusesource.mqtt.client.Message;
+import org.fusesource.mqtt.client.QoS;
+import org.fusesource.mqtt.client.Topic;
+import org.junit.Test;
+
+public class MQTTSecurityCRLTest extends ActiveMQTestBase {
+
+
+   /**
+* These artifacts are required for testing mqtt with CRL
+* 
+* openssl genrsa -out ca.key 2048
+* openssl req -new -x509 -days 1826 -key ca.key -out ca.crt
+* touch certindex
+* echo 01 > certserial
+* echo 01 > crlnumber
+* 
+* Create ca.conf file with
+* 
+* # Mainly copied from:
+* # http://swearingscience.com/2009/01/18/openssl-self-signed-ca/
+* 
+* [ ca ]
+* default_ca = myca
+* 
+* [ crl_ext ]
+* # issuerAltName=issuer:copy #this would copy the issuer name to 
altname
+* authorityKeyIdentifier=keyid:always
+* 
+* [ myca ]
+* dir = ./
+* new_certs_dir = $dir
+* unique_subject = no
+* certificate = $dir/ca.crt
+* database = $dir/certindex
+* private_key = $dir/ca.key
+* serial = $dir/certserial
+* default_days = 730
+* default_md = sha1
+* policy = myca_policy
+* x509_extensions = myca_extensions
+* crlnumber = $dir/crlnumber
+* default_crl_days = 730
+* 
+* [ myca_policy ]
+* commonName = supplied
+* stateOrProvinceName = supplied
+* countryName = optional
+* emailAddress = optional
+* organizationName = supplied
+* organizationalUnitName = optional
+* 
+* [ myca_extensions ]
+* basicConstraints = CA:false
+* subjectKeyIdentifier = hash
+* authorityKeyIdentifier = keyid:always
+* keyUsage = digitalSignature,keyEncipherment
+* extendedKeyUsage = serverAuth, 

[jira] [Commented] (ARTEMIS-1548) Support CRL

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/ARTEMIS-1548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16291619#comment-16291619
 ] 

ASF GitHub Bot commented on ARTEMIS-1548:
-

Github user jbertram commented on a diff in the pull request:

https://github.com/apache/activemq-artemis/pull/1715#discussion_r157064083
  
--- Diff: 
tests/integration-tests/src/test/java/org/apache/activemq/artemis/tests/integration/mqtt/imported/MQTTSecurityCRLTest.java
 ---
@@ -0,0 +1,357 @@
+/**
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements.  See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License.  You may obtain a copy of the License at
+ * 
+ * http://www.apache.org/licenses/LICENSE-2.0
+ * 
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+package org.apache.activemq.artemis.tests.integration.mqtt.imported;
+
+import java.io.ByteArrayInputStream;
+import java.io.ByteArrayOutputStream;
+import java.io.File;
+import java.io.FileInputStream;
+import java.io.IOException;
+import java.security.KeyStore;
+import java.security.ProtectionDomain;
+import java.util.HashSet;
+import java.util.Set;
+import java.util.concurrent.TimeUnit;
+import javax.net.ssl.KeyManager;
+import javax.net.ssl.KeyManagerFactory;
+import javax.net.ssl.SSLContext;
+import javax.net.ssl.SSLException;
+import javax.net.ssl.TrustManager;
+import javax.net.ssl.TrustManagerFactory;
+import org.apache.activemq.artemis.api.core.TransportConfiguration;
+import org.apache.activemq.artemis.core.config.Configuration;
+import org.apache.activemq.artemis.core.config.WildcardConfiguration;
+import org.apache.activemq.artemis.core.config.impl.FileConfiguration;
+import 
org.apache.activemq.artemis.core.remoting.impl.netty.NettyAcceptorFactory;
+import 
org.apache.activemq.artemis.core.remoting.impl.netty.TransportConstants;
+import org.apache.activemq.artemis.core.security.Role;
+import org.apache.activemq.artemis.core.server.ActiveMQServer;
+import org.apache.activemq.artemis.core.settings.HierarchicalRepository;
+import 
org.apache.activemq.artemis.spi.core.security.ActiveMQJAASSecurityManager;
+import org.apache.activemq.artemis.tests.util.ActiveMQTestBase;
+import org.fusesource.mqtt.client.BlockingConnection;
+import org.fusesource.mqtt.client.MQTT;
+import org.fusesource.mqtt.client.Message;
+import org.fusesource.mqtt.client.QoS;
+import org.fusesource.mqtt.client.Topic;
+import org.junit.Test;
+
+public class MQTTSecurityCRLTest extends ActiveMQTestBase {
+
+
+   /**
+* These artifacts are required for testing mqtt with CRL
+* 
+* openssl genrsa -out ca.key 2048
+* openssl req -new -x509 -days 1826 -key ca.key -out ca.crt
+* touch certindex
+* echo 01 > certserial
+* echo 01 > crlnumber
+* 
+* Create ca.conf file with
+* 
+* # Mainly copied from:
+* # http://swearingscience.com/2009/01/18/openssl-self-signed-ca/
+* 
+* [ ca ]
+* default_ca = myca
+* 
+* [ crl_ext ]
+* # issuerAltName=issuer:copy #this would copy the issuer name to 
altname
+* authorityKeyIdentifier=keyid:always
+* 
+* [ myca ]
+* dir = ./
+* new_certs_dir = $dir
+* unique_subject = no
+* certificate = $dir/ca.crt
+* database = $dir/certindex
+* private_key = $dir/ca.key
+* serial = $dir/certserial
+* default_days = 730
+* default_md = sha1
+* policy = myca_policy
+* x509_extensions = myca_extensions
+* crlnumber = $dir/crlnumber
+* default_crl_days = 730
+* 
+* [ myca_policy ]
+* commonName = supplied
+* stateOrProvinceName = supplied
+* countryName = optional
+* emailAddress = optional
+* organizationName = supplied
+* organizationalUnitName = optional
+* 
+* [ myca_extensions ]
+* basicConstraints = CA:false
+* subjectKeyIdentifier = hash
+* authorityKeyIdentifier = keyid:always
+* keyUsage = digitalSignature,keyEncipherment
+* extendedKeyUsage = serverAuth, 

[jira] [Commented] (AMQ-6875) Virtual destination consumers can create invalid demand for Virtual Topics

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMQ-6875?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16291591#comment-16291591
 ] 

ASF subversion and git services commented on AMQ-6875:
--

Commit 94aea677acab41fc8ba425c9fefc9c351fb31a94 in activemq's branch 
refs/heads/activemq-5.15.x from [~cshannon]
[ https://git-wip-us.apache.org/repos/asf?p=activemq.git;h=94aea67 ]

AMQ-6875 - Use the correct destination for Virtual destination consumers
when using Virtual Topics

(cherry picked from commit 56baba96c657d4e44b88955a964d6c92ff39b822)


> Virtual destination consumers can create invalid demand for Virtual Topics
> --
>
> Key: AMQ-6875
> URL: https://issues.apache.org/jira/browse/AMQ-6875
> Project: ActiveMQ
>  Issue Type: Bug
>  Components: Broker, networkbridge
>Affects Versions: 5.15.2
>Reporter: Christopher L. Shannon
>Assignee: Christopher L. Shannon
> Fix For: 5.16.0, 5.15.3
>
>
> When testing out Virtual topics over a network bridge that has the virtual 
> destination consumers feature enabled I noticed that the consumer advisories 
> were wrong.  The destinations sent as part of the consumer advisories to 
> create demand over the bridge are using the name of the Virtual Topic.  
> This is causing extra demand to flow across the network bridge in some cases 
> because by default the VirtualTopic name is "VirtualTopic.>" .  So once one 
> Virtual Topic is created on a remote broker then any messages sent to 
> "VirtualTopic.>" on the local broker will be forwarded over to the other 
> broker even if there is no VirtualTopic matching.
> The solution is to make sure to use the actual topic that the VirtualTopic is 
> subscribed to as part of the advisory messags.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (AMQ-6875) Virtual destination consumers can create invalid demand for Virtual Topics

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMQ-6875?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16291590#comment-16291590
 ] 

ASF subversion and git services commented on AMQ-6875:
--

Commit 56baba96c657d4e44b88955a964d6c92ff39b822 in activemq's branch 
refs/heads/master from [~cshannon]
[ https://git-wip-us.apache.org/repos/asf?p=activemq.git;h=56baba9 ]

AMQ-6875 - Use the correct destination for Virtual destination consumers
when using Virtual Topics


> Virtual destination consumers can create invalid demand for Virtual Topics
> --
>
> Key: AMQ-6875
> URL: https://issues.apache.org/jira/browse/AMQ-6875
> Project: ActiveMQ
>  Issue Type: Bug
>  Components: Broker, networkbridge
>Affects Versions: 5.15.2
>Reporter: Christopher L. Shannon
>Assignee: Christopher L. Shannon
> Fix For: 5.16.0, 5.15.3
>
>
> When testing out Virtual topics over a network bridge that has the virtual 
> destination consumers feature enabled I noticed that the consumer advisories 
> were wrong.  The destinations sent as part of the consumer advisories to 
> create demand over the bridge are using the name of the Virtual Topic.  
> This is causing extra demand to flow across the network bridge in some cases 
> because by default the VirtualTopic name is "VirtualTopic.>" .  So once one 
> Virtual Topic is created on a remote broker then any messages sent to 
> "VirtualTopic.>" on the local broker will be forwarded over to the other 
> broker even if there is no VirtualTopic matching.
> The solution is to make sure to use the actual topic that the VirtualTopic is 
> subscribed to as part of the advisory messags.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (AMQ-6875) Virtual destination consumers can create invalid demand for Virtual Topics

[Christopher L. Shannon (JIRA)]

Christopher L. Shannon created AMQ-6875:
---

 Summary: Virtual destination consumers can create invalid demand 
for Virtual Topics
 Key: AMQ-6875
 URL: https://issues.apache.org/jira/browse/AMQ-6875
 Project: ActiveMQ
  Issue Type: Bug
  Components: Broker, networkbridge
Affects Versions: 5.15.2
Reporter: Christopher L. Shannon
Assignee: Christopher L. Shannon
 Fix For: 5.16.0, 5.15.3


When testing out Virtual topics over a network bridge that has the virtual 
destination consumers feature enabled I noticed that the consumer advisories 
were wrong.  The destinations sent as part of the consumer advisories to create 
demand over the bridge are using the name of the Virtual Topic.  

This is causing extra demand to flow across the network bridge in some cases 
because by default the VirtualTopic name is "VirtualTopic.>" .  So once one 
Virtual Topic is created on a remote broker then any messages sent to 
"VirtualTopic.>" on the local broker will be forwarded over to the other broker 
even if there is no VirtualTopic matching.

The solution is to make sure to use the actual topic that the VirtualTopic is 
subscribed to as part of the advisory messags.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (ARTEMIS-1562) Refactor example documentation

[Justin Bertram (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ARTEMIS-1562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Justin Bertram updated ARTEMIS-1562:

Affects Version/s: 2.4.0

> Refactor example documentation
> --
>
> Key: ARTEMIS-1562
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1562
> Project: ActiveMQ Artemis
>  Issue Type: Improvement
>Affects Versions: 2.4.0
>Reporter: Justin Bertram
>Assignee: Justin Bertram
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (ARTEMIS-1562) Refactor example documentation

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/ARTEMIS-1562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16291464#comment-16291464
 ] 

ASF GitHub Bot commented on ARTEMIS-1562:
-

GitHub user jbertram opened a pull request:

https://github.com/apache/activemq-artemis/pull/1716

ARTEMIS-1562 Refactor example documentation

This commit contains these changes:
* Change example documentation to use markdown
* Generate HTML doc based on markdown during release
* Fix XML formatting in some examples
* Repair out-of-date documentation

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/jbertram/activemq-artemis ARTEMIS-1562

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/activemq-artemis/pull/1716.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1716


commit 7621ace7265b914822dc507a04fd4daf30928e1a
Author: Justin Bertram 
Date:   2017-10-24T19:20:37Z

ARTEMIS-1562 Refactor example documentation

This commit contains these changes:
* Change example documentation to use markdown
* Generate HTML doc based on markdown during release
* Fix XML formatting in some examples
* Repair out-of-date documentation




> Refactor example documentation
> --
>
> Key: ARTEMIS-1562
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1562
> Project: ActiveMQ Artemis
>  Issue Type: Improvement
>Reporter: Justin Bertram
>Assignee: Justin Bertram
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (ARTEMIS-1562) Refactor example documentation

[Justin Bertram (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ARTEMIS-1562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Justin Bertram updated ARTEMIS-1562:

Summary: Refactor example documentation  (was: Refactor examples to use 
markdown)

> Refactor example documentation
> --
>
> Key: ARTEMIS-1562
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1562
> Project: ActiveMQ Artemis
>  Issue Type: Improvement
>Reporter: Justin Bertram
>Assignee: Justin Bertram
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (ARTEMIS-1562) Refactor examples to use markdown

[Justin Bertram (JIRA)]

Justin Bertram created ARTEMIS-1562:
---

 Summary: Refactor examples to use markdown
 Key: ARTEMIS-1562
 URL: https://issues.apache.org/jira/browse/ARTEMIS-1562
 Project: ActiveMQ Artemis
  Issue Type: Improvement
Reporter: Justin Bertram
Assignee: Justin Bertram






--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (ARTEMIS-1548) Support CRL

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/ARTEMIS-1548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16291353#comment-16291353
 ] 

ASF GitHub Bot commented on ARTEMIS-1548:
-

Github user Skiler closed the pull request at:

https://github.com/apache/activemq-artemis/pull/1708


> Support CRL
> ---
>
> Key: ARTEMIS-1548
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1548
> Project: ActiveMQ Artemis
>  Issue Type: New Feature
>Reporter: Justin Bertram
>Assignee: Justin Bertram
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (ARTEMIS-1548) Support CRL

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/ARTEMIS-1548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16291352#comment-16291352
 ] 

ASF GitHub Bot commented on ARTEMIS-1548:
-

Github user Skiler commented on the issue:

https://github.com/apache/activemq-artemis/pull/1708
  
Fixed by https://github.com/apache/activemq-artemis/pull/1715


> Support CRL
> ---
>
> Key: ARTEMIS-1548
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1548
> Project: ActiveMQ Artemis
>  Issue Type: New Feature
>Reporter: Justin Bertram
>Assignee: Justin Bertram
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (ARTEMIS-1548) Support CRL

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/ARTEMIS-1548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16291350#comment-16291350
 ] 

ASF GitHub Bot commented on ARTEMIS-1548:
-

GitHub user Skiler opened a pull request:

https://github.com/apache/activemq-artemis/pull/1715

ARTEMIS-1548 Support CRL



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/Skiler/activemq-artemis mqtt_crl

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/activemq-artemis/pull/1715.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1715


commit 1a429504df9448666fda3b43bb7a24e0346df80a
Author: raul.valdoleiros 
Date:   2017-12-05T15:57:13Z

ARTEMIS-1548 Support CRL




> Support CRL
> ---
>
> Key: ARTEMIS-1548
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1548
> Project: ActiveMQ Artemis
>  Issue Type: New Feature
>Reporter: Justin Bertram
>Assignee: Justin Bertram
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (ARTEMIS-1504) AMQP: Update Qpid JMS to latest 0.28.0 release and Proton-j to 0.24.0 to match

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/ARTEMIS-1504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16291232#comment-16291232
 ] 

ASF GitHub Bot commented on ARTEMIS-1504:
-

GitHub user tabish121 opened a pull request:

https://github.com/apache/activemq-artemis/pull/1714

ARTEMIS-1504 Update Qpid JMS to 0.28.0 and proton-j to 0.24.0

Updates to latest Qpid JMS and the latest Proton-J release

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/tabish121/activemq-artemis ARTEMIS-1504

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/activemq-artemis/pull/1714.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1714


commit d040a653e05f124449a487d173064650664e6577
Author: Timothy Bish 
Date:   2017-12-14T17:36:24Z

ARTEMIS-1504 Update Qpid JMS to 0.28.0 and proton-j to 0.24.0

Updates to latest Qpid JMS and the latest Proton-J release




> AMQP: Update Qpid JMS to latest 0.28.0 release and Proton-j to 0.24.0 to match
> --
>
> Key: ARTEMIS-1504
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1504
> Project: ActiveMQ Artemis
>  Issue Type: Task
>  Components: AMQP
>Affects Versions: 2.4.0
>Reporter: Timothy Bish
>Assignee: Timothy Bish
>Priority: Minor
> Fix For: 2.5.0
>
>
> Update to latest Qpid-JMS release and match its Proton-J dependency. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (ARTEMIS-1504) AMQP: Update Qpid JMS to latest 0.28.0 release and Proton-j to 0.24.0 to match

[Timothy Bish (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ARTEMIS-1504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Timothy Bish updated ARTEMIS-1504:
--
Summary: AMQP: Update Qpid JMS to latest 0.28.0 release and Proton-j to 
0.24.0 to match  (was: AMQP: Update Qpid JMS to latest 0.27.0 release and 
Proton-j to 0.23.0 to match)

> AMQP: Update Qpid JMS to latest 0.28.0 release and Proton-j to 0.24.0 to match
> --
>
> Key: ARTEMIS-1504
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1504
> Project: ActiveMQ Artemis
>  Issue Type: Task
>  Components: AMQP
>Affects Versions: 2.4.0
>Reporter: Timothy Bish
>Assignee: Timothy Bish
>Priority: Minor
> Fix For: 2.5.0
>
>
> Update to latest Qpid-JMS release and match its Proton-J dependency. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Resolved] (AMQ-6874) AMQP: Update Qpid JMS to latest 0.28.0 release and Proton-j to 0.24.0 to match

[Timothy Bish (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMQ-6874?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Timothy Bish resolved AMQ-6874.
---
   Resolution: Fixed
 Assignee: Timothy Bish
Fix Version/s: 5.15.3
   5.16.0

> AMQP: Update Qpid JMS to latest 0.28.0 release and Proton-j to 0.24.0 to match
> --
>
> Key: AMQ-6874
> URL: https://issues.apache.org/jira/browse/AMQ-6874
> Project: ActiveMQ
>  Issue Type: Task
>Reporter: Timothy Bish
>Assignee: Timothy Bish
> Fix For: 5.16.0, 5.15.3
>
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Reopened] (ARTEMIS-1504) AMQP: Update Qpid JMS to latest 0.27.0 release and Proton-j to 0.23.0 to match

[Timothy Bish (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ARTEMIS-1504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Timothy Bish reopened ARTEMIS-1504:
---

New versions released

> AMQP: Update Qpid JMS to latest 0.27.0 release and Proton-j to 0.23.0 to match
> --
>
> Key: ARTEMIS-1504
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1504
> Project: ActiveMQ Artemis
>  Issue Type: Task
>  Components: AMQP
>Affects Versions: 2.4.0
>Reporter: Timothy Bish
>Assignee: Timothy Bish
>Priority: Minor
> Fix For: 2.5.0
>
>
> Update to latest Qpid-JMS release and match its Proton-J dependency. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (AMQ-6874) AMQP: Update Qpid JMS to latest 0.28.0 release and Proton-j to 0.24.0 to match

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMQ-6874?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16291223#comment-16291223
 ] 

ASF subversion and git services commented on AMQ-6874:
--

Commit c5d8a98106b93cc48e6ee9d93599c06e1294e1fe in activemq's branch 
refs/heads/activemq-5.15.x from [~tabish121]
[ https://git-wip-us.apache.org/repos/asf?p=activemq.git;h=c5d8a98 ]

AMQ-6874 Update Qpid JMS to 0.28.0 and proton-j to 0.24.0

This updates the AMQP libs Qpid JMS and Proton-J, also updates netty to
4.1.18.Final to match the version used for Qpid JMS
(cherry picked from commit d3e439378405afb699fcbfc63d9342fbb6ad77ce)


> AMQP: Update Qpid JMS to latest 0.28.0 release and Proton-j to 0.24.0 to match
> --
>
> Key: AMQ-6874
> URL: https://issues.apache.org/jira/browse/AMQ-6874
> Project: ActiveMQ
>  Issue Type: Task
>Reporter: Timothy Bish
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (AMQ-6874) AMQP: Update Qpid JMS to latest 0.28.0 release and Proton-j to 0.24.0 to match

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMQ-6874?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16291220#comment-16291220
 ] 

ASF subversion and git services commented on AMQ-6874:
--

Commit d3e439378405afb699fcbfc63d9342fbb6ad77ce in activemq's branch 
refs/heads/master from [~tabish121]
[ https://git-wip-us.apache.org/repos/asf?p=activemq.git;h=d3e4393 ]

AMQ-6874 Update Qpid JMS to 0.28.0 and proton-j to 0.24.0

This updates the AMQP libs Qpid JMS and Proton-J, also updates netty to
4.1.18.Final to match the version used for Qpid JMS

> AMQP: Update Qpid JMS to latest 0.28.0 release and Proton-j to 0.24.0 to match
> --
>
> Key: AMQ-6874
> URL: https://issues.apache.org/jira/browse/AMQ-6874
> Project: ActiveMQ
>  Issue Type: Task
>Reporter: Timothy Bish
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (AMQ-6874) AMQP: Update Qpid JMS to latest 0.28.0 release and Proton-j to 0.24.0 to match

[Timothy Bish (JIRA)]

Timothy Bish created AMQ-6874:
-

 Summary: AMQP: Update Qpid JMS to latest 0.28.0 release and 
Proton-j to 0.24.0 to match
 Key: AMQ-6874
 URL: https://issues.apache.org/jira/browse/AMQ-6874
 Project: ActiveMQ
  Issue Type: Task
Reporter: Timothy Bish






--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (ARTEMIS-1546) Messages sent with snapshot won't be read from 1.x consumers

[clebert suconic (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ARTEMIS-1546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

clebert suconic updated ARTEMIS-1546:
-
Description: 
Sending JMS message with core master, receiving with 1.4 will cause issues.

Any other combination is fine!


The issue is that 1.x had an extra integer at the end of the body with the size 
of the body.

Basically there is on at the beginning  and one at the end of the body

{size} ... bytes... {size + Initial Head}


that integer was lost during the AMQP / Core refactoring... 

The fix here is to recast the message with the integer.

  was:
Sending JMS message with core master, receiving with 1.4 will cause issues.

Any other combination is fine!


> Messages sent with snapshot won't be read from 1.x consumers
> 
>
> Key: ARTEMIS-1546
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1546
> Project: ActiveMQ Artemis
>  Issue Type: Bug
>Reporter: clebert suconic
>Assignee: clebert suconic
> Fix For: 2.5.0
>
>
> Sending JMS message with core master, receiving with 1.4 will cause issues.
> Any other combination is fine!
> The issue is that 1.x had an extra integer at the end of the body with the 
> size of the body.
> Basically there is on at the beginning  and one at the end of the body
> {size} ... bytes... {size + Initial Head}
> that integer was lost during the AMQP / Core refactoring... 
> The fix here is to recast the message with the integer.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (ARTEMIS-1546) Messages sent with snapshot won't be read from 1.x consumers

[clebert suconic (JIRA)]

[ 
https://issues.apache.org/jira/browse/ARTEMIS-1546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16291134#comment-16291134
 ] 

clebert suconic commented on ARTEMIS-1546:
--

ARTEMIS-1561 was found as part of this one

> Messages sent with snapshot won't be read from 1.x consumers
> 
>
> Key: ARTEMIS-1546
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1546
> Project: ActiveMQ Artemis
>  Issue Type: Bug
>Reporter: clebert suconic
>Assignee: clebert suconic
> Fix For: 2.5.0
>
>
> Sending JMS message with core master, receiving with 1.4 will cause issues.
> Any other combination is fine!



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (ARTEMIS-1546) Messages sent with snapshot won't be read from 1.x consumers

[clebert suconic (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ARTEMIS-1546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

clebert suconic updated ARTEMIS-1546:
-
Summary: Messages sent with snapshot won't be read from 1.x consumers  
(was: Compatibility issues between Artemis 1.4 and 2.0)

> Messages sent with snapshot won't be read from 1.x consumers
> 
>
> Key: ARTEMIS-1546
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1546
> Project: ActiveMQ Artemis
>  Issue Type: Bug
>Reporter: clebert suconic
>Assignee: clebert suconic
> Fix For: 2.5.0
>
>
> Sending JMS message with core master, receiving with 1.4 will cause issues.
> Any other combination is fine!



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (ARTEMIS-1561) Auto create won't work with 1.x clients

[clebert suconic (JIRA)]

[ 
https://issues.apache.org/jira/browse/ARTEMIS-1561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16291123#comment-16291123
 ] 

clebert suconic commented on ARTEMIS-1561:
--

I'm adding Compatibility tests...

uncomment a line on ArtemisServerProcess to see failures.

the test I have there is validating another issue fixed... this goes a bit 
beyond.

> Auto create won't work with 1.x clients
> ---
>
> Key: ARTEMIS-1561
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1561
> Project: ActiveMQ Artemis
>  Issue Type: Bug
>Affects Versions: 2.0.0, 2.1.0, 2.2.0, 2.3.0, 2.4.0
>Reporter: clebert suconic
>Assignee: Martyn Taylor
> Fix For: 2.5.0
>
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (ARTEMIS-1561) Auto create won't work with 1.x clients

[clebert suconic (JIRA)]

clebert suconic created ARTEMIS-1561:


 Summary: Auto create won't work with 1.x clients
 Key: ARTEMIS-1561
 URL: https://issues.apache.org/jira/browse/ARTEMIS-1561
 Project: ActiveMQ Artemis
  Issue Type: Bug
Affects Versions: 2.4.0, 2.3.0, 2.2.0, 2.1.0, 2.0.0
Reporter: clebert suconic
Assignee: Martyn Taylor
 Fix For: 2.5.0






--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (ARTEMIS-1559) Repeated retries of unencrypted traffic to SSL-enabled boker causes OOM exception

[Tommy Lillehagen (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ARTEMIS-1559?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Tommy Lillehagen updated ARTEMIS-1559:
--
Description: 
Repro steps:

 * We have a broker (A) set up with SSL enabled (using Artemis v2.4 / v2.3)
 * A client (B) set up to use plain (non-TLS) communication (same version of 
Artemis)
 * Trying to establish a connection between (B) and (A) triggers multiple 
retries
 * Each message gets, from what I can tell, rejected quickly by (A), but each 
iteration leaks heap memory
 * Due to the number of retries in a short amount a time (~1000s from what I 
can tell) causes the above to grow the heap by 470M or so within less than 10 
seconds (the set timeout)
 * This consequently results in an out of memory exception

The above behaviour is observed in both version 2.3 and 2.4.

We've tested older versions (2.1 and 2.2), and neither of those manifest the 
same problem.

I've run some profiling on (A), and {{NettyAcceptor.initChannel}} 
({{getSslHandler()}}) seems to be a critical point (will include screenshots).

That being said, most of the accumulated heap memory seems to be claimable and 
is mostly collected during the next GC cycle in the tests that I've run.

Source: https://github.com/corda/corda/pull/2252

  was:
Repro steps:

 * We have a broker (A) set up with SSL enabled (using Artemis v2.4 / v2.3)
 * A client (B) set up to use plain (non-TLS) communication (same version of 
Artemis)
 * Trying to establish a connection between (B) and (A) triggers multiple 
retries
 * Each message gets, from what I can tell, rejected quickly by (A), but each 
iteration leaks heap memory
 * Due to the number of retries in a short amount a time (~1000s from what I 
can tell) causes the above to grow the heap by 470M or so within less than 10 
seconds (the set timeout)
 * This consequently results in an out of memory exception

The above behaviour is observed in both version 2.3 and 2.4.

We've tested older versions (2.1 and 2.2), and neither of those manifest the 
same problem.

I've run some profiling on (A), and {{NettyAcceptor.initChannel}} 
({{getSslHandler()}}) seems to be a critical point (will include screenshots).

That being said, most of the accumulated heap memory seems to be claimable and 
is mostly collected during the next GC cycle in the tests that I've run.


> Repeated retries of unencrypted traffic to SSL-enabled boker causes OOM 
> exception
> -
>
> Key: ARTEMIS-1559
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1559
> Project: ActiveMQ Artemis
>  Issue Type: Bug
>Affects Versions: 2.3.0, 2.4.0
>Reporter: Tommy Lillehagen
>  Labels: memory-leak
> Attachments: mem-leak-source.png, mem-leak.png
>
>
> Repro steps:
>  * We have a broker (A) set up with SSL enabled (using Artemis v2.4 / v2.3)
>  * A client (B) set up to use plain (non-TLS) communication (same version of 
> Artemis)
>  * Trying to establish a connection between (B) and (A) triggers multiple 
> retries
>  * Each message gets, from what I can tell, rejected quickly by (A), but each 
> iteration leaks heap memory
>  * Due to the number of retries in a short amount a time (~1000s from what I 
> can tell) causes the above to grow the heap by 470M or so within less than 10 
> seconds (the set timeout)
>  * This consequently results in an out of memory exception
> The above behaviour is observed in both version 2.3 and 2.4.
> We've tested older versions (2.1 and 2.2), and neither of those manifest the 
> same problem.
> I've run some profiling on (A), and {{NettyAcceptor.initChannel}} 
> ({{getSslHandler()}}) seems to be a critical point (will include screenshots).
> That being said, most of the accumulated heap memory seems to be claimable 
> and is mostly collected during the next GC cycle in the tests that I've run.
> Source: https://github.com/corda/corda/pull/2252



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (ARTEMIS-1559) Repeated retries of unencrypted traffic to SSL-enabled boker causes OOM exception

[Tommy Lillehagen (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ARTEMIS-1559?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Tommy Lillehagen updated ARTEMIS-1559:
--
Attachment: mem-leak.png
mem-leak-source.png

> Repeated retries of unencrypted traffic to SSL-enabled boker causes OOM 
> exception
> -
>
> Key: ARTEMIS-1559
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1559
> Project: ActiveMQ Artemis
>  Issue Type: Bug
>Affects Versions: 2.3.0, 2.4.0
>Reporter: Tommy Lillehagen
>  Labels: memory-leak
> Attachments: mem-leak-source.png, mem-leak.png
>
>
> Repro steps:
>  * We have a broker (A) set up with SSL enabled (using Artemis v2.4 / v2.3)
>  * A client (B) set up to use plain (non-TLS) communication (same version of 
> Artemis)
>  * Trying to establish a connection between (B) and (A) triggers multiple 
> retries
>  * Each message gets, from what I can tell, rejected quickly by (A), but each 
> iteration leaks heap memory
>  * Due to the number of retries in a short amount a time (~1000s from what I 
> can tell) causes the above to grow the heap by 470M or so within less than 10 
> seconds (the set timeout)
>  * This consequently results in an out of memory exception
> The above behaviour is observed in both version 2.3 and 2.4.
> We've tested older versions (2.1 and 2.2), and neither of those manifest the 
> same problem.
> I've run some profiling on (A), and {{NettyAcceptor.initChannel}} 
> ({{getSslHandler()}}) seems to be a critical point (will include screenshots).
> That being said, most of the accumulated heap memory seems to be claimable 
> and is mostly collected during the next GC cycle in the tests that I've run.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (ARTEMIS-1560) Destroy message instead of sending it to DLQ

[Tom Ross (JIRA)]

Tom Ross created ARTEMIS-1560:
-

 Summary: Destroy message instead of sending it to DLQ
 Key: ARTEMIS-1560
 URL: https://issues.apache.org/jira/browse/ARTEMIS-1560
 Project: ActiveMQ Artemis
  Issue Type: New Feature
  Components: Broker
Affects Versions: 2.3.0
 Environment: Artemis broker
Reporter: Tom Ross


There is a requirement to add an enhancement to the way messages are sent to 
DLQ. 
It should be possible to set a property on a message that when rejected by 
client the broker would rollback an existing transaction, ACK the message and 
destroy it instead of sending it to DLQ.




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (ARTEMIS-1559) Repeated retries of unencrypted traffic to SSL-enabled boker causes OOM exception

[Tommy Lillehagen (JIRA)]

Tommy Lillehagen created ARTEMIS-1559:
-

 Summary: Repeated retries of unencrypted traffic to SSL-enabled 
boker causes OOM exception
 Key: ARTEMIS-1559
 URL: https://issues.apache.org/jira/browse/ARTEMIS-1559
 Project: ActiveMQ Artemis
  Issue Type: Bug
Affects Versions: 2.4.0, 2.3.0
Reporter: Tommy Lillehagen


Repro steps:

 * We have a broker (A) set up with SSL enabled (using Artemis v2.4 / v2.3)
 * A client (B) set up to use plain (non-TLS) communication (same version of 
Artemis)
 * Trying to establish a connection between (B) and (A) triggers multiple 
retries
 * Each message gets, from what I can tell, rejected quickly by (A), but each 
iteration leaks heap memory
 * Due to the number of retries in a short amount a time (~1000s from what I 
can tell) causes the above to grow the heap by 470M or so within less than 10 
seconds (the set timeout)
 * This consequently results in an out of memory exception

The above behaviour is observed in both version 2.3 and 2.4.

We've tested older versions (2.1 and 2.2), and neither of those manifest the 
same problem.

I've run some profiling on (A), and {{NettyAcceptor.initChannel}} 
({{getSslHandler()}}) seems to be a critical point (will include screenshots).

That being said, most of the accumulated heap memory seems to be claimable and 
is mostly collected during the next GC cycle in the tests that I've run.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (ARTEMIS-1516) Ensure JNDI using Tomcat Resources works as like ActiveMQ 5

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/ARTEMIS-1516?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16290844#comment-16290844
 ] 

ASF GitHub Bot commented on ARTEMIS-1516:
-

Github user clebertsuconic commented on the issue:

https://github.com/apache/activemq-artemis/pull/1659
  
just updating this that I haven't forgot about this... I'm working on a 
testsuite for compatibility checks and I will extend it to make sure this will 
work.


> Ensure JNDI using Tomcat Resources works as like ActiveMQ 5
> ---
>
> Key: ARTEMIS-1516
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1516
> Project: ActiveMQ Artemis
>  Issue Type: Bug
>Reporter: Michael Andre Pearce
>Assignee: Michael Andre Pearce
>
> Ensure JNDI using Tomcat Resources works as like ActiveMQ 5. JNDI 
> serialisation needs to use StringRefAddr to support this.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (ARTEMIS-1310) Provide GSSAPI (kerberos) SASL mechanism for AMQP

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/ARTEMIS-1310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16290717#comment-16290717
 ] 

ASF GitHub Bot commented on ARTEMIS-1310:
-

GitHub user gtully opened a pull request:

https://github.com/apache/activemq-artemis/pull/1711

[ARTEMIS-1310] [ARTEMIS-1264] - remove some dead code - krb5 login mo…

…dule and jaas callback handler now have the smarts to query netty

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/gtully/activemq-artemis JBEAP-13868

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/activemq-artemis/pull/1711.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1711


commit 2e1c909a69f15953277fbe696b2e278f704c2e72
Author: gtully 
Date:   2017-12-14T11:07:15Z

[ARTEMIS-1310] [ARTEMIS-1264] - remove some dead code - krb5 login module 
and jaas callback handler now have the smarts to query netty




> Provide GSSAPI (kerberos) SASL mechanism for AMQP
> -
>
> Key: ARTEMIS-1310
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1310
> Project: ActiveMQ Artemis
>  Issue Type: Bug
>  Components: AMQP
>Affects Versions: 2.2.0
>Reporter: Gary Tully
>Assignee: Gary Tully
> Fix For: 2.3.0
>
>
> implement GSSAPI sasl mechanism for AMQP transport allowing kerberos single 
> sign on (authentication) and subsequent authorisation
> Doco: 
> https://github.com/apache/activemq-artemis/blob/master/docs/user-manual/en/security.md#kerberos-authentication



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)