Hi
Do you have any plans to release 5.9.2 in the future? There are only 2
commits, but the commits would solve one problem on ServiceMix 5.0.x and
would let us remove a workaround with the web console.
Kindly regards
Krzysztof
--
Krzysztof Sobkowiak
JEE OSS Architect | Technical Architect @
See
https://builds.apache.org/job/ActiveMQ/org.apache.activemq$activemq-jms-pool/1517/
See
https://builds.apache.org/job/ActiveMQ/org.apache.activemq$activemq-spring/1517/
+1
On 8 September 2014 15:43, Timothy Bish tabish...@gmail.com wrote:
Hello
This is a call for a vote on the release of Apache.NMS.ActiveMQ v1.6.4
This is a bug fix only release focusing on some issues with Consumers in
local transacted sessions where messages were getting marked as
[
https://issues.apache.org/jira/browse/AMQ-5349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jakub Korab updated AMQ-5349:
-
Summary: Master broker stays up without access to lease-database-locker
(was: Master broker stays without
Jakub Korab created AMQ-5349:
Summary: Master broker stays without access to
lease-database-locker
Key: AMQ-5349
URL: https://issues.apache.org/jira/browse/AMQ-5349
Project: ActiveMQ
Issue
Timothy Bish created AMQ-5350:
-
Summary: Separate the AMQP maxFrameSize setting from the
WireFormat maxFrameSize setting.
Key: AMQ-5350
URL: https://issues.apache.org/jira/browse/AMQ-5350
Project:
[
https://issues.apache.org/jira/browse/AMQ-5350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish resolved AMQ-5350.
---
Resolution: Fixed
Fixed on trunk.
Separate the AMQP maxFrameSize setting from the WireFormat
[
https://issues.apache.org/jira/browse/AMQ-5350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14127117#comment-14127117
]
clebert suconic commented on AMQ-5350:
--
do you still set maxFrameSize on the transport?
[
https://issues.apache.org/jira/browse/AMQ-5350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14127126#comment-14127126
]
Timothy Bish commented on AMQ-5350:
---
No, it's not set unless the URI of the
Rob Davies created AMQ-5351:
---
Summary: Create a Camel routes plugin to load routes dynamically
into the broker
Key: AMQ-5351
URL: https://issues.apache.org/jira/browse/AMQ-5351
Project: ActiveMQ
[
https://issues.apache.org/jira/browse/AMQ-5351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rob Davies resolved AMQ-5351.
-
Resolution: Fixed
resolved by refs/heads/trunk b2e6a4166 - 7ca25965d
Create a Camel routes plugin to
Robbie Gemmell created AMQ-5352:
---
Summary: AMQP messages published transactionally should be
accepted using a TransactionalState
Key: AMQ-5352
URL: https://issues.apache.org/jira/browse/AMQ-5352
[
https://issues.apache.org/jira/browse/AMQ-5352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robbie Gemmell updated AMQ-5352:
Attachment: AMQ-5352.patch
Attaching patch which checks if the deliverystate was transactional and if
+1
On Mon, Sep 8, 2014 at 7:43 AM, Timothy Bish tabish...@gmail.com wrote:
Hello
This is a call for a vote on the release of Apache.NMS.ActiveMQ v1.6.4
This is a bug fix only release focusing on some issues with Consumers in
local transacted sessions where messages were getting marked as
[
https://issues.apache.org/jira/browse/AMQ-5352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish resolved AMQ-5352.
---
Resolution: Fixed
Fix Version/s: 5.11.0
Fixed on trunk.
AMQP messages published
[
https://issues.apache.org/jira/browse/AMQ-5080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14127472#comment-14127472
]
Fer Troya commented on AMQ-5080:
Hi [~gtully] I've noticed this commit refers to this fix as
Daniel Kulp created AMQ-5353:
Summary: Mismatch of camel versions allowed
Key: AMQ-5353
URL: https://issues.apache.org/jira/browse/AMQ-5353
Project: ActiveMQ
Issue Type: Bug
[
https://issues.apache.org/jira/browse/AMQ-5185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14127819#comment-14127819
]
Paddy commented on AMQ-5185:
virtual topic workaround requires consumers to use queues and MQTT
[
https://issues.apache.org/jira/browse/AMQ-5185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14127845#comment-14127845
]
Timothy Bish commented on AMQ-5185:
---
The workaround transparently subscribes the connect
See
https://builds.apache.org/job/ActiveMQ/org.apache.activemq$activemq-stomp/1518/
--
[00:38:57] [INFO]
[INFO]
See https://builds.apache.org/job/ActiveMQ/1518/changes
Changes:
[tabish121] https://issues.apache.org/jira/browse/AMQ-5350
[rajdavies] added CamelRoutesBrokerPlugin for
https://issues.apache.org/jira/browse/AMQ-5351
[tabish121] https://issues.apache.org/jira/browse/AMQ-5352
[dkulp]
22 matches
Mail list logo