[jira] [Commented] (ARTEMIS-595) When creating JMS bridge management API should pass bridge name to JMS broker

[ https://issues.apache.org/jira/browse/ARTEMIS-595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15348997#comment-15348997 ] ASF GitHub Bot commented on ARTEMIS-595: Github user bayern39 closed the pull req

[jira] [Commented] (ARTEMIS-591) Wrong XAException return code when broker timeout is hit

[ https://issues.apache.org/jira/browse/ARTEMIS-591?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15348989#comment-15348989 ] ASF GitHub Bot commented on ARTEMIS-591: Github user bayern39 commented on the is

[jira] [Closed] (ARTEMIS-595) When creating JMS bridge management API should pass bridge name to JMS broker

[ https://issues.apache.org/jira/browse/ARTEMIS-595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Bertram closed ARTEMIS-595. -- Resolution: Fixed > When creating JMS bridge management API should pass bridge name to JMS brok

[jira] [Assigned] (ARTEMIS-569) property missing from XSD

[ https://issues.apache.org/jira/browse/ARTEMIS-569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Bertram reassigned ARTEMIS-569: -- Assignee: Justin Bertram > property missing from XSD > - > >

[jira] [Commented] (ARTEMIS-596) JMS Bridge logger message should be identified by the bridge name

[ https://issues.apache.org/jira/browse/ARTEMIS-596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15348753#comment-15348753 ] ASF GitHub Bot commented on ARTEMIS-596: GitHub user jbertram opened a pull reque

[jira] [Commented] (ARTEMIS-569) property missing from XSD

[ https://issues.apache.org/jira/browse/ARTEMIS-569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15348751#comment-15348751 ] ASF GitHub Bot commented on ARTEMIS-569: GitHub user jbertram opened a pull reque

[jira] [Commented] (ARTEMIS-596) JMS Bridge logger message should be identified by the bridge name

[ https://issues.apache.org/jira/browse/ARTEMIS-596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15348440#comment-15348440 ] ASF subversion and git services commented on ARTEMIS-596: - Commit

[jira] [Commented] (ARTEMIS-595) When creating JMS bridge management API should pass bridge name to JMS broker

[ https://issues.apache.org/jira/browse/ARTEMIS-595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15348445#comment-15348445 ] ASF GitHub Bot commented on ARTEMIS-595: Github user jbertram commented on the is

[jira] [Commented] (ARTEMIS-596) JMS Bridge logger message should be identified by the bridge name

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

[jira] [Commented] (ARTEMIS-596) JMS Bridge logger message should be identified by the bridge name

[ https://issues.apache.org/jira/browse/ARTEMIS-596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15348428#comment-15348428 ] Tom Ross commented on ARTEMIS-596: -- https://github.com/apache/activemq-artemis/pull/597

[jira] [Commented] (ARTEMIS-596) JMS Bridge logger message should be identified by the bridge name

[ https://issues.apache.org/jira/browse/ARTEMIS-596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15348425#comment-15348425 ] ASF GitHub Bot commented on ARTEMIS-596: GitHub user TomRoss opened a pull reques

[jira] [Commented] (ARTEMIS-591) Wrong XAException return code when broker timeout is hit

[ https://issues.apache.org/jira/browse/ARTEMIS-591?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15348399#comment-15348399 ] ASF GitHub Bot commented on ARTEMIS-591: Github user jbertram commented on the is

[jira] [Commented] (ARTEMIS-595) When creating JMS bridge management API should pass bridge name to JMS broker

[ https://issues.apache.org/jira/browse/ARTEMIS-595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15348392#comment-15348392 ] ASF GitHub Bot commented on ARTEMIS-595: Github user jbertram commented on the is

[jira] [Updated] (AMQ-6335) MasterSlave: Queues don't stay paused after failover.

[ https://issues.apache.org/jira/browse/AMQ-6335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish updated AMQ-6335: -- Issue Type: New Feature (was: Bug) > MasterSlave: Queues don't stay paused after failover. >

[jira] [Closed] (AMQ-6314) Improve ActiveMQ performance with no message loss configuration

[ https://issues.apache.org/jira/browse/AMQ-6314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish closed AMQ-6314. - Resolution: Invalid This is a discussion that needs to happen on the users forum, jira is where real bugs a

[jira] [Commented] (AMQ-6286) Queue order lost on repeated redelivery

[ https://issues.apache.org/jira/browse/AMQ-6286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15348271#comment-15348271 ] ASF subversion and git services commented on AMQ-6286: -- Commit e02c1a17

[jira] [Updated] (ARTEMIS-596) JMS Bridge logger message should be identified by the bridge name

[ https://issues.apache.org/jira/browse/ARTEMIS-596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Ross updated ARTEMIS-596: - Summary: JMS Bridge logger message should be identified by the bridge name (was: JMS Bridge logger messa

[jira] [Comment Edited] (ARTEMIS-595) When creating JMS bridge management API should pass bridge name to JMS broker

[ https://issues.apache.org/jira/browse/ARTEMIS-595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15348263#comment-15348263 ] Chen Maoqian edited comment on ARTEMIS-595 at 6/24/16 1:34 PM:

[jira] [Commented] (ARTEMIS-595) When creating JMS bridge management API should pass bridge name to JMS broker

[ https://issues.apache.org/jira/browse/ARTEMIS-595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15348263#comment-15348263 ] Chen Maoqian commented on ARTEMIS-595: -- i am so sorry that,can you tell me detailed?

[jira] [Created] (ARTEMIS-596) JMS Bridge logger message should be identify by the bridge name

Tom Ross created ARTEMIS-596: Summary: JMS Bridge logger message should be identify by the bridge name Key: ARTEMIS-596 URL: https://issues.apache.org/jira/browse/ARTEMIS-596 Project: ActiveMQ Artemis

[jira] [Commented] (ARTEMIS-595) When creating JMS bridge management API should pass bridge name to JMS broker

[ https://issues.apache.org/jira/browse/ARTEMIS-595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15348251#comment-15348251 ] Tom Ross commented on ARTEMIS-595: -- I think you have misunderstood the issue. The sPR is

[jira] [Commented] (AMQ-6241) Installing camel-core in Karaf prevents activemq-camel from deploying successfully

[ https://issues.apache.org/jira/browse/AMQ-6241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15348110#comment-15348110 ] Ralf Steppacher commented on AMQ-6241: -- Is there any ETA for this issue? Or is there a

[jira] [Commented] (ARTEMIS-594) support HTTPS access to hawtio

[ https://issues.apache.org/jira/browse/ARTEMIS-594?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15348011#comment-15348011 ] ASF GitHub Bot commented on ARTEMIS-594: Github user gaohoward commented on the i