[jira] [Resolved] (AMQ-5534) Generic JMS connection pool should be able to renew connections after JMSException

[ https://issues.apache.org/jira/browse/AMQ-5534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dejan Bosanac resolved AMQ-5534. Resolution: Fixed Fixed with http://git-wip-us.apache.org/repos/asf/activemq/commit/b53d8ea2

[jira] [Commented] (AMQ-5229) Queue; be able to pause/resume dispatch of message to all consumers

[ https://issues.apache.org/jira/browse/AMQ-5229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14287505#comment-14287505 ] Jean-Marc Reymond commented on AMQ-5229: This is exactly what I am missing from AMQ

[jira] [Commented] (AMQ-4727) Unable to add camel routes to activemq running in a karaf container

[ https://issues.apache.org/jira/browse/AMQ-4727?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14287369#comment-14287369 ] Gary Tully commented on AMQ-4727: - JB thanks - there are two strange things with the itests

[jira] [Commented] (AMQ-5534) Generic JMS connection pool should be able to renew connections after JMSException

[ https://issues.apache.org/jira/browse/AMQ-5534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14287324#comment-14287324 ] Dejan Bosanac commented on AMQ-5534: There's a new {{reconnectOnException}} property on

[GitHub] activemq-6 pull request: removing redundant tests

GitHub user jbertram opened a pull request: https://github.com/apache/activemq-6/pull/76 removing redundant tests You can merge this pull request into a Git repository by running: $ git pull https://github.com/jbertram/activemq-6 master_work Alternatively you can review and

[jira] [Created] (AMQ-5534) Generic JMS connection pool should be able to renew connections after JMSException

Dejan Bosanac created AMQ-5534: -- Summary: Generic JMS connection pool should be able to renew connections after JMSException Key: AMQ-5534 URL: https://issues.apache.org/jira/browse/AMQ-5534 Project:

[jira] [Updated] (ACTIVEMQ6-70) Implement resource limits

[ https://issues.apache.org/jira/browse/ACTIVEMQ6-70?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic updated ACTIVEMQ6-70: - Affects Version/s: 6.0.0 Fix Version/s: 6.1.0 Implement resource limits

[GitHub] activemq-6 pull request: a few fixes coming from former branches

Github user asfgit closed the pull request at: https://github.com/apache/activemq-6/pull/73 --- 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

Re: AMQ2149LevelDBTest failures

that log has been reclaimed so I am not sure on your question, but I think for that test there is a single durable consumer, so I think order should be retained for that chap. Maybe verify that. The rollback should be limited to the commit reply lost case, I think. On 16 January 2015 at 04:37,

Re: AMQ2149LevelDBTest failures

Thanks Gary. I'm reading through the test code more carefully right now to understand the entirety of it's operation. You are correct - a durable consumer is used on Topics, although I need to verify that's actually used in the case that's failing. With a durable subscriber, the problem gets

[jira] [Created] (AMQCPP-559) Deadlock in concurrent condition

eagle518 created AMQCPP-559: --- Summary: Deadlock in concurrent condition Key: AMQCPP-559 URL: https://issues.apache.org/jira/browse/AMQCPP-559 Project: ActiveMQ C++ Client Issue Type: Bug

Jenkins build is still unstable: ActiveMQ-SysTest-Trunk » ActiveMQ :: System Tests #10

See https://builds.apache.org/job/ActiveMQ-SysTest-Trunk/org.apache.activemq$activemq-systest/10/

Jenkins build is unstable: ActiveMQ-SysTest-Trunk #10

See https://builds.apache.org/job/ActiveMQ-SysTest-Trunk/10/

[jira] [Commented] (AMQ-5527) Performance issues for org.apache.activemq.broker.jmx.QueueView.removeMessage

[ https://issues.apache.org/jira/browse/AMQ-5527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14288083#comment-14288083 ] Michael Rimov commented on AMQ-5527: I think my initial report was inaccurate and it

[GitHub] activemq-6 pull request: fixing checkstyle that I messed up on my ...

GitHub user clebertsuconic opened a pull request: https://github.com/apache/activemq-6/pull/74 fixing checkstyle that I messed up on my last commit You can merge this pull request into a Git repository by running: $ git pull https://github.com/clebertsuconic/activemq-6

[GitHub] activemq-6 pull request: fixing checkstyle that I messed up on my ...

Github user asfgit closed the pull request at: https://github.com/apache/activemq-6/pull/74 --- 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

[jira] [Commented] (AMQ-5225) broker will not start when using leveldb

[ https://issues.apache.org/jira/browse/AMQ-5225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14287759#comment-14287759 ] Marc Schöchlin commented on AMQ-5225: - This should be fixed :-) I do: {code} zip

[GitHub] activemq-6 pull request: THIS IS A TEST, DO NOT MERGE

GitHub user jbertram opened a pull request: https://github.com/apache/activemq-6/pull/75 THIS IS A TEST, DO NOT MERGE You can merge this pull request into a Git repository by running: $ git pull https://github.com/jbertram/activemq-6 master_bridgeTestFailure Alternatively

[GitHub] activemq-6 pull request: THIS IS A TEST, DO NOT MERGE

Github user jbertram closed the pull request at: https://github.com/apache/activemq-6/pull/75 --- 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