Re: [VOTE] Apache ActiveMQ 5.4.0

+1 On Monday, August 16, 2010, Guillaume Nodet gno...@gmail.com wrote: +1 On Sat, Aug 14, 2010 at 03:17, Hadrian Zbarcea hzbar...@gmail.com wrote: A new release activemq-5.4.0 is out with approximately 283 issues resolved. Please find the staging repo here:

[jira] Assigned: (AMQ-2203) Duplication of Camel routes in activemq.xml and applicationContext.xml for Camel web app.

[ https://issues.apache.org/activemq/browse/AMQ-2203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dejan Bosanac reassigned AMQ-2203: -- Assignee: Dejan Bosanac Duplication of Camel routes in activemq.xml and

[jira] Created: (AMQ-2870) Messages that don't match a message selector for a durable subscription are stored causing the persistent store to eventually fill up

Messages that don't match a message selector for a durable subscription are stored causing the persistent store to eventually fill up - Key:

[jira] Resolved: (AMQCPP-310) Add support for Message Priority Dispatching to CMS

[ https://issues.apache.org/activemq/browse/AMQCPP-310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish resolved AMQCPP-310. - Resolution: Fixed Implemented in trunk. Tests added. Add support for Message Priority

[jira] Commented: (AMQ-2598) Configuring HTTP networkConnector with proxyHost, proxyPort results in Invalid connect parameters: {proxyPort=nn)} error

[ https://issues.apache.org/activemq/browse/AMQ-2598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=61213#action_61213 ] Gregg Saffell commented on AMQ-2598: Thanks, we will update our activemq.xml files

[jira] Resolved: (AMQ-2870) Messages that don't match a message selector for a durable subscription are stored causing the persistent store to eventually fill up

[ https://issues.apache.org/activemq/browse/AMQ-2870?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Tully resolved AMQ-2870. - Resolution: Fixed fix committed in r985993 - unmatched messages are now acked immediately by a

[jira] Updated: (AMQ-2584) Massege store is not cleaned when durable topic subscribers are refusing messages

[ https://issues.apache.org/activemq/browse/AMQ-2584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Tully updated AMQ-2584: Attachment: AMQ2584Test.java junit test case based on submitted test but borrowing from the junit test

[jira] Assigned: (AMQ-2584) Massege store is not cleaned when durable topic subscribers are refusing messages

[ https://issues.apache.org/activemq/browse/AMQ-2584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Tully reassigned AMQ-2584: --- Assignee: Gary Tully Massege store is not cleaned when durable topic subscribers are refusing

[jira] Commented: (AMQ-2584) Massege store is not cleaned when durable topic subscribers are refusing messages

[ https://issues.apache.org/activemq/browse/AMQ-2584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=61216#action_61216 ] Gary Tully commented on AMQ-2584: - The difference may be the use of a small journal data file

[jira] Resolved: (AMQ-2868) NegativeQueueTest and JDBC variant - intermittent failure - missing message when cache exhausted

[ https://issues.apache.org/activemq/browse/AMQ-2868?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Tully resolved AMQ-2868. - Resolution: Fixed sticking with the shared lock for the time being. NegativeQueueTest and JDBC

[jira] Commented: (AMQNET-271) Add support for a Message Transformer to be set in NMS API

[ https://issues.apache.org/activemq/browse/AMQNET-271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=61218#action_61218 ] Timothy Bish commented on AMQNET-271: - So would adding sine delegate definitions like

[jira] Created: (AMQNET-272) Received BytesMessages should be in read-only mode by default

Received BytesMessages should be in read-only mode by default - Key: AMQNET-272 URL: https://issues.apache.org/activemq/browse/AMQNET-272 Project: ActiveMQ .Net Issue Type: Bug

Re: [VOTE] Apache ActiveMQ 5.4.0

Looks good. Here's my non-binding +1. FYI, we're firing up a Geronimo 2.2.x TCK run with 5.4.0. Will let you know if there are any problems... --kevan On Aug 13, 2010, at 9:17 PM, Hadrian Zbarcea wrote: A new release activemq-5.4.0 is out with approximately 283 issues resolved. Please find

[jira] Commented: (AMQNET-271) Add support for a Message Transformer to be set in NMS API

[ https://issues.apache.org/activemq/browse/AMQNET-271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=61219#action_61219 ] Jim Gomes commented on AMQNET-271: -- Yeah, those look good. Although, I would change the

Re: [VOTE] Apache ActiveMQ 5.4.0

+1 On Fri, Aug 13, 2010 at 6:17 PM, Hadrian Zbarcea hzbar...@gmail.com wrote: A new release activemq-5.4.0 is out with approximately 283 issues resolved. Please find the staging repo here: https://repository.apache.org/content/repositories/orgapacheactivemq-104/ The binary distribution is

[jira] Commented: (AMQNET-271) Add support for a Message Transformer to be set in NMS API

[ https://issues.apache.org/activemq/browse/AMQNET-271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=61220#action_61220 ] Timothy Bish commented on AMQNET-271: - Those names are fine. As for the JMS Spec

[jira] Commented: (AMQNET-272) Received BytesMessages should be in read-only mode by default

[ https://issues.apache.org/activemq/browse/AMQNET-272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=61221#action_61221 ] Timothy Bish commented on AMQNET-272: - You want me to look into this one? Send it my way

[jira] Commented: (AMQNET-272) Received BytesMessages should be in read-only mode by default

[ https://issues.apache.org/activemq/browse/AMQNET-272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=61222#action_61222 ] Jim Gomes commented on AMQNET-272: -- I don't mind taking this one. I actually came across it

[jira] Commented: (AMQNET-272) Received BytesMessages should be in read-only mode by default

[ https://issues.apache.org/activemq/browse/AMQNET-272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=61223#action_61223 ] Timothy Bish commented on AMQNET-272: - K, I'll fix the NMS BytesMessage Test so it calls

[jira] Resolved: (AMQNET-272) Received BytesMessages should be in read-only mode by default

[ https://issues.apache.org/activemq/browse/AMQNET-272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jim Gomes resolved AMQNET-272. -- Resolution: Working as Designed Fixed the unit test to reset the sent message flags. Nothing

[jira] Work logged: (AMQNET-272) Received BytesMessages should be in read-only mode by default

[ https://issues.apache.org/activemq/browse/AMQNET-272?page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#action_36933 ] Jim Gomes logged work on AMQNET-272: Author: Jim Gomes Created on: 16/Aug/10 06:24

[RESULT][VOTE] Apache ActiveMQ 5.4.0

The vote passes with: [8] +1 - binding votes (dejan, tim, hiram, rob, guillaume, gary, jim, hadrian) [2] +1 - non-binding votes (jean-baptiste, kevan) [0] -1 I will promote the artifacts to the central repo in the morning. I am over a slow connection now and it's getting late. Many thanks to

[jira] Commented: (AMQ-2574) Try to stop OSGi bundle when closing application context

[ https://issues.apache.org/activemq/browse/AMQ-2574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=61226#action_61226 ] Bruce Snyder commented on AMQ-2574: --- A few items of note: # The