[jira] [Updated] (AMQ-5381) ActiveMQBytesMessage mishandles restoration of old message contents

[ https://issues.apache.org/jira/browse/AMQ-5381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hadrian Zbarcea updated AMQ-5381: - Fix Version/s: 5.10.1 > ActiveMQBytesMessage mishandles restoration of old message contents > --

[jira] [Closed] (ACTIVEMQ6-61) SelectorParser package conflict with openwire tests

[ https://issues.apache.org/jira/browse/ACTIVEMQ6-61?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Howard Gao closed ACTIVEMQ6-61. --- Resolution: Fixed > SelectorParser package conflict with openwire tests > --

[jira] [Updated] (AMQ-5337) Bug in ConcurrentLinkedQueue leads to excessive CPU-consumption by ActiveMQ process

[ https://issues.apache.org/jira/browse/AMQ-5337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hadrian Zbarcea updated AMQ-5337: - Fix Version/s: 5.10.1 > Bug in ConcurrentLinkedQueue leads to excessive CPU-consumption by ActiveMQ

[jira] [Updated] (AMQ-5323) ActiveMQ Message getProperty and setProperty inconsistent behaviour

[ https://issues.apache.org/jira/browse/AMQ-5323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hadrian Zbarcea updated AMQ-5323: - Fix Version/s: 5.10.1 > ActiveMQ Message getProperty and setProperty inconsistent behaviour > --

[jira] [Updated] (AMQ-5295) HTTPS Network Connector doesn't work with Mutual authentication- HTTPSClientTransport uses wrong SSLSocketFactory

[ https://issues.apache.org/jira/browse/AMQ-5295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hadrian Zbarcea updated AMQ-5295: - Fix Version/s: 5.10.1 > HTTPS Network Connector doesn't work with Mutual authentication- > HTTPSCli

[jira] [Updated] (AMQ-5315) NullPointerException in DemandForwardingBridgeSupport.collectBrokerInfos

[ https://issues.apache.org/jira/browse/AMQ-5315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hadrian Zbarcea updated AMQ-5315: - Fix Version/s: 5.10.1 > NullPointerException in DemandForwardingBridgeSupport.collectBrokerInfos > -

[jira] [Updated] (AMQ-5220) Advisory messages are still empty when received with a Stomp subscription

[ https://issues.apache.org/jira/browse/AMQ-5220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hadrian Zbarcea updated AMQ-5220: - Fix Version/s: 5.10.1 > Advisory messages are still empty when received with a Stomp subscription >

Build failed in Jenkins: ActiveMQ-Trunk-Deploy #1164

See -- [...truncated 494 lines...] Compression is 0.0% Took 0.11 sec [JENKINS] Archiving to org.apache

Build failed in Jenkins: ActiveMQ-Trunk-Deploy » ActiveMQ #1164

See -- maven3-agent.jar already up to date maven3-interceptor.jar already up to date maven3-interceptor-commons.jar already up to date <===[JENKINS REMOTING CAPA

[jira] [Updated] (AMQ-5304) groupClass not applied to TempDestinationAuthorizationEntry

[ https://issues.apache.org/jira/browse/AMQ-5304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hadrian Zbarcea updated AMQ-5304: - Fix Version/s: 5.10.1 > groupClass not applied to TempDestinationAuthorizationEntry > --

[jira] [Updated] (AMQ-5289) Track forwards across a network in destination statistics

[ https://issues.apache.org/jira/browse/AMQ-5289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hadrian Zbarcea updated AMQ-5289: - Fix Version/s: 5.10.1 > Track forwards across a network in destination statistics >

[jira] [Updated] (AMQ-5198) MessageConsumer and Producer are not thread safe

[ https://issues.apache.org/jira/browse/AMQ-5198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hadrian Zbarcea updated AMQ-5198: - Fix Version/s: 5.10.1 > MessageConsumer and Producer are not thread safe > -

[jira] [Updated] (AMQ-5279) failover redelivery to alternative consumers with pending transaction causes rollback *and* dlq processing

[ https://issues.apache.org/jira/browse/AMQ-5279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hadrian Zbarcea updated AMQ-5279: - Fix Version/s: 5.10.1 > failover redelivery to alternative consumers with pending transaction cause

[jira] [Issue Comment Deleted] (AMQ-4237) JMX ObjectNames do not follow JMX Best practices to use a Hierarchical format

[ https://issues.apache.org/jira/browse/AMQ-4237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish updated AMQ-4237: -- Comment: was deleted (was: ddd) > JMX ObjectNames do not follow JMX Best practices to use a Hierarchical

Re: JMS Destination handling for AMQP 1.0

On 17 December 2014 at 18:37, Robbie Gemmell wrote: > > On 17 December 2014 at 16:46, Rob Godfrey wrote: > > On 17 December 2014 at 17:25, Robbie Gemmell > > wrote: > >> > >> On 17 December 2014 at 15:00, Rob Godfrey > wrote: > >> > On 17 December 2014 at 15:45, Robbie Gemmell < > robbie.gemm..

[jira] [Commented] (AMQ-4237) JMX ObjectNames do not follow JMX Best practices to use a Hierarchical format

[ https://issues.apache.org/jira/browse/AMQ-4237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14250209#comment-14250209 ] tangxiangqi commented on AMQ-4237: -- ddd > JMX ObjectNames do not follow JMX Best practices

Re: JMS Destination handling for AMQP 1.0

On 17 December 2014 at 16:46, Rob Godfrey wrote: > On 17 December 2014 at 17:25, Robbie Gemmell > wrote: >> >> On 17 December 2014 at 15:00, Rob Godfrey wrote: >> > On 17 December 2014 at 15:45, Robbie Gemmell >> > wrote: >> >> >> >> On 17 December 2014 at 13:43, Rob Godfrey >> wrote: >> >> >

[activemq6] XML or Not on Configurations

Since we are not moving on ActiveMQ6 we could things differently. I was wondering for configuration.. is there anything better these days for storing config? I heard today for two options... YAML, and JSON. So we would have Three options so far: YAML - it seems nice.. but I'm not sure about li

Re: JMS Destination handling for AMQP 1.0

On 17 December 2014 at 17:25, Robbie Gemmell wrote: > > On 17 December 2014 at 15:00, Rob Godfrey wrote: > > On 17 December 2014 at 15:45, Robbie Gemmell > > wrote: > >> > >> On 17 December 2014 at 13:43, Rob Godfrey > wrote: > >> > On 17 December 2014 at 13:37, Robbie Gemmell < > robbie.gemm..

Re: JMS Destination handling for AMQP 1.0

On 17 December 2014 at 15:00, Rob Godfrey wrote: > On 17 December 2014 at 15:45, Robbie Gemmell > wrote: >> >> On 17 December 2014 at 13:43, Rob Godfrey wrote: >> > On 17 December 2014 at 13:37, Robbie Gemmell >> > wrote: >> >> >> >> Hi everyone (please use reply-all to keep both lists on the t

Re: JMS Destination handling for AMQP 1.0

On 17 December 2014 at 15:45, Robbie Gemmell wrote: > > On 17 December 2014 at 13:43, Rob Godfrey wrote: > > On 17 December 2014 at 13:37, Robbie Gemmell > > wrote: > >> > >> Hi everyone (please use reply-all to keep both lists on the trail), > >> > >> I would like to have a discussion around JM

[jira] [Updated] (AMQ-5491) Standalone Web console Session timeout with user/password input

[ https://issues.apache.org/jira/browse/AMQ-5491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hadrian Zbarcea updated AMQ-5491: - Fix Version/s: 5.11.0 > Standalone Web console Session timeout with user/password input > --

[jira] [Assigned] (AMQ-5491) Standalone Web console Session timeout with user/password input

[ https://issues.apache.org/jira/browse/AMQ-5491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hadrian Zbarcea reassigned AMQ-5491: Assignee: Hadrian Zbarcea > Standalone Web console Session timeout with user/password input >

Re: JMS Destination handling for AMQP 1.0

On 17 December 2014 at 13:43, Rob Godfrey wrote: > On 17 December 2014 at 13:37, Robbie Gemmell > wrote: >> >> Hi everyone (please use reply-all to keep both lists on the trail), >> >> I would like to have a discussion around JMS destination handling in >> the JMS Mapping for AMQP 1.0, in particu

[jira] [Updated] (AMQ-5491) Standalone Web console Session timeout with user/password input

[ https://issues.apache.org/jira/browse/AMQ-5491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dumitru HUSLEAG updated AMQ-5491: - Description: We use the web console as a standalone application deployed on a Jetty instance. And we

[jira] [Updated] (AMQ-5491) Standalone Web console Session timeout with user/password input

[ https://issues.apache.org/jira/browse/AMQ-5491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dumitru HUSLEAG updated AMQ-5491: - Description: We use the web console as a standalone application deployed on a Jetty instance. And we

[jira] [Updated] (AMQ-5491) Standalone Web console Session timeout with user/password input

[ https://issues.apache.org/jira/browse/AMQ-5491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dumitru HUSLEAG updated AMQ-5491: - Description: We use the web console as a standalone deployed on a Jetty instance. And we need to sec

[jira] [Comment Edited] (AMQ-1730) Bad use of Jms field JMSXDeliveryCount. Related to RedeliveryCount and message prefetch

[ https://issues.apache.org/jira/browse/AMQ-1730?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14249853#comment-14249853 ] Christian Tytgat edited comment on AMQ-1730 at 12/17/14 2:07 PM: -

[jira] [Updated] (AMQ-5491) Standalone Web console Session timeout with user/password input

[ https://issues.apache.org/jira/browse/AMQ-5491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dumitru HUSLEAG updated AMQ-5491: - Description: We use the web console as a standalone application deployed on a Jetty instance. And we

[jira] [Updated] (AMQ-5491) Standalone Web console Session timeout with user/password input

[ https://issues.apache.org/jira/browse/AMQ-5491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dumitru HUSLEAG updated AMQ-5491: - Description: We use the web console as a standalone deployed on a Jetty instance. And we need to sec

[jira] [Updated] (AMQ-5491) Standalone Web console Session timeout with user/password input

[ https://issues.apache.org/jira/browse/AMQ-5491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dumitru HUSLEAG updated AMQ-5491: - Attachment: 0001-AMQ-5491-Standalone-Web-console-Session-timeout-with.patch > Standalone Web console

[jira] [Commented] (AMQ-1730) Bad use of Jms field JMSXDeliveryCount. Related to RedeliveryCount and message prefetch

[ https://issues.apache.org/jira/browse/AMQ-1730?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14249853#comment-14249853 ] Christian Tytgat commented on AMQ-1730: --- Is this supposed to be fixed for topics as we

Re: JMS Destination handling for AMQP 1.0

On 17 December 2014 at 13:37, Robbie Gemmell wrote: > > Hi everyone (please use reply-all to keep both lists on the trail), > > I would like to have a discussion around JMS destination handling in > the JMS Mapping for AMQP 1.0, in particular around how to handle JMS > Destination names via the AM

[jira] [Updated] (AMQ-5491) Standalone Web console Session timeout with user/password input

[ https://issues.apache.org/jira/browse/AMQ-5491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dumitru HUSLEAG updated AMQ-5491: - Description: We use the web console as a standalone deployed on a Jetty instance. And we need

[jira] [Updated] (AMQ-5491) Standalone Web console Session timeout with user/password input

[ https://issues.apache.org/jira/browse/AMQ-5491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dumitru HUSLEAG updated AMQ-5491: - Description: We use the web console as a standalone deployed on a Jetty instance. And we need to s

[jira] [Closed] (AMQ-5490) broker does not write out supported version header

[ https://issues.apache.org/jira/browse/AMQ-5490?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gordon Sim closed AMQ-5490. --- Resolution: Duplicate > broker does not write out supported version header > ---

[jira] [Commented] (AMQ-5490) broker does not write out supported version header

[ https://issues.apache.org/jira/browse/AMQ-5490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14249830#comment-14249830 ] Gordon Sim commented on AMQ-5490: - Not yet, will do that > broker does not write out suppor

[jira] [Updated] (AMQ-5491) Standalone Web console Session timeout with user/password input

[ https://issues.apache.org/jira/browse/AMQ-5491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dumitru HUSLEAG updated AMQ-5491: - Fix Version/s: 5.11.0 Summary: Standalone Web console Session timeout with user/password i

[jira] [Created] (AMQ-5491) Standalone Web console Session timeout

Dumitru HUSLEAG created AMQ-5491: Summary: Standalone Web console Session timeout Key: AMQ-5491 URL: https://issues.apache.org/jira/browse/AMQ-5491 Project: ActiveMQ Issue Type: New Feature

[jira] [Commented] (AMQ-5490) broker does not write out supported version header

[ https://issues.apache.org/jira/browse/AMQ-5490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14249815#comment-14249815 ] Robbie Gemmell commented on AMQ-5490: - I notice you said affects 5.10. Have you tried wi

[jira] [Created] (AMQ-5490) broker does not write out supported version header

Gordon Sim created AMQ-5490: --- Summary: broker does not write out supported version header Key: AMQ-5490 URL: https://issues.apache.org/jira/browse/AMQ-5490 Project: ActiveMQ Issue Type: Bug

JMS Destination handling for AMQP 1.0

Hi everyone (please use reply-all to keep both lists on the trail), I would like to have a discussion around JMS destination handling in the JMS Mapping for AMQP 1.0, in particular around how to handle JMS Destination names via the AMQP "address" field of a link (producer/consumer) source/target a

[jira] [Commented] (ACTIVEMQ6-61) SelectorParser package conflict with openwire tests

[ https://issues.apache.org/jira/browse/ACTIVEMQ6-61?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14249710#comment-14249710 ] ASF GitHub Bot commented on ACTIVEMQ6-61: - Github user asfgit closed the pull re

[GitHub] activemq-6 pull request: ACTIVEMQ6-61 SelectorParser package confl...

Github user asfgit closed the pull request at: https://github.com/apache/activemq-6/pull/47 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is e