Re: [VOTE] Apache ActiveMQ 5.3.2

+1 On 27 Apr 2010, at 00:04, David Jencks wrote: Hi, I've staged a release candidate for ActiveMQ 5.3.2. The main driver for this is to get the osgi version range fixes into a release usable by the upcoming geronimo 3.0 milestone. The changes since the recent 5.3.1: merging 881433

Re: [VOTE] Apache ActiveMQ 5.3.2

+1 BTW we don't need to redo a release to change svn tag. Let's do it manually with svn mv. It would be good to have apache pom 7 and everything fixed for the 5.4 release though. Cheers -- Dejan Bosanac - http://twitter.com/dejanb Open Source Integration - http://fusesource.com/ ActiveMQ in

[jira] Resolved: (AMQ-2183) Master/slave out of sync with multiple consumers of a VirtualTopic on the same broker

[ https://issues.apache.org/activemq/browse/AMQ-2183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dejan Bosanac resolved AMQ-2183. Resolution: Fixed Fixed with svn revision 938353. The order of TransactionBroker and

Re: [VOTE] Apache ActiveMQ 5.3.2

+1 On 27 April 2010 00:04, David Jencks david_jen...@yahoo.com wrote: Hi, I've staged a release candidate for ActiveMQ 5.3.2. The main driver for this is to get the osgi version range fixes into a release usable by the upcoming geronimo 3.0 milestone. The changes since the recent 5.3.1:

Re: [VOTE] Apache ActiveMQ 5.3.2

+1 On Mon, 2010-04-26 at 16:04 -0700, David Jencks wrote: Hi, I've staged a release candidate for ActiveMQ 5.3.2. The main driver for this is to get the osgi version range fixes into a release usable by the upcoming geronimo 3.0 milestone. The changes since the recent 5.3.1:

[jira] Assigned: (AMQ-2714) Apache ActiveMQ is prone to XSS Vulnerability

[ https://issues.apache.org/activemq/browse/AMQ-2714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dejan Bosanac reassigned AMQ-2714: -- Assignee: Dejan Bosanac Apache ActiveMQ is prone to XSS Vulnerability

[jira] Commented: (AMQNET-249) Is API Receive having ordering problem?

[ https://issues.apache.org/activemq/browse/AMQNET-249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=59123#action_59123 ] jim yu commented on AMQNET-249: --- Hi, Timothy, Thanks for your reply and the information, but I

Re: [VOTE] Apache ActiveMQ 5.3.2

+1 On Mon, Apr 26, 2010 at 8:34 PM, Bruce Snyder bruce.sny...@gmail.com wrote: On Mon, Apr 26, 2010 at 6:32 PM, Bruce Snyder bruce.sny...@gmail.com wrote: On Mon, Apr 26, 2010 at 5:04 PM, David Jencks david_jen...@yahoo.com wrote: Hi, I've staged a release candidate for ActiveMQ 5.3.2.  The

[jira] Commented: (AMQNET-249) Is API Receive having ordering problem?

[ https://issues.apache.org/activemq/browse/AMQNET-249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=59124#action_59124 ] Timothy Bish commented on AMQNET-249: - First thing I'd recommend is that you upgrade to

[jira] Updated: (AMQ-2714) Apache ActiveMQ is prone to XSS Vulnerability

[ https://issues.apache.org/activemq/browse/AMQ-2714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dejan Bosanac updated AMQ-2714: --- Attachment: AMQ-2714.zip Apache ActiveMQ is prone to XSS Vulnerability

[jira] Resolved: (AMQ-2714) Apache ActiveMQ is prone to XSS Vulnerability

[ https://issues.apache.org/activemq/browse/AMQ-2714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dejan Bosanac resolved AMQ-2714. Fix Version/s: 5.4.0 Resolution: Fixed I confirmed the problem in 5.3.x versions.

Hudson build became unstable: ActiveMQ » ActiveMQ :: RA #335

See http://hudson.zones.apache.org/hudson/job/ActiveMQ/org.apache.activemq$activemq-ra/335/

Hudson build is still unstable: ActiveMQ » ActiveMQ :: Core #335

See http://hudson.zones.apache.org/hudson/job/ActiveMQ/org.apache.activemq$activemq-core/changes

Hudson build is still unstable: ActiveMQ #335

See http://hudson.zones.apache.org/hudson/job/ActiveMQ/changes

Re: [VOTE] Apache ActiveMQ 5.3.2

+1 - Jim -Original Message- From: David Jencks david_jen...@yahoo.com Date: Mon, 26 Apr 2010 16:04:39 To: dev@activemq.apache.org Cc: Geronimo Dev List \(JIRA\)d...@geronimo.apache.org Subject: [VOTE] Apache ActiveMQ 5.3.2 Hi, I've staged a release candidate for ActiveMQ 5.3.2. The

[jira] Commented: (AMQ-2636) Add support for setting the Differentiated Services or Type Of Service on outgoing TCP/IP packets to support Quality Of Service

[ https://issues.apache.org/activemq/browse/AMQ-2636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=59128#action_59128 ] Dejan Bosanac commented on AMQ-2636: added missing diff serv names with svn revision 938461

Re: [VOTE] Apache ActiveMQ 5.3.2

On Mon, Apr 26, 2010 at 5:04 PM, David Jencks david_jen...@yahoo.com wrote: Hi, I've staged a release candidate for ActiveMQ 5.3.2.  The main driver for this is to get the osgi version range fixes into a release usable by the upcoming geronimo 3.0 milestone. The changes since the recent

[jira] Commented: (AMQ-2714) Apache ActiveMQ is prone to XSS Vulnerability

[ https://issues.apache.org/activemq/browse/AMQ-2714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=59133#action_59133 ] arun kethipelly commented on AMQ-2714: -- Hi Dejan, Thanks for the prompt reply and fixing

[jira] Commented: (AMQ-2659) JMSException incorrectly thrown when using XAConnection/XASession outside a transaction

[ https://issues.apache.org/activemq/browse/AMQ-2659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=59134#action_59134 ] Eugene Rodos commented on AMQ-2659: --- Isn't an ack sent at the end of ActiveMQSession.run()

[jira] Commented: (AMQ-2659) JMSException incorrectly thrown when using XAConnection/XASession outside a transaction

[ https://issues.apache.org/activemq/browse/AMQ-2659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=59135#action_59135 ] Gary Tully commented on AMQ-2659: - yea, in the run() case it is. The issue is for other regular

Re: [VOTE] Apache ActiveMQ 5.3.2

I think leaving the tag as is will be fine, having the correct info in the pom is important. On 27 April 2010 17:49, David Jencks david_jen...@yahoo.com wrote: On Apr 27, 2010, at 1:21 AM, Dejan Bosanac wrote: +1 BTW we don't need to redo a release to change svn tag. Let's do it

[jira] Commented: (AMQ-2659) JMSException incorrectly thrown when using XAConnection/XASession outside a transaction

[ https://issues.apache.org/activemq/browse/AMQ-2659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=59136#action_59136 ] Eugene Rodos commented on AMQ-2659: --- I still don't understand why using XASession without a

[jira] Commented: (AMQ-2085) AMQ should not install a JMXConnectorServer for an MBeanServer it does not create

[ https://issues.apache.org/activemq/browse/AMQ-2085?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=59138#action_59138 ] Phil Pickett commented on AMQ-2085: --- I'm seeing some different behavior between a webapp with

[jira] Commented: (AMQNET-249) Is API Receive having ordering problem?

[ https://issues.apache.org/activemq/browse/AMQNET-249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=59139#action_59139 ] jim yu commented on AMQNET-249: --- Hi, Thanks for your replay. I was using NMS 1.2.0 at first

Hudson build is back to stable : ActiveMQ » ActiveMQ :: RA #336

See http://hudson.zones.apache.org/hudson/job/ActiveMQ/org.apache.activemq$activemq-ra/336/