See
https://builds.apache.org/job/ActiveMQ/org.apache.activemq$activemq-unit-tests/1522/changes
Changes:
[gtully] add info log message for a queue purge event
--
[...truncated 659 lines...]
[05:50:41] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0,
See https://builds.apache.org/job/ActiveMQ/1522/changes
Changes:
[gtully] add info log message for a queue purge event
[gtully] https://issues.apache.org/jira/browse/AMQ-4705 - verify lock sanity on
acquire so master cannot start and immediatly fail with a keepalive failure
[
https://issues.apache.org/jira/browse/AMQ-5121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dejan Bosanac resolved AMQ-5121.
Resolution: Fixed
Fix Version/s: 5.11.0
Assignee: Dejan Bosanac (was: Jean-Baptiste
GitHub user shanielh opened a pull request:
https://github.com/apache/activemq-apollo/pull/7
fix web administration console message truncate bug APLO-362
https://issues.apache.org/jira/browse/APLO-362
The fix is in the lines 765 - 769, No idea why the diff is so big.
You
See
https://builds.apache.org/job/ActiveMQ-Trunk-Deploy/org.apache.activemq$activemq-parent/1065/
See https://builds.apache.org/job/ActiveMQ-Trunk-Deploy/1065/changes
[
https://issues.apache.org/jira/browse/AMQ-5364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
AR updated AMQ-5364:
Attachment: ActivemqNbTests.tar.gz
MQTT Unsubscribe does not work as intended in network of brokers scenario
AR created AMQ-5364:
---
Summary: MQTT Unsubscribe does not work as intended in network of
brokers scenario
Key: AMQ-5364
URL: https://issues.apache.org/jira/browse/AMQ-5364
Project: ActiveMQ
Issue Type:
AR created AMQ-5365:
---
Summary: MQTT topic name in received message is wrong in network
of brokers scenario
Key: AMQ-5365
URL: https://issues.apache.org/jira/browse/AMQ-5365
Project: ActiveMQ
Issue Type:
[
https://issues.apache.org/jira/browse/AMQ-5364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
AR updated AMQ-5364:
Description:
I’m trying to make sure that if an unsubscribe() is done for an existing
durable topic in any of the brokers,
See
https://builds.apache.org/job/ActiveMQ/org.apache.activemq$activemq-runtime-config/1523/
See
https://builds.apache.org/job/ActiveMQ/org.apache.activemq$activemq-leveldb-store/1523/
See https://builds.apache.org/job/ActiveMQ/1523/changes
Changes:
[dejan] https://issues.apache.org/jira/browse/AMQ-5121 - use jmxLocal in karaf
only for jmx-based commands
[gtully] improve trace logging on failure and tidy up future - try to nail down
intermittent duplex bridge half start
Claus Ibsen created AMQ-5366:
Summary: Upgrade to Camel 2.14
Key: AMQ-5366
URL: https://issues.apache.org/jira/browse/AMQ-5366
Project: ActiveMQ
Issue Type: Task
Components:
[
https://issues.apache.org/jira/browse/AMQ-5366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved AMQ-5366.
--
Resolution: Fixed
Upgrade to Camel 2.14
-
Key: AMQ-5366
15 matches
Mail list logo