[jira] [Resolved] (AMQ-5841) activemq script returns a non zero exit code for successful operations

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

[jira] [Updated] (AMQ-5840) activemq-osgi should include activemq-blueprint

[ https://issues.apache.org/jira/browse/AMQ-5840?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tobias Heide updated AMQ-5840: -- Attachment: activemq-osgi-should-include-activemq-blueprint.patch activemq-osgi should include

[jira] [Created] (AMQ-5840) activemq-osgi should include activemq-blueprint

Tobias Heide created AMQ-5840: - Summary: activemq-osgi should include activemq-blueprint Key: AMQ-5840 URL: https://issues.apache.org/jira/browse/AMQ-5840 Project: ActiveMQ Issue Type: Bug

[jira] [Created] (AMQCPP-571) Unacknowledged messages dissappear from broker if session/consumer is closed and then re-created

Mark Williams created AMQCPP-571: Summary: Unacknowledged messages dissappear from broker if session/consumer is closed and then re-created Key: AMQCPP-571 URL: https://issues.apache.org/jira/browse/AMQCPP-571

[jira] [Updated] (AMQCPP-571) Unacknowledged messages dissappear from broker if session/consumer is closed and then re-created

[ https://issues.apache.org/jira/browse/AMQCPP-571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Williams updated AMQCPP-571: - Attachment: (was: LostMessages.cpp) Unacknowledged messages dissappear from broker if

[jira] [Updated] (AMQCPP-571) Unacknowledged messages dissappear from broker if session/consumer is closed and then re-created

[ https://issues.apache.org/jira/browse/AMQCPP-571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Williams updated AMQCPP-571: - Attachment: LostMessages.h Unacknowledged messages dissappear from broker if session/consumer is

[jira] [Created] (AMQ-5842) activemq script doesn't work on solaris because of su command

Thomas RICOU created AMQ-5842: - Summary: activemq script doesn't work on solaris because of su command Key: AMQ-5842 URL: https://issues.apache.org/jira/browse/AMQ-5842 Project: ActiveMQ Issue

[jira] [Assigned] (AMQ-5842) activemq script doesn't work on solaris because of su command

[ https://issues.apache.org/jira/browse/AMQ-5842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré reassigned AMQ-5842: - Assignee: Jean-Baptiste Onofré activemq script doesn't work on solaris because of

[jira] [Updated] (AMQ-5770) activemq-web-console feature doesn't install in Karaf 4 SNAPSHOT

[ https://issues.apache.org/jira/browse/AMQ-5770?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated AMQ-5770: -- Fix Version/s: 5.12.0 5.11.2 activemq-web-console feature doesn't

[jira] [Updated] (AMQ-5770) activemq-web-console feature doesn't install in Karaf 4 SNAPSHOT

[ https://issues.apache.org/jira/browse/AMQ-5770?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated AMQ-5770: -- Affects Version/s: 5.11.1 activemq-web-console feature doesn't install in Karaf 4

[jira] [Closed] (AMQ-5736) JMS 2.0 Support

[ https://issues.apache.org/jira/browse/AMQ-5736?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Pavlovich closed AMQ-5736. --- Resolution: Duplicate I'm good, looks like the dup issue has this covered. Thanks! JMS 2.0 Support

[jira] [Created] (AMQ-5846) High cpu usage if using masterslave discovery in network brokers

duff qiu created AMQ-5846: - Summary: High cpu usage if using masterslave discovery in network brokers Key: AMQ-5846 URL: https://issues.apache.org/jira/browse/AMQ-5846 Project: ActiveMQ Issue Type:

[jira] [Commented] (ARTEMIS-123) Import ActiveMQ OpenWire test framework

[ https://issues.apache.org/jira/browse/ARTEMIS-123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14586320#comment-14586320 ] Justin Bertram commented on ARTEMIS-123: This looks like a duplicate of

[jira] [Updated] (AMQ-5843) Add an option to include original message body for advisory messages

[ https://issues.apache.org/jira/browse/AMQ-5843?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christopher L. Shannon updated AMQ-5843: Summary: Add an option to include original message body for advisory messages (was:

[jira] [Commented] (AMQ-5843) Add option to include original message body for Advisory messages

[ https://issues.apache.org/jira/browse/AMQ-5843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14586384#comment-14586384 ] ASF GitHub Bot commented on AMQ-5843: - GitHub user cshannon opened a pull request:

[jira] [Updated] (ARTEMIS-136) XA should send FAIL instead of ERR in case of any communication issues

[ https://issues.apache.org/jira/browse/ARTEMIS-136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic updated ARTEMIS-136: Affects Version/s: 1.0.0 This also affects all versions of HornetQ. And from some

[jira] [Commented] (ARTEMIS-136) XA should send FAIL instead of ERR in case of any communication issues

[ https://issues.apache.org/jira/browse/ARTEMIS-136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14586644#comment-14586644 ] ASF GitHub Bot commented on ARTEMIS-136: GitHub user clebertsuconic opened a pull

[jira] [Comment Edited] (ARTEMIS-90) ClassNotFoundException when a backup server fails over after having failed back

[ https://issues.apache.org/jira/browse/ARTEMIS-90?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14586622#comment-14586622 ] Justin Bertram edited comment on ARTEMIS-90 at 6/15/15 8:31 PM:

[jira] [Created] (AMQ-5844) Introduce logic into the failover transport not to recreate aborted slow consumers.

Ganesh created AMQ-5844: --- Summary: Introduce logic into the failover transport not to recreate aborted slow consumers. Key: AMQ-5844 URL: https://issues.apache.org/jira/browse/AMQ-5844 Project: ActiveMQ

[jira] [Commented] (AMQ-5844) Introduce logic into the failover transport not to recreate aborted slow consumers.

[ https://issues.apache.org/jira/browse/AMQ-5844?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14586580#comment-14586580 ] Ganesh commented on AMQ-5844: - The FailoverTransport must remove slow consumer from its state so

[jira] [Assigned] (ARTEMIS-90) ClassNotFoundException when a backup server fails over after having failed back

[ https://issues.apache.org/jira/browse/ARTEMIS-90?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Bertram reassigned ARTEMIS-90: - Assignee: Justin Bertram ClassNotFoundException when a backup server fails over after

[jira] [Updated] (AMQ-5844) Introduce logic into the failover transport not to recreate aborted slow consumers.

[ https://issues.apache.org/jira/browse/AMQ-5844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ganesh updated AMQ-5844: Attachment: FailoverTransportDeleteSlowConsumerTest.java AMQ-5844-GMURTHY-PATCH.TXT Introduce logic

[jira] [Updated] (ARTEMIS-79) JMX: getFirstMessageAsJSON not suitable for large messages

[ https://issues.apache.org/jira/browse/ARTEMIS-79?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic updated ARTEMIS-79: --- Fix Version/s: 1.0.1 JMX: getFirstMessageAsJSON not suitable for large messages

[jira] [Created] (ARTEMIS-137) Review Logging implementation with i18n support

clebert suconic created ARTEMIS-137: --- Summary: Review Logging implementation with i18n support Key: ARTEMIS-137 URL: https://issues.apache.org/jira/browse/ARTEMIS-137 Project: ActiveMQ Artemis