Re: [VOTE] Apache ActiveMQ 5.11.0 (rc3)

[artnaseef]

Re-reading the entire thread, it appears there is an mbean leak.



--
View this message in context: 
http://activemq.2283324.n4.nabble.com/VOTE-Apache-ActiveMQ-5-11-0-rc3-tp4690743p4691397.html
Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.

Re: [VOTE] Apache ActiveMQ 5.11.0 (rc3)

[artnaseef]

A leak is a major concern.  

With that said, I have questions.  First, I thought the creation of addition
mbeans was failing, is that not right?  If so, then what is actually
leaking?  Are the mbeans being created but not removed?

Also, can you clarify under what conditions this occurs?  For example, does
it involve the use of an anonymous producer?




--
View this message in context: 
http://activemq.2283324.n4.nabble.com/VOTE-Apache-ActiveMQ-5-11-0-rc3-tp4690743p4691394.html
Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.

Re: [VOTE] Apache ActiveMQ 5.11.0 (rc3)

[Claus Ibsen]

On Wed, Feb 11, 2015 at 12:00 AM, artnaseef  wrote:
> Hey Claus - we can work on a 5.10.2; this bug exists in 5.10.1?
>

Yes 5.10.1 and 5.11.0 are affected.


> Before starting down that route, though, is it possible to clarify the
> impact of this bug?  It sounds like a nuisance from what I read - and could
> hurt performance in some use-cases.  Is that fair?
>
>

IMHO its a major issue that can cause the broker to run out of memory,
and of course before that slow down. And managing the broker becomes
more problematic as the JMX tree has an ever grown number of mbeans.

The issue is caused when clients are using JMS and the activemq-pool
and/or activemq-jms-pool.
And out of the box Camel users would usually do that.



>
> --
> View this message in context: 
> http://activemq.2283324.n4.nabble.com/VOTE-Apache-ActiveMQ-5-11-0-rc3-tp4690743p4691299.html
> Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.



-- 
Claus Ibsen
-
Red Hat, Inc.
Email: cib...@redhat.com
Twitter: davsclaus
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen
hawtio: http://hawt.io/
fabric8: http://fabric8.io/

Re: [VOTE] Apache ActiveMQ 5.11.0 (rc3)

[artnaseef]

Hey Claus - we can work on a 5.10.2; this bug exists in 5.10.1?

Before starting down that route, though, is it possible to clarify the
impact of this bug?  It sounds like a nuisance from what I read - and could
hurt performance in some use-cases.  Is that fair?



--
View this message in context: 
http://activemq.2283324.n4.nabble.com/VOTE-Apache-ActiveMQ-5-11-0-rc3-tp4690743p4691299.html
Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.

Re: [VOTE] Apache ActiveMQ 5.11.0 (rc3)

[Claus Ibsen]

On Thu, Feb 5, 2015 at 7:14 PM, Paul Gale  wrote:
> Given Claus' discovery does the severity of the issue warrant an immediate
> dot release 5.11.1?
>

Its fixed now on master and 2.11 branch. And IMHO should be backported
to 5.10.x branch as well.

Patch releases would be a good idea, starting with 5.10.2, and then
catch up with a few other fixes before doing 5.11.1.


> Thanks,
> Paul
>
> On Thu, Feb 5, 2015 at 9:39 AM, Claus Ibsen  wrote:
>
>> Hi
>>
>> Okay I have narrowed it down to the git commit that caused this issue.
>> I posted that in the ticket.
>>
>> It its due this ticket:  https://issues.apache.org/jira/browse/AMQ-5015
>>
>> On Wed, Feb 4, 2015 at 10:39 AM, Claus Ibsen 
>> wrote:
>> > Hi
>> >
>> > I logged a ticket about this. Not sure what the title it, but I
>> > suspect its related to the activemq-pool.
>> >
>> > I found an easier way of reproducing it using the
>> camel-example-management.
>> > https://issues.apache.org/jira/browse/AMQ-5564
>> >
>> > Just change the AMQ version in its pom.xml
>> >
>> > 
>> >
>>  
>> org.apache.camel.example.management.*
>> >
>>  
>> org.apache.activemq.xbean,org.apache.activemq.broker,org.apache.activemq.pool
>> >   
>> >   
>> >   5.11.0
>> > 
>> >
>> > I attached screenshot of 5.10.0 working and 5.10.1 and 5.11.0 failing.
>> > So as the issue is introduced in 5.10.1 that narrows down what code
>> > change caused this, as it must be a commit in that patch branch.
>> >
>> > On Wed, Feb 4, 2015 at 10:24 AM, Claus Ibsen 
>> wrote:
>> >> Hi
>> >>
>> >> Just upgraded Camel master branch to 5.11.0 and you can reproduce the
>> >> issue there also
>> >>
>> >> cd examples/camel-example-management
>> >> mvn clean install camel:run
>> >>
>> >> Connect to the JVM using jconsole.
>> >>
>> >> Notice the AcitveMQ tree under dynamic producers keeps adding new
>> >> mbeans, until your JVM runs out of memory.
>> >>
>> >> On Wed, Feb 4, 2015 at 10:11 AM, Claus Ibsen 
>> wrote:
>> >>> Hi
>> >>>
>> >>> I have done as Arthur suggested to dump the stacktrace, and also with
>> >>> Gary's turn on|off the anonoymous producers.
>> >>>
>> >>> I posted output from console as 2 gists
>> >>>
>> >>> https://gist.github.com/davsclaus/b5fbb1287d383107e599
>> >>>
>> >>> https://gist.github.com/davsclaus/0472ed0ab85ec5af9e79
>> >>>
>> >>> On Wed, Feb 4, 2015 at 12:05 AM, Gary Tully 
>> wrote:
>>  claus, that looks like producers are not being cached - I thought the
>>  culprit may be https://issues.apache.org/jira/browse/AMQ-4968 but
>> that
>>  would have made 5.10. In any event, can you set
>>  useAnonymousProducers=false on your activemq pooled connection
>>  factory.
>> 
>>  On 3 February 2015 at 16:55, Claus Ibsen 
>> wrote:
>> > Hi
>> >
>> > Just wanted to say I have stumbled on a weird issue with the 5.11.0
>> > release which I had trouble reproducing consistently.
>> >
>> > The issue is subtle causing AMQ to continuously re-create dynamic
>> > producer mbeans in the JMX tree. This is using a Camel spring app
>> with
>> > the AMQ connection pool.
>> >
>> > Though just now I was able to see that 5.10.0 was stable and the
>> > mbeans didnt re-create continusly, but with 5.11.0 that happens (with
>> > no other change that switching from 5.10.0 to 5.11.0)
>> >
>> > Though I think that issue could go unnoticed as the jmx tree looks
>> > okay, but you may discover a flicker in jconsole when it redraws, and
>> > then there is a little CPU time to create/destroy the mbeans.
>> >
>> > I noticed this with hawtio as it also "flicker" when the jmx tree is
>> > redrawn. And therefore was using hawtio to track down the issue.
>> >
>> >
>> > I enabled a WARN logging when a mbean was registerede/unregistered
>> and
>> > you can see
>> >
>> > WARN  | ActiveMQ Transport: tcp:///127.0.0.1:56632@31316 | JMX
>> > notification:
>> javax.management.MBeanServerNotification[source=JMImplementation:type=MBeanServerDelegate][type=JMX.mbean.registered][message=][mbeanName=org.apache.activemq:type=Broker,brokerName=broker1,endpoint=dynamicProducer,clientId=ID_davsclaus.air-56625-1422981975940-4_5,producerId=ID_davsclaus.air-56625-1422981975940-5_6_1_8]
>> > WARN  | ActiveMQ Transport: tcp:///127.0.0.1:56633@31316 | JMX
>> > notification:
>> javax.management.MBeanServerNotification[source=JMImplementation:type=MBeanServerDelegate][type=JMX.mbean.registered][message=][mbeanName=org.apache.activemq:type=Broker,brokerName=broker1,endpoint=dynamicProducer,clientId=ID_davsclaus.air-56625-1422981975940-4_6,producerId=ID_davsclaus.air-56625-1422981975940-5_7_1_8]
>> > WARN  | ActiveMQ Transport: tcp:///127.0.0.1:56634@31316 | JMX
>> > notification:
>> javax.management.MBeanServerNotification[source=JMImplementation:type=MBeanServerDelegate][type=JMX.mbean.registered][message=][mbeanName=org.apache.activemq:type=Broker,brokerName=broker1,endpoint=dynamicP

Re: [VOTE] Apache ActiveMQ 5.11.0 (rc3)

[Paul Gale]

Actually if you're working with a forked repo (as I am) the command will be:

git fetch --tags upstream

Just an FYI


Thanks,
Paul

On Thu, Feb 5, 2015 at 4:38 PM, artnaseef  wrote:

> Yup:
>
> git tag -v activemq-5.11.0
>
>
> git fetch --tags
>
> get tag -v actrivemq-5.11.0
>
>
>
>
> --
> View this message in context:
> http://activemq.2283324.n4.nabble.com/VOTE-Apache-ActiveMQ-5-11-0-rc3-tp4690743p4691128.html
> Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.
>

Re: [VOTE] Apache ActiveMQ 5.11.0 (rc3)

[artnaseef]

Yup:

git tag -v activemq-5.11.0


git fetch --tags

get tag -v actrivemq-5.11.0




--
View this message in context: 
http://activemq.2283324.n4.nabble.com/VOTE-Apache-ActiveMQ-5-11-0-rc3-tp4690743p4691128.html
Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.

Re: [VOTE] Apache ActiveMQ 5.11.0 (rc3)

[artnaseef]

Ahh, good catch dkulp.  Perhaps Paul needs to update his repo?  I think I
need to do that too.



--
View this message in context: 
http://activemq.2283324.n4.nabble.com/VOTE-Apache-ActiveMQ-5-11-0-rc3-tp4690743p4691127.html
Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.

Re: [VOTE] Apache ActiveMQ 5.11.0 (rc3)

[Daniel Kulp]

> On Feb 5, 2015, at 3:15 PM, Paul Gale  wrote:
> 
> I am trying to build 5.11.0 based on the Git tag "activemq-5.11.0".
> However, this tag points to commit 48b0cf3 dating from 2014-12-29.
> 
> Shouldn't this tag point to commit 4ba1a16 dated 2015-01-30? If so, can one
> of the committers please move said tag?

The tag seems OK in the Apache repo which is the one that matters:

https://git-wip-us.apache.org/repos/asf?p=activemq.git;a=tag;h=66bd5da9405765ddbc950b4f1c5a6ef6195207e5


Dan



> 
> Thanks,
> Paul
> 
> On Thu, Feb 5, 2015 at 2:39 PM, artnaseef  wrote:
> 
>> Good question - do we know the exact conditions required to cause the
>> problem?  And all of the impacts when the problem occurs?
>> 
>> 
>> 
>> --
>> View this message in context:
>> http://activemq.2283324.n4.nabble.com/VOTE-Apache-ActiveMQ-5-11-0-rc3-tp4690743p4691118.html
>> Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.
>> 

-- 
Daniel Kulp
dk...@apache.org - http://dankulp.com/blog
Talend Community Coder - http://coders.talend.com

Re: [VOTE] Apache ActiveMQ 5.11.0 (rc3)

[artnaseef]

Cool - thanks Tim.  Let me know if I can help.



--
View this message in context: 
http://activemq.2283324.n4.nabble.com/VOTE-Apache-ActiveMQ-5-11-0-rc3-tp4690743p4691124.html
Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.

Re: [VOTE] Apache ActiveMQ 5.11.0 (rc3)

[artnaseef]

The tag should be moved to the actual release.  I don't want to touch that
myself though as I do not know how to be sure which commit is truly the
correct one.



--
View this message in context: 
http://activemq.2283324.n4.nabble.com/VOTE-Apache-ActiveMQ-5-11-0-rc3-tp4690743p4691123.html
Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.

Re: [VOTE] Apache ActiveMQ 5.11.0 (rc3)

[Paul Gale]

I am trying to build 5.11.0 based on the Git tag "activemq-5.11.0".
However, this tag points to commit 48b0cf3 dating from 2014-12-29.

Shouldn't this tag point to commit 4ba1a16 dated 2015-01-30? If so, can one
of the committers please move said tag?

Thanks,
Paul

On Thu, Feb 5, 2015 at 2:39 PM, artnaseef  wrote:

> Good question - do we know the exact conditions required to cause the
> problem?  And all of the impacts when the problem occurs?
>
>
>
> --
> View this message in context:
> http://activemq.2283324.n4.nabble.com/VOTE-Apache-ActiveMQ-5-11-0-rc3-tp4690743p4691118.html
> Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.
>

Re: [VOTE] Apache ActiveMQ 5.11.0 (rc3)

[Timothy Bish]

On 02/05/2015 02:37 PM, artnaseef wrote:

Good find Claus.  I'll try to find time tonight to look at that one as it's
an area I've been in before.



--
View this message in context: 
http://activemq.2283324.n4.nabble.com/VOTE-Apache-ActiveMQ-5-11-0-rc3-tp4690743p4691117.html
Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.
.


I'm on it.

--
Tim Bish
Sr Software Engineer | RedHat Inc.
tim.b...@redhat.com | www.redhat.com
skype: tabish121 | twitter: @tabish121
blog: http://timbish.blogspot.com/

Re: [VOTE] Apache ActiveMQ 5.11.0 (rc3)

[artnaseef]

Good question - do we know the exact conditions required to cause the
problem?  And all of the impacts when the problem occurs?



--
View this message in context: 
http://activemq.2283324.n4.nabble.com/VOTE-Apache-ActiveMQ-5-11-0-rc3-tp4690743p4691118.html
Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.

Re: [VOTE] Apache ActiveMQ 5.11.0 (rc3)

[artnaseef]

Good find Claus.  I'll try to find time tonight to look at that one as it's
an area I've been in before.



--
View this message in context: 
http://activemq.2283324.n4.nabble.com/VOTE-Apache-ActiveMQ-5-11-0-rc3-tp4690743p4691117.html
Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.

Re: [VOTE] Apache ActiveMQ 5.11.0 (rc3)

[Paul Gale]

Given Claus' discovery does the severity of the issue warrant an immediate
dot release 5.11.1?

Thanks,
Paul

On Thu, Feb 5, 2015 at 9:39 AM, Claus Ibsen  wrote:

> Hi
>
> Okay I have narrowed it down to the git commit that caused this issue.
> I posted that in the ticket.
>
> It its due this ticket:  https://issues.apache.org/jira/browse/AMQ-5015
>
> On Wed, Feb 4, 2015 at 10:39 AM, Claus Ibsen 
> wrote:
> > Hi
> >
> > I logged a ticket about this. Not sure what the title it, but I
> > suspect its related to the activemq-pool.
> >
> > I found an easier way of reproducing it using the
> camel-example-management.
> > https://issues.apache.org/jira/browse/AMQ-5564
> >
> > Just change the AMQ version in its pom.xml
> >
> > 
> >
>  
> org.apache.camel.example.management.*
> >
>  
> org.apache.activemq.xbean,org.apache.activemq.broker,org.apache.activemq.pool
> >   
> >   
> >   5.11.0
> > 
> >
> > I attached screenshot of 5.10.0 working and 5.10.1 and 5.11.0 failing.
> > So as the issue is introduced in 5.10.1 that narrows down what code
> > change caused this, as it must be a commit in that patch branch.
> >
> > On Wed, Feb 4, 2015 at 10:24 AM, Claus Ibsen 
> wrote:
> >> Hi
> >>
> >> Just upgraded Camel master branch to 5.11.0 and you can reproduce the
> >> issue there also
> >>
> >> cd examples/camel-example-management
> >> mvn clean install camel:run
> >>
> >> Connect to the JVM using jconsole.
> >>
> >> Notice the AcitveMQ tree under dynamic producers keeps adding new
> >> mbeans, until your JVM runs out of memory.
> >>
> >> On Wed, Feb 4, 2015 at 10:11 AM, Claus Ibsen 
> wrote:
> >>> Hi
> >>>
> >>> I have done as Arthur suggested to dump the stacktrace, and also with
> >>> Gary's turn on|off the anonoymous producers.
> >>>
> >>> I posted output from console as 2 gists
> >>>
> >>> https://gist.github.com/davsclaus/b5fbb1287d383107e599
> >>>
> >>> https://gist.github.com/davsclaus/0472ed0ab85ec5af9e79
> >>>
> >>> On Wed, Feb 4, 2015 at 12:05 AM, Gary Tully 
> wrote:
>  claus, that looks like producers are not being cached - I thought the
>  culprit may be https://issues.apache.org/jira/browse/AMQ-4968 but
> that
>  would have made 5.10. In any event, can you set
>  useAnonymousProducers=false on your activemq pooled connection
>  factory.
> 
>  On 3 February 2015 at 16:55, Claus Ibsen 
> wrote:
> > Hi
> >
> > Just wanted to say I have stumbled on a weird issue with the 5.11.0
> > release which I had trouble reproducing consistently.
> >
> > The issue is subtle causing AMQ to continuously re-create dynamic
> > producer mbeans in the JMX tree. This is using a Camel spring app
> with
> > the AMQ connection pool.
> >
> > Though just now I was able to see that 5.10.0 was stable and the
> > mbeans didnt re-create continusly, but with 5.11.0 that happens (with
> > no other change that switching from 5.10.0 to 5.11.0)
> >
> > Though I think that issue could go unnoticed as the jmx tree looks
> > okay, but you may discover a flicker in jconsole when it redraws, and
> > then there is a little CPU time to create/destroy the mbeans.
> >
> > I noticed this with hawtio as it also "flicker" when the jmx tree is
> > redrawn. And therefore was using hawtio to track down the issue.
> >
> >
> > I enabled a WARN logging when a mbean was registerede/unregistered
> and
> > you can see
> >
> > WARN  | ActiveMQ Transport: tcp:///127.0.0.1:56632@31316 | JMX
> > notification:
> javax.management.MBeanServerNotification[source=JMImplementation:type=MBeanServerDelegate][type=JMX.mbean.registered][message=][mbeanName=org.apache.activemq:type=Broker,brokerName=broker1,endpoint=dynamicProducer,clientId=ID_davsclaus.air-56625-1422981975940-4_5,producerId=ID_davsclaus.air-56625-1422981975940-5_6_1_8]
> > WARN  | ActiveMQ Transport: tcp:///127.0.0.1:56633@31316 | JMX
> > notification:
> javax.management.MBeanServerNotification[source=JMImplementation:type=MBeanServerDelegate][type=JMX.mbean.registered][message=][mbeanName=org.apache.activemq:type=Broker,brokerName=broker1,endpoint=dynamicProducer,clientId=ID_davsclaus.air-56625-1422981975940-4_6,producerId=ID_davsclaus.air-56625-1422981975940-5_7_1_8]
> > WARN  | ActiveMQ Transport: tcp:///127.0.0.1:56634@31316 | JMX
> > notification:
> javax.management.MBeanServerNotification[source=JMImplementation:type=MBeanServerDelegate][type=JMX.mbean.registered][message=][mbeanName=org.apache.activemq:type=Broker,brokerName=broker1,endpoint=dynamicProducer,clientId=ID_davsclaus.air-56625-1422981975940-4_7,producerId=ID_davsclaus.air-56625-1422981975940-5_8_1_8]
> > WARN  | ActiveMQ Transport: tcp:///127.0.0.1:56626@31316 | JMX
> > notification:
> javax.management.MBeanServerNotification[source=JMImplementation:type=MBeanServerDelegate][type=JMX.mbean.registered][message=][mbeanName=org.apache.activemq:type=Broker,brokerName=brok

Re: [VOTE] Apache ActiveMQ 5.11.0 (rc3)

[Claus Ibsen]

Hi

Okay I have narrowed it down to the git commit that caused this issue.
I posted that in the ticket.

It its due this ticket:  https://issues.apache.org/jira/browse/AMQ-5015

On Wed, Feb 4, 2015 at 10:39 AM, Claus Ibsen  wrote:
> Hi
>
> I logged a ticket about this. Not sure what the title it, but I
> suspect its related to the activemq-pool.
>
> I found an easier way of reproducing it using the camel-example-management.
> https://issues.apache.org/jira/browse/AMQ-5564
>
> Just change the AMQ version in its pom.xml
>
> 
> 
> org.apache.camel.example.management.*
> 
> org.apache.activemq.xbean,org.apache.activemq.broker,org.apache.activemq.pool
>   
>   
>   5.11.0
> 
>
> I attached screenshot of 5.10.0 working and 5.10.1 and 5.11.0 failing.
> So as the issue is introduced in 5.10.1 that narrows down what code
> change caused this, as it must be a commit in that patch branch.
>
> On Wed, Feb 4, 2015 at 10:24 AM, Claus Ibsen  wrote:
>> Hi
>>
>> Just upgraded Camel master branch to 5.11.0 and you can reproduce the
>> issue there also
>>
>> cd examples/camel-example-management
>> mvn clean install camel:run
>>
>> Connect to the JVM using jconsole.
>>
>> Notice the AcitveMQ tree under dynamic producers keeps adding new
>> mbeans, until your JVM runs out of memory.
>>
>> On Wed, Feb 4, 2015 at 10:11 AM, Claus Ibsen  wrote:
>>> Hi
>>>
>>> I have done as Arthur suggested to dump the stacktrace, and also with
>>> Gary's turn on|off the anonoymous producers.
>>>
>>> I posted output from console as 2 gists
>>>
>>> https://gist.github.com/davsclaus/b5fbb1287d383107e599
>>>
>>> https://gist.github.com/davsclaus/0472ed0ab85ec5af9e79
>>>
>>> On Wed, Feb 4, 2015 at 12:05 AM, Gary Tully  wrote:
 claus, that looks like producers are not being cached - I thought the
 culprit may be https://issues.apache.org/jira/browse/AMQ-4968 but that
 would have made 5.10. In any event, can you set
 useAnonymousProducers=false on your activemq pooled connection
 factory.

 On 3 February 2015 at 16:55, Claus Ibsen  wrote:
> Hi
>
> Just wanted to say I have stumbled on a weird issue with the 5.11.0
> release which I had trouble reproducing consistently.
>
> The issue is subtle causing AMQ to continuously re-create dynamic
> producer mbeans in the JMX tree. This is using a Camel spring app with
> the AMQ connection pool.
>
> Though just now I was able to see that 5.10.0 was stable and the
> mbeans didnt re-create continusly, but with 5.11.0 that happens (with
> no other change that switching from 5.10.0 to 5.11.0)
>
> Though I think that issue could go unnoticed as the jmx tree looks
> okay, but you may discover a flicker in jconsole when it redraws, and
> then there is a little CPU time to create/destroy the mbeans.
>
> I noticed this with hawtio as it also "flicker" when the jmx tree is
> redrawn. And therefore was using hawtio to track down the issue.
>
>
> I enabled a WARN logging when a mbean was registerede/unregistered and
> you can see
>
> WARN  | ActiveMQ Transport: tcp:///127.0.0.1:56632@31316 | JMX
> notification: 
> javax.management.MBeanServerNotification[source=JMImplementation:type=MBeanServerDelegate][type=JMX.mbean.registered][message=][mbeanName=org.apache.activemq:type=Broker,brokerName=broker1,endpoint=dynamicProducer,clientId=ID_davsclaus.air-56625-1422981975940-4_5,producerId=ID_davsclaus.air-56625-1422981975940-5_6_1_8]
> WARN  | ActiveMQ Transport: tcp:///127.0.0.1:56633@31316 | JMX
> notification: 
> javax.management.MBeanServerNotification[source=JMImplementation:type=MBeanServerDelegate][type=JMX.mbean.registered][message=][mbeanName=org.apache.activemq:type=Broker,brokerName=broker1,endpoint=dynamicProducer,clientId=ID_davsclaus.air-56625-1422981975940-4_6,producerId=ID_davsclaus.air-56625-1422981975940-5_7_1_8]
> WARN  | ActiveMQ Transport: tcp:///127.0.0.1:56634@31316 | JMX
> notification: 
> javax.management.MBeanServerNotification[source=JMImplementation:type=MBeanServerDelegate][type=JMX.mbean.registered][message=][mbeanName=org.apache.activemq:type=Broker,brokerName=broker1,endpoint=dynamicProducer,clientId=ID_davsclaus.air-56625-1422981975940-4_7,producerId=ID_davsclaus.air-56625-1422981975940-5_8_1_8]
> WARN  | ActiveMQ Transport: tcp:///127.0.0.1:56626@31316 | JMX
> notification: 
> javax.management.MBeanServerNotification[source=JMImplementation:type=MBeanServerDelegate][type=JMX.mbean.registered][message=][mbeanName=org.apache.activemq:type=Broker,brokerName=broker1,endpoint=dynamicProducer,clientId=ID_davsclaus.air-56625-1422981975940-4_8,producerId=ID_davsclaus.air-56625-1422981975940-5_1_1_8]
> WARN  | ActiveMQ Transport: tcp:///127.0.0.1:56628@31316 | JMX
> notification: 
> javax.management.MBeanServerNotification[source=JMImplementation:type=MBeanServerDelegate][type=JMX.mbean.re

Re: [VOTE] Apache ActiveMQ 5.11.0 (rc3)

[Jean-Baptiste Onofré]

+1 (non binding)

Regards
JB

On 01/30/2015 03:00 PM, Gary Tully wrote:

Hi folks,

I've just cut a third release candidate for the long-awaited 5.11.0 release.
This release has more than 120 bug fixes and improvements.

-note-
this candidate includes the fix for the 'reliably' broken test case from rc2
however there can be no expectation of a 'reliable' full test run from
mvn install.
I have raised https://issues.apache.org/jira/browse/AMQ-5552 to address that.
I think a resolution to that issue would address all of the
disapproving commentary on the rc2 vote. If you voted -1 last time
round, please chime in on AMQ-5552.
-end note-

Could you please review the artifacts and vote?

The list of resolved issues is here:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210&version=12324951

You can get binary distributions here:
https://repository.apache.org/content/repositories/orgapacheactivemq-1016/org/apache/activemq/apache-activemq/5.11.0/

Source archives are here:
https://repository.apache.org/content/repositories/orgapacheactivemq-1016/org/apache/activemq/activemq-parent/5.11.0/

Maven2 repository is at:
https://repository.apache.org/content/repositories/orgapacheactivemq-1016/

Source tag:
https://git-wip-us.apache.org/repos/asf?p=activemq.git;a=tag;h=66bd5da9405765ddbc950b4f1c5a6ef6195207e5

The vote will remain open for 72 hours.

[ ] +1  approve the release as Apache ActiveMQ 5.11.0
[ ] +0  no opinion
[ ] -1  disapprove (and reason why)


Here's my +1

Regards,
Gary.



--
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com

Re: [VOTE] Apache ActiveMQ 5.11.0 (rc3)

[Claus Ibsen]

Hi

I logged a ticket about this. Not sure what the title it, but I
suspect its related to the activemq-pool.

I found an easier way of reproducing it using the camel-example-management.
https://issues.apache.org/jira/browse/AMQ-5564

Just change the AMQ version in its pom.xml



org.apache.camel.example.management.*

org.apache.activemq.xbean,org.apache.activemq.broker,org.apache.activemq.pool
  
  
  5.11.0


I attached screenshot of 5.10.0 working and 5.10.1 and 5.11.0 failing.
So as the issue is introduced in 5.10.1 that narrows down what code
change caused this, as it must be a commit in that patch branch.

On Wed, Feb 4, 2015 at 10:24 AM, Claus Ibsen  wrote:
> Hi
>
> Just upgraded Camel master branch to 5.11.0 and you can reproduce the
> issue there also
>
> cd examples/camel-example-management
> mvn clean install camel:run
>
> Connect to the JVM using jconsole.
>
> Notice the AcitveMQ tree under dynamic producers keeps adding new
> mbeans, until your JVM runs out of memory.
>
> On Wed, Feb 4, 2015 at 10:11 AM, Claus Ibsen  wrote:
>> Hi
>>
>> I have done as Arthur suggested to dump the stacktrace, and also with
>> Gary's turn on|off the anonoymous producers.
>>
>> I posted output from console as 2 gists
>>
>> https://gist.github.com/davsclaus/b5fbb1287d383107e599
>>
>> https://gist.github.com/davsclaus/0472ed0ab85ec5af9e79
>>
>> On Wed, Feb 4, 2015 at 12:05 AM, Gary Tully  wrote:
>>> claus, that looks like producers are not being cached - I thought the
>>> culprit may be https://issues.apache.org/jira/browse/AMQ-4968 but that
>>> would have made 5.10. In any event, can you set
>>> useAnonymousProducers=false on your activemq pooled connection
>>> factory.
>>>
>>> On 3 February 2015 at 16:55, Claus Ibsen  wrote:
 Hi

 Just wanted to say I have stumbled on a weird issue with the 5.11.0
 release which I had trouble reproducing consistently.

 The issue is subtle causing AMQ to continuously re-create dynamic
 producer mbeans in the JMX tree. This is using a Camel spring app with
 the AMQ connection pool.

 Though just now I was able to see that 5.10.0 was stable and the
 mbeans didnt re-create continusly, but with 5.11.0 that happens (with
 no other change that switching from 5.10.0 to 5.11.0)

 Though I think that issue could go unnoticed as the jmx tree looks
 okay, but you may discover a flicker in jconsole when it redraws, and
 then there is a little CPU time to create/destroy the mbeans.

 I noticed this with hawtio as it also "flicker" when the jmx tree is
 redrawn. And therefore was using hawtio to track down the issue.


 I enabled a WARN logging when a mbean was registerede/unregistered and
 you can see

 WARN  | ActiveMQ Transport: tcp:///127.0.0.1:56632@31316 | JMX
 notification: 
 javax.management.MBeanServerNotification[source=JMImplementation:type=MBeanServerDelegate][type=JMX.mbean.registered][message=][mbeanName=org.apache.activemq:type=Broker,brokerName=broker1,endpoint=dynamicProducer,clientId=ID_davsclaus.air-56625-1422981975940-4_5,producerId=ID_davsclaus.air-56625-1422981975940-5_6_1_8]
 WARN  | ActiveMQ Transport: tcp:///127.0.0.1:56633@31316 | JMX
 notification: 
 javax.management.MBeanServerNotification[source=JMImplementation:type=MBeanServerDelegate][type=JMX.mbean.registered][message=][mbeanName=org.apache.activemq:type=Broker,brokerName=broker1,endpoint=dynamicProducer,clientId=ID_davsclaus.air-56625-1422981975940-4_6,producerId=ID_davsclaus.air-56625-1422981975940-5_7_1_8]
 WARN  | ActiveMQ Transport: tcp:///127.0.0.1:56634@31316 | JMX
 notification: 
 javax.management.MBeanServerNotification[source=JMImplementation:type=MBeanServerDelegate][type=JMX.mbean.registered][message=][mbeanName=org.apache.activemq:type=Broker,brokerName=broker1,endpoint=dynamicProducer,clientId=ID_davsclaus.air-56625-1422981975940-4_7,producerId=ID_davsclaus.air-56625-1422981975940-5_8_1_8]
 WARN  | ActiveMQ Transport: tcp:///127.0.0.1:56626@31316 | JMX
 notification: 
 javax.management.MBeanServerNotification[source=JMImplementation:type=MBeanServerDelegate][type=JMX.mbean.registered][message=][mbeanName=org.apache.activemq:type=Broker,brokerName=broker1,endpoint=dynamicProducer,clientId=ID_davsclaus.air-56625-1422981975940-4_8,producerId=ID_davsclaus.air-56625-1422981975940-5_1_1_8]
 WARN  | ActiveMQ Transport: tcp:///127.0.0.1:56628@31316 | JMX
 notification: 
 javax.management.MBeanServerNotification[source=JMImplementation:type=MBeanServerDelegate][type=JMX.mbean.registered][message=][mbeanName=org.apache.activemq:type=Broker,brokerName=broker1,endpoint=dynamicProducer,clientId=ID_davsclaus.air-56625-1422981975940-4_1,producerId=ID_davsclaus.air-56625-1422981975940-5_2_11_8]
 WARN  | ActiveMQ Transport: tcp:///127.0.0.1:56629@31316 | JMX
 notification: 
 javax.management.MBeanServerNotification

Re: [VOTE] Apache ActiveMQ 5.11.0 (rc3)

[Claus Ibsen]

Hi

Just upgraded Camel master branch to 5.11.0 and you can reproduce the
issue there also

cd examples/camel-example-management
mvn clean install camel:run

Connect to the JVM using jconsole.

Notice the AcitveMQ tree under dynamic producers keeps adding new
mbeans, until your JVM runs out of memory.

On Wed, Feb 4, 2015 at 10:11 AM, Claus Ibsen  wrote:
> Hi
>
> I have done as Arthur suggested to dump the stacktrace, and also with
> Gary's turn on|off the anonoymous producers.
>
> I posted output from console as 2 gists
>
> https://gist.github.com/davsclaus/b5fbb1287d383107e599
>
> https://gist.github.com/davsclaus/0472ed0ab85ec5af9e79
>
> On Wed, Feb 4, 2015 at 12:05 AM, Gary Tully  wrote:
>> claus, that looks like producers are not being cached - I thought the
>> culprit may be https://issues.apache.org/jira/browse/AMQ-4968 but that
>> would have made 5.10. In any event, can you set
>> useAnonymousProducers=false on your activemq pooled connection
>> factory.
>>
>> On 3 February 2015 at 16:55, Claus Ibsen  wrote:
>>> Hi
>>>
>>> Just wanted to say I have stumbled on a weird issue with the 5.11.0
>>> release which I had trouble reproducing consistently.
>>>
>>> The issue is subtle causing AMQ to continuously re-create dynamic
>>> producer mbeans in the JMX tree. This is using a Camel spring app with
>>> the AMQ connection pool.
>>>
>>> Though just now I was able to see that 5.10.0 was stable and the
>>> mbeans didnt re-create continusly, but with 5.11.0 that happens (with
>>> no other change that switching from 5.10.0 to 5.11.0)
>>>
>>> Though I think that issue could go unnoticed as the jmx tree looks
>>> okay, but you may discover a flicker in jconsole when it redraws, and
>>> then there is a little CPU time to create/destroy the mbeans.
>>>
>>> I noticed this with hawtio as it also "flicker" when the jmx tree is
>>> redrawn. And therefore was using hawtio to track down the issue.
>>>
>>>
>>> I enabled a WARN logging when a mbean was registerede/unregistered and
>>> you can see
>>>
>>> WARN  | ActiveMQ Transport: tcp:///127.0.0.1:56632@31316 | JMX
>>> notification: 
>>> javax.management.MBeanServerNotification[source=JMImplementation:type=MBeanServerDelegate][type=JMX.mbean.registered][message=][mbeanName=org.apache.activemq:type=Broker,brokerName=broker1,endpoint=dynamicProducer,clientId=ID_davsclaus.air-56625-1422981975940-4_5,producerId=ID_davsclaus.air-56625-1422981975940-5_6_1_8]
>>> WARN  | ActiveMQ Transport: tcp:///127.0.0.1:56633@31316 | JMX
>>> notification: 
>>> javax.management.MBeanServerNotification[source=JMImplementation:type=MBeanServerDelegate][type=JMX.mbean.registered][message=][mbeanName=org.apache.activemq:type=Broker,brokerName=broker1,endpoint=dynamicProducer,clientId=ID_davsclaus.air-56625-1422981975940-4_6,producerId=ID_davsclaus.air-56625-1422981975940-5_7_1_8]
>>> WARN  | ActiveMQ Transport: tcp:///127.0.0.1:56634@31316 | JMX
>>> notification: 
>>> javax.management.MBeanServerNotification[source=JMImplementation:type=MBeanServerDelegate][type=JMX.mbean.registered][message=][mbeanName=org.apache.activemq:type=Broker,brokerName=broker1,endpoint=dynamicProducer,clientId=ID_davsclaus.air-56625-1422981975940-4_7,producerId=ID_davsclaus.air-56625-1422981975940-5_8_1_8]
>>> WARN  | ActiveMQ Transport: tcp:///127.0.0.1:56626@31316 | JMX
>>> notification: 
>>> javax.management.MBeanServerNotification[source=JMImplementation:type=MBeanServerDelegate][type=JMX.mbean.registered][message=][mbeanName=org.apache.activemq:type=Broker,brokerName=broker1,endpoint=dynamicProducer,clientId=ID_davsclaus.air-56625-1422981975940-4_8,producerId=ID_davsclaus.air-56625-1422981975940-5_1_1_8]
>>> WARN  | ActiveMQ Transport: tcp:///127.0.0.1:56628@31316 | JMX
>>> notification: 
>>> javax.management.MBeanServerNotification[source=JMImplementation:type=MBeanServerDelegate][type=JMX.mbean.registered][message=][mbeanName=org.apache.activemq:type=Broker,brokerName=broker1,endpoint=dynamicProducer,clientId=ID_davsclaus.air-56625-1422981975940-4_1,producerId=ID_davsclaus.air-56625-1422981975940-5_2_11_8]
>>> WARN  | ActiveMQ Transport: tcp:///127.0.0.1:56629@31316 | JMX
>>> notification: 
>>> javax.management.MBeanServerNotification[source=JMImplementation:type=MBeanServerDelegate][type=JMX.mbean.registered][message=][mbeanName=org.apache.activemq:type=Broker,brokerName=broker1,endpoint=dynamicProducer,clientId=ID_davsclaus.air-56625-1422981975940-4_2,producerId=ID_davsclaus.air-56625-1422981975940-5_3_1_9]
>>>
>>>
>>>
>>> Just wanted to share this and say there is maybe a glitch in this release.
>>>
>>> As I discovered this using hawtio, I created a branch with my current
>>> work code that reproduces the issue.
>>>
>>> https://github.com/hawtio/hawtio/tree/amq511bug
>>>
>>> The commit has instructions how to reproduce.
>>> https://github.com/hawtio/hawtio/commit/9162529299059d25e1e6b7c7d7e0be45ee4556b4
>>>
>>> As I was a hunt in the hay-stack I had to disable various stuff in the
>>> hawtio spring xml file w

Re: [VOTE] Apache ActiveMQ 5.11.0 (rc3)

[Claus Ibsen]

Hi

I have done as Arthur suggested to dump the stacktrace, and also with
Gary's turn on|off the anonoymous producers.

I posted output from console as 2 gists

https://gist.github.com/davsclaus/b5fbb1287d383107e599

https://gist.github.com/davsclaus/0472ed0ab85ec5af9e79

On Wed, Feb 4, 2015 at 12:05 AM, Gary Tully  wrote:
> claus, that looks like producers are not being cached - I thought the
> culprit may be https://issues.apache.org/jira/browse/AMQ-4968 but that
> would have made 5.10. In any event, can you set
> useAnonymousProducers=false on your activemq pooled connection
> factory.
>
> On 3 February 2015 at 16:55, Claus Ibsen  wrote:
>> Hi
>>
>> Just wanted to say I have stumbled on a weird issue with the 5.11.0
>> release which I had trouble reproducing consistently.
>>
>> The issue is subtle causing AMQ to continuously re-create dynamic
>> producer mbeans in the JMX tree. This is using a Camel spring app with
>> the AMQ connection pool.
>>
>> Though just now I was able to see that 5.10.0 was stable and the
>> mbeans didnt re-create continusly, but with 5.11.0 that happens (with
>> no other change that switching from 5.10.0 to 5.11.0)
>>
>> Though I think that issue could go unnoticed as the jmx tree looks
>> okay, but you may discover a flicker in jconsole when it redraws, and
>> then there is a little CPU time to create/destroy the mbeans.
>>
>> I noticed this with hawtio as it also "flicker" when the jmx tree is
>> redrawn. And therefore was using hawtio to track down the issue.
>>
>>
>> I enabled a WARN logging when a mbean was registerede/unregistered and
>> you can see
>>
>> WARN  | ActiveMQ Transport: tcp:///127.0.0.1:56632@31316 | JMX
>> notification: 
>> javax.management.MBeanServerNotification[source=JMImplementation:type=MBeanServerDelegate][type=JMX.mbean.registered][message=][mbeanName=org.apache.activemq:type=Broker,brokerName=broker1,endpoint=dynamicProducer,clientId=ID_davsclaus.air-56625-1422981975940-4_5,producerId=ID_davsclaus.air-56625-1422981975940-5_6_1_8]
>> WARN  | ActiveMQ Transport: tcp:///127.0.0.1:56633@31316 | JMX
>> notification: 
>> javax.management.MBeanServerNotification[source=JMImplementation:type=MBeanServerDelegate][type=JMX.mbean.registered][message=][mbeanName=org.apache.activemq:type=Broker,brokerName=broker1,endpoint=dynamicProducer,clientId=ID_davsclaus.air-56625-1422981975940-4_6,producerId=ID_davsclaus.air-56625-1422981975940-5_7_1_8]
>> WARN  | ActiveMQ Transport: tcp:///127.0.0.1:56634@31316 | JMX
>> notification: 
>> javax.management.MBeanServerNotification[source=JMImplementation:type=MBeanServerDelegate][type=JMX.mbean.registered][message=][mbeanName=org.apache.activemq:type=Broker,brokerName=broker1,endpoint=dynamicProducer,clientId=ID_davsclaus.air-56625-1422981975940-4_7,producerId=ID_davsclaus.air-56625-1422981975940-5_8_1_8]
>> WARN  | ActiveMQ Transport: tcp:///127.0.0.1:56626@31316 | JMX
>> notification: 
>> javax.management.MBeanServerNotification[source=JMImplementation:type=MBeanServerDelegate][type=JMX.mbean.registered][message=][mbeanName=org.apache.activemq:type=Broker,brokerName=broker1,endpoint=dynamicProducer,clientId=ID_davsclaus.air-56625-1422981975940-4_8,producerId=ID_davsclaus.air-56625-1422981975940-5_1_1_8]
>> WARN  | ActiveMQ Transport: tcp:///127.0.0.1:56628@31316 | JMX
>> notification: 
>> javax.management.MBeanServerNotification[source=JMImplementation:type=MBeanServerDelegate][type=JMX.mbean.registered][message=][mbeanName=org.apache.activemq:type=Broker,brokerName=broker1,endpoint=dynamicProducer,clientId=ID_davsclaus.air-56625-1422981975940-4_1,producerId=ID_davsclaus.air-56625-1422981975940-5_2_11_8]
>> WARN  | ActiveMQ Transport: tcp:///127.0.0.1:56629@31316 | JMX
>> notification: 
>> javax.management.MBeanServerNotification[source=JMImplementation:type=MBeanServerDelegate][type=JMX.mbean.registered][message=][mbeanName=org.apache.activemq:type=Broker,brokerName=broker1,endpoint=dynamicProducer,clientId=ID_davsclaus.air-56625-1422981975940-4_2,producerId=ID_davsclaus.air-56625-1422981975940-5_3_1_9]
>>
>>
>>
>> Just wanted to share this and say there is maybe a glitch in this release.
>>
>> As I discovered this using hawtio, I created a branch with my current
>> work code that reproduces the issue.
>>
>> https://github.com/hawtio/hawtio/tree/amq511bug
>>
>> The commit has instructions how to reproduce.
>> https://github.com/hawtio/hawtio/commit/9162529299059d25e1e6b7c7d7e0be45ee4556b4
>>
>> As I was a hunt in the hay-stack I had to disable various stuff in the
>> hawtio spring xml file where we setup stuff we use for testing and
>> developing, hence the removal of the NOB, and some Camel routes and
>> whatnot.
>>
>> On Fri, Jan 30, 2015 at 3:00 PM, Gary Tully  wrote:
>>> Hi folks,
>>>
>>> I've just cut a third release candidate for the long-awaited 5.11.0 release.
>>> This release has more than 120 bug fixes and improvements.
>>>
>>> -note-
>>> this candidate includes the fix for the 'reliably' broken test case from rc

Re: [VOTE] Apache ActiveMQ 5.11.0 (rc3)

[Gary Tully]

claus, that looks like producers are not being cached - I thought the
culprit may be https://issues.apache.org/jira/browse/AMQ-4968 but that
would have made 5.10. In any event, can you set
useAnonymousProducers=false on your activemq pooled connection
factory.

On 3 February 2015 at 16:55, Claus Ibsen  wrote:
> Hi
>
> Just wanted to say I have stumbled on a weird issue with the 5.11.0
> release which I had trouble reproducing consistently.
>
> The issue is subtle causing AMQ to continuously re-create dynamic
> producer mbeans in the JMX tree. This is using a Camel spring app with
> the AMQ connection pool.
>
> Though just now I was able to see that 5.10.0 was stable and the
> mbeans didnt re-create continusly, but with 5.11.0 that happens (with
> no other change that switching from 5.10.0 to 5.11.0)
>
> Though I think that issue could go unnoticed as the jmx tree looks
> okay, but you may discover a flicker in jconsole when it redraws, and
> then there is a little CPU time to create/destroy the mbeans.
>
> I noticed this with hawtio as it also "flicker" when the jmx tree is
> redrawn. And therefore was using hawtio to track down the issue.
>
>
> I enabled a WARN logging when a mbean was registerede/unregistered and
> you can see
>
> WARN  | ActiveMQ Transport: tcp:///127.0.0.1:56632@31316 | JMX
> notification: 
> javax.management.MBeanServerNotification[source=JMImplementation:type=MBeanServerDelegate][type=JMX.mbean.registered][message=][mbeanName=org.apache.activemq:type=Broker,brokerName=broker1,endpoint=dynamicProducer,clientId=ID_davsclaus.air-56625-1422981975940-4_5,producerId=ID_davsclaus.air-56625-1422981975940-5_6_1_8]
> WARN  | ActiveMQ Transport: tcp:///127.0.0.1:56633@31316 | JMX
> notification: 
> javax.management.MBeanServerNotification[source=JMImplementation:type=MBeanServerDelegate][type=JMX.mbean.registered][message=][mbeanName=org.apache.activemq:type=Broker,brokerName=broker1,endpoint=dynamicProducer,clientId=ID_davsclaus.air-56625-1422981975940-4_6,producerId=ID_davsclaus.air-56625-1422981975940-5_7_1_8]
> WARN  | ActiveMQ Transport: tcp:///127.0.0.1:56634@31316 | JMX
> notification: 
> javax.management.MBeanServerNotification[source=JMImplementation:type=MBeanServerDelegate][type=JMX.mbean.registered][message=][mbeanName=org.apache.activemq:type=Broker,brokerName=broker1,endpoint=dynamicProducer,clientId=ID_davsclaus.air-56625-1422981975940-4_7,producerId=ID_davsclaus.air-56625-1422981975940-5_8_1_8]
> WARN  | ActiveMQ Transport: tcp:///127.0.0.1:56626@31316 | JMX
> notification: 
> javax.management.MBeanServerNotification[source=JMImplementation:type=MBeanServerDelegate][type=JMX.mbean.registered][message=][mbeanName=org.apache.activemq:type=Broker,brokerName=broker1,endpoint=dynamicProducer,clientId=ID_davsclaus.air-56625-1422981975940-4_8,producerId=ID_davsclaus.air-56625-1422981975940-5_1_1_8]
> WARN  | ActiveMQ Transport: tcp:///127.0.0.1:56628@31316 | JMX
> notification: 
> javax.management.MBeanServerNotification[source=JMImplementation:type=MBeanServerDelegate][type=JMX.mbean.registered][message=][mbeanName=org.apache.activemq:type=Broker,brokerName=broker1,endpoint=dynamicProducer,clientId=ID_davsclaus.air-56625-1422981975940-4_1,producerId=ID_davsclaus.air-56625-1422981975940-5_2_11_8]
> WARN  | ActiveMQ Transport: tcp:///127.0.0.1:56629@31316 | JMX
> notification: 
> javax.management.MBeanServerNotification[source=JMImplementation:type=MBeanServerDelegate][type=JMX.mbean.registered][message=][mbeanName=org.apache.activemq:type=Broker,brokerName=broker1,endpoint=dynamicProducer,clientId=ID_davsclaus.air-56625-1422981975940-4_2,producerId=ID_davsclaus.air-56625-1422981975940-5_3_1_9]
>
>
>
> Just wanted to share this and say there is maybe a glitch in this release.
>
> As I discovered this using hawtio, I created a branch with my current
> work code that reproduces the issue.
>
> https://github.com/hawtio/hawtio/tree/amq511bug
>
> The commit has instructions how to reproduce.
> https://github.com/hawtio/hawtio/commit/9162529299059d25e1e6b7c7d7e0be45ee4556b4
>
> As I was a hunt in the hay-stack I had to disable various stuff in the
> hawtio spring xml file where we setup stuff we use for testing and
> developing, hence the removal of the NOB, and some Camel routes and
> whatnot.
>
> On Fri, Jan 30, 2015 at 3:00 PM, Gary Tully  wrote:
>> Hi folks,
>>
>> I've just cut a third release candidate for the long-awaited 5.11.0 release.
>> This release has more than 120 bug fixes and improvements.
>>
>> -note-
>> this candidate includes the fix for the 'reliably' broken test case from rc2
>> however there can be no expectation of a 'reliable' full test run from
>> mvn install.
>> I have raised https://issues.apache.org/jira/browse/AMQ-5552 to address that.
>> I think a resolution to that issue would address all of the
>> disapproving commentary on the rc2 vote. If you voted -1 last time
>> round, please chime in on AMQ-5552.
>> -end note-
>>
>> Could you please review the artifacts and

Re: [VOTE] Apache ActiveMQ 5.11.0 (rc3)

[artnaseef]

Hey Claus - can you try dumping the stack trace when the MBeans are created
and removed to see the internal cause?  I'm thinking along the following
lines:

LOG.warn(..., new Exception())




--
View this message in context: 
http://activemq.2283324.n4.nabble.com/VOTE-Apache-ActiveMQ-5-11-0-rc3-tp4690743p4690944.html
Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.

Re: [VOTE] Apache ActiveMQ 5.11.0 (rc3)

[Claus Ibsen]

Hi

Just wanted to say I have stumbled on a weird issue with the 5.11.0
release which I had trouble reproducing consistently.

The issue is subtle causing AMQ to continuously re-create dynamic
producer mbeans in the JMX tree. This is using a Camel spring app with
the AMQ connection pool.

Though just now I was able to see that 5.10.0 was stable and the
mbeans didnt re-create continusly, but with 5.11.0 that happens (with
no other change that switching from 5.10.0 to 5.11.0)

Though I think that issue could go unnoticed as the jmx tree looks
okay, but you may discover a flicker in jconsole when it redraws, and
then there is a little CPU time to create/destroy the mbeans.

I noticed this with hawtio as it also "flicker" when the jmx tree is
redrawn. And therefore was using hawtio to track down the issue.


I enabled a WARN logging when a mbean was registerede/unregistered and
you can see

WARN  | ActiveMQ Transport: tcp:///127.0.0.1:56632@31316 | JMX
notification: 
javax.management.MBeanServerNotification[source=JMImplementation:type=MBeanServerDelegate][type=JMX.mbean.registered][message=][mbeanName=org.apache.activemq:type=Broker,brokerName=broker1,endpoint=dynamicProducer,clientId=ID_davsclaus.air-56625-1422981975940-4_5,producerId=ID_davsclaus.air-56625-1422981975940-5_6_1_8]
WARN  | ActiveMQ Transport: tcp:///127.0.0.1:56633@31316 | JMX
notification: 
javax.management.MBeanServerNotification[source=JMImplementation:type=MBeanServerDelegate][type=JMX.mbean.registered][message=][mbeanName=org.apache.activemq:type=Broker,brokerName=broker1,endpoint=dynamicProducer,clientId=ID_davsclaus.air-56625-1422981975940-4_6,producerId=ID_davsclaus.air-56625-1422981975940-5_7_1_8]
WARN  | ActiveMQ Transport: tcp:///127.0.0.1:56634@31316 | JMX
notification: 
javax.management.MBeanServerNotification[source=JMImplementation:type=MBeanServerDelegate][type=JMX.mbean.registered][message=][mbeanName=org.apache.activemq:type=Broker,brokerName=broker1,endpoint=dynamicProducer,clientId=ID_davsclaus.air-56625-1422981975940-4_7,producerId=ID_davsclaus.air-56625-1422981975940-5_8_1_8]
WARN  | ActiveMQ Transport: tcp:///127.0.0.1:56626@31316 | JMX
notification: 
javax.management.MBeanServerNotification[source=JMImplementation:type=MBeanServerDelegate][type=JMX.mbean.registered][message=][mbeanName=org.apache.activemq:type=Broker,brokerName=broker1,endpoint=dynamicProducer,clientId=ID_davsclaus.air-56625-1422981975940-4_8,producerId=ID_davsclaus.air-56625-1422981975940-5_1_1_8]
WARN  | ActiveMQ Transport: tcp:///127.0.0.1:56628@31316 | JMX
notification: 
javax.management.MBeanServerNotification[source=JMImplementation:type=MBeanServerDelegate][type=JMX.mbean.registered][message=][mbeanName=org.apache.activemq:type=Broker,brokerName=broker1,endpoint=dynamicProducer,clientId=ID_davsclaus.air-56625-1422981975940-4_1,producerId=ID_davsclaus.air-56625-1422981975940-5_2_11_8]
WARN  | ActiveMQ Transport: tcp:///127.0.0.1:56629@31316 | JMX
notification: 
javax.management.MBeanServerNotification[source=JMImplementation:type=MBeanServerDelegate][type=JMX.mbean.registered][message=][mbeanName=org.apache.activemq:type=Broker,brokerName=broker1,endpoint=dynamicProducer,clientId=ID_davsclaus.air-56625-1422981975940-4_2,producerId=ID_davsclaus.air-56625-1422981975940-5_3_1_9]



Just wanted to share this and say there is maybe a glitch in this release.

As I discovered this using hawtio, I created a branch with my current
work code that reproduces the issue.

https://github.com/hawtio/hawtio/tree/amq511bug

The commit has instructions how to reproduce.
https://github.com/hawtio/hawtio/commit/9162529299059d25e1e6b7c7d7e0be45ee4556b4

As I was a hunt in the hay-stack I had to disable various stuff in the
hawtio spring xml file where we setup stuff we use for testing and
developing, hence the removal of the NOB, and some Camel routes and
whatnot.

On Fri, Jan 30, 2015 at 3:00 PM, Gary Tully  wrote:
> Hi folks,
>
> I've just cut a third release candidate for the long-awaited 5.11.0 release.
> This release has more than 120 bug fixes and improvements.
>
> -note-
> this candidate includes the fix for the 'reliably' broken test case from rc2
> however there can be no expectation of a 'reliable' full test run from
> mvn install.
> I have raised https://issues.apache.org/jira/browse/AMQ-5552 to address that.
> I think a resolution to that issue would address all of the
> disapproving commentary on the rc2 vote. If you voted -1 last time
> round, please chime in on AMQ-5552.
> -end note-
>
> Could you please review the artifacts and vote?
>
> The list of resolved issues is here:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210&version=12324951
>
> You can get binary distributions here:
> https://repository.apache.org/content/repositories/orgapacheactivemq-1016/org/apache/activemq/apache-activemq/5.11.0/
>
> Source archives are here:
> https://repository.apache.org/content/repositories/orgapacheactivemq-1016/org/apache/activemq/act

Re: [VOTE] Apache ActiveMQ 5.11.0 (rc3)

[Daniel Kulp]

+1

Looks good.

Dan



> On Jan 30, 2015, at 9:00 AM, Gary Tully  wrote:
> 
> Hi folks,
> 
> I've just cut a third release candidate for the long-awaited 5.11.0 release.
> This release has more than 120 bug fixes and improvements.
> 
> -note-
> this candidate includes the fix for the 'reliably' broken test case from rc2
> however there can be no expectation of a 'reliable' full test run from
> mvn install.
> I have raised https://issues.apache.org/jira/browse/AMQ-5552 to address that.
> I think a resolution to that issue would address all of the
> disapproving commentary on the rc2 vote. If you voted -1 last time
> round, please chime in on AMQ-5552.
> -end note-
> 
> Could you please review the artifacts and vote?
> 
> The list of resolved issues is here:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210&version=12324951
> 
> You can get binary distributions here:
> https://repository.apache.org/content/repositories/orgapacheactivemq-1016/org/apache/activemq/apache-activemq/5.11.0/
> 
> Source archives are here:
> https://repository.apache.org/content/repositories/orgapacheactivemq-1016/org/apache/activemq/activemq-parent/5.11.0/
> 
> Maven2 repository is at:
> https://repository.apache.org/content/repositories/orgapacheactivemq-1016/
> 
> Source tag:
> https://git-wip-us.apache.org/repos/asf?p=activemq.git;a=tag;h=66bd5da9405765ddbc950b4f1c5a6ef6195207e5
> 
> The vote will remain open for 72 hours.
> 
> [ ] +1  approve the release as Apache ActiveMQ 5.11.0
> [ ] +0  no opinion
> [ ] -1  disapprove (and reason why)
> 
> 
> Here's my +1
> 
> Regards,
> Gary.

-- 
Daniel Kulp
dk...@apache.org - http://dankulp.com/blog
Talend Community Coder - http://coders.talend.com

Re: [VOTE] Apache ActiveMQ 5.11.0 (rc3)

[Rob Davies]

+1


Gary Tully 
30 January 2015 14:00
Hi folks,

I've just cut a third release candidate for the long-awaited 5.11.0 
release.

This release has more than 120 bug fixes and improvements.

-note-
this candidate includes the fix for the 'reliably' broken test case 
from rc2

however there can be no expectation of a 'reliable' full test run from
mvn install.
I have raised https://issues.apache.org/jira/browse/AMQ-5552 to 
address that.

I think a resolution to that issue would address all of the
disapproving commentary on the rc2 vote. If you voted -1 last time
round, please chime in on AMQ-5552.
-end note-

Could you please review the artifacts and vote?

The list of resolved issues is here:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210&version=12324951

You can get binary distributions here:
https://repository.apache.org/content/repositories/orgapacheactivemq-1016/org/apache/activemq/apache-activemq/5.11.0/

Source archives are here:
https://repository.apache.org/content/repositories/orgapacheactivemq-1016/org/apache/activemq/activemq-parent/5.11.0/

Maven2 repository is at:
https://repository.apache.org/content/repositories/orgapacheactivemq-1016/

Source tag:
https://git-wip-us.apache.org/repos/asf?p=activemq.git;a=tag;h=66bd5da9405765ddbc950b4f1c5a6ef6195207e5

The vote will remain open for 72 hours.

[ ] +1 approve the release as Apache ActiveMQ 5.11.0
[ ] +0 no opinion
[ ] -1 disapprove (and reason why)


Here's my +1

Regards,
Gary.

Re: [VOTE] Apache ActiveMQ 5.11.0 (rc3)

[Jim Gomes]

+1

On Mon, Feb 2, 2015, 8:11 AM Hadrian Zbarcea  wrote:

> +1 (binding)
>
> * Sigs ok
> * Legal ok (almost)
>- a bunch of Copyright notices pointing to 2014 or 2013 (need to
> cleanup)
> * Builds from source ok (almost)
>
> There is one consistent failure in activemq-karaf-itest, however test
> does pass when ran individually. No product defect, but should be
> addressed.
> ActiveMQAMQPBrokerFeatureTest>ActiveMQBrokerFeatureTest.test:66->
> AbstractJmsFeatureTest.produceMessage:67->getConnection:53
> » ClassNotFound
>
>
> All in all, quite impressive. Very solid release, awesome work.
>
> Thanks Gary,
> Hadrian
>
>
> On 01/30/2015 09:00 AM, Gary Tully wrote:
> > Hi folks,
> >
> > I've just cut a third release candidate for the long-awaited 5.11.0
> release.
> > This release has more than 120 bug fixes and improvements.
> >
> > -note-
> > this candidate includes the fix for the 'reliably' broken test case from
> rc2
> > however there can be no expectation of a 'reliable' full test run from
> > mvn install.
> > I have raised https://issues.apache.org/jira/browse/AMQ-5552 to address
> that.
> > I think a resolution to that issue would address all of the
> > disapproving commentary on the rc2 vote. If you voted -1 last time
> > round, please chime in on AMQ-5552.
> > -end note-
> >
> > Could you please review the artifacts and vote?
> >
> > The list of resolved issues is here:
> > https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> projectId=12311210&version=12324951
> >
> > You can get binary distributions here:
> > https://repository.apache.org/content/repositories/
> orgapacheactivemq-1016/org/apache/activemq/apache-activemq/5.11.0/
> >
> > Source archives are here:
> > https://repository.apache.org/content/repositories/
> orgapacheactivemq-1016/org/apache/activemq/activemq-parent/5.11.0/
> >
> > Maven2 repository is at:
> > https://repository.apache.org/content/repositories/
> orgapacheactivemq-1016/
> >
> > Source tag:
> > https://git-wip-us.apache.org/repos/asf?p=activemq.git;a=tag;h=
> 66bd5da9405765ddbc950b4f1c5a6ef6195207e5
> >
> > The vote will remain open for 72 hours.
> >
> > [ ] +1  approve the release as Apache ActiveMQ 5.11.0
> > [ ] +0  no opinion
> > [ ] -1  disapprove (and reason why)
> >
> >
> > Here's my +1
> >
> > Regards,
> > Gary.
>
>

Re: [VOTE] Apache ActiveMQ 5.11.0 (rc3)

[Hadrian Zbarcea]

+1 (binding)

* Sigs ok
* Legal ok (almost)
  - a bunch of Copyright notices pointing to 2014 or 2013 (need to cleanup)
* Builds from source ok (almost)

There is one consistent failure in activemq-karaf-itest, however test 
does pass when ran individually. No product defect, but should be addressed.
ActiveMQAMQPBrokerFeatureTest>ActiveMQBrokerFeatureTest.test:66->AbstractJmsFeatureTest.produceMessage:67->getConnection:53 
» ClassNotFound



All in all, quite impressive. Very solid release, awesome work.

Thanks Gary,
Hadrian


On 01/30/2015 09:00 AM, Gary Tully wrote:

Hi folks,

I've just cut a third release candidate for the long-awaited 5.11.0 release.
This release has more than 120 bug fixes and improvements.

-note-
this candidate includes the fix for the 'reliably' broken test case from rc2
however there can be no expectation of a 'reliable' full test run from
mvn install.
I have raised https://issues.apache.org/jira/browse/AMQ-5552 to address that.
I think a resolution to that issue would address all of the
disapproving commentary on the rc2 vote. If you voted -1 last time
round, please chime in on AMQ-5552.
-end note-

Could you please review the artifacts and vote?

The list of resolved issues is here:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210&version=12324951

You can get binary distributions here:
https://repository.apache.org/content/repositories/orgapacheactivemq-1016/org/apache/activemq/apache-activemq/5.11.0/

Source archives are here:
https://repository.apache.org/content/repositories/orgapacheactivemq-1016/org/apache/activemq/activemq-parent/5.11.0/

Maven2 repository is at:
https://repository.apache.org/content/repositories/orgapacheactivemq-1016/

Source tag:
https://git-wip-us.apache.org/repos/asf?p=activemq.git;a=tag;h=66bd5da9405765ddbc950b4f1c5a6ef6195207e5

The vote will remain open for 72 hours.

[ ] +1  approve the release as Apache ActiveMQ 5.11.0
[ ] +0  no opinion
[ ] -1  disapprove (and reason why)


Here's my +1

Regards,
Gary.

Re: [VOTE] Apache ActiveMQ 5.11.0 (rc3)

[Hiram Chirino]

+1

On Fri, Jan 30, 2015 at 9:00 AM, Gary Tully  wrote:
> Hi folks,
>
> I've just cut a third release candidate for the long-awaited 5.11.0 release.
> This release has more than 120 bug fixes and improvements.
>
> -note-
> this candidate includes the fix for the 'reliably' broken test case from rc2
> however there can be no expectation of a 'reliable' full test run from
> mvn install.
> I have raised https://issues.apache.org/jira/browse/AMQ-5552 to address that.
> I think a resolution to that issue would address all of the
> disapproving commentary on the rc2 vote. If you voted -1 last time
> round, please chime in on AMQ-5552.
> -end note-
>
> Could you please review the artifacts and vote?
>
> The list of resolved issues is here:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210&version=12324951
>
> You can get binary distributions here:
> https://repository.apache.org/content/repositories/orgapacheactivemq-1016/org/apache/activemq/apache-activemq/5.11.0/
>
> Source archives are here:
> https://repository.apache.org/content/repositories/orgapacheactivemq-1016/org/apache/activemq/activemq-parent/5.11.0/
>
> Maven2 repository is at:
> https://repository.apache.org/content/repositories/orgapacheactivemq-1016/
>
> Source tag:
> https://git-wip-us.apache.org/repos/asf?p=activemq.git;a=tag;h=66bd5da9405765ddbc950b4f1c5a6ef6195207e5
>
> The vote will remain open for 72 hours.
>
> [ ] +1  approve the release as Apache ActiveMQ 5.11.0
> [ ] +0  no opinion
> [ ] -1  disapprove (and reason why)
>
>
> Here's my +1
>
> Regards,
> Gary.



-- 
Hiram Chirino
Engineering | Red Hat, Inc.
hchir...@redhat.com | fusesource.com | redhat.com
skype: hiramchirino | twitter: @hiramchirino

Re: [VOTE] Apache ActiveMQ 5.11.0 (rc3)

[Robbie Gemmell]

+1 (non-binding)

I gave a kick of the tyres to the broker binaries on linux, verified
the checksums+sigs, built the source release skipping the tests, did a
'quick' subset of the tests (Client, Broker, Stomp, MQTT, JDBC,
LevelDB, AMQP), and verified a dependent project using the build
output.

Robbie

On 30 January 2015 at 14:00, Gary Tully  wrote:
> Hi folks,
>
> I've just cut a third release candidate for the long-awaited 5.11.0 release.
> This release has more than 120 bug fixes and improvements.
>
> -note-
> this candidate includes the fix for the 'reliably' broken test case from rc2
> however there can be no expectation of a 'reliable' full test run from
> mvn install.
> I have raised https://issues.apache.org/jira/browse/AMQ-5552 to address that.
> I think a resolution to that issue would address all of the
> disapproving commentary on the rc2 vote. If you voted -1 last time
> round, please chime in on AMQ-5552.
> -end note-
>
> Could you please review the artifacts and vote?
>
> The list of resolved issues is here:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210&version=12324951
>
> You can get binary distributions here:
> https://repository.apache.org/content/repositories/orgapacheactivemq-1016/org/apache/activemq/apache-activemq/5.11.0/
>
> Source archives are here:
> https://repository.apache.org/content/repositories/orgapacheactivemq-1016/org/apache/activemq/activemq-parent/5.11.0/
>
> Maven2 repository is at:
> https://repository.apache.org/content/repositories/orgapacheactivemq-1016/
>
> Source tag:
> https://git-wip-us.apache.org/repos/asf?p=activemq.git;a=tag;h=66bd5da9405765ddbc950b4f1c5a6ef6195207e5
>
> The vote will remain open for 72 hours.
>
> [ ] +1  approve the release as Apache ActiveMQ 5.11.0
> [ ] +0  no opinion
> [ ] -1  disapprove (and reason why)
>
>
> Here's my +1
>
> Regards,
> Gary.

Re: [VOTE] Apache ActiveMQ 5.11.0 (rc3)

[Dejan Bosanac]

+1

Regards
--
Dejan Bosanac
--
Red Hat, Inc.
dbosa...@redhat.com
Twitter: @dejanb
Blog: http://sensatic.net
ActiveMQ in Action: http://www.manning.com/snyder/

On Sat, Jan 31, 2015 at 8:55 PM, Timothy Bish  wrote:

> +1
>
>
> On 01/30/2015 09:00 AM, Gary Tully wrote:
>
>> Hi folks,
>>
>> I've just cut a third release candidate for the long-awaited 5.11.0
>> release.
>> This release has more than 120 bug fixes and improvements.
>>
>> -note-
>> this candidate includes the fix for the 'reliably' broken test case from
>> rc2
>> however there can be no expectation of a 'reliable' full test run from
>> mvn install.
>> I have raised https://issues.apache.org/jira/browse/AMQ-5552 to address
>> that.
>> I think a resolution to that issue would address all of the
>> disapproving commentary on the rc2 vote. If you voted -1 last time
>> round, please chime in on AMQ-5552.
>> -end note-
>>
>> Could you please review the artifacts and vote?
>>
>> The list of resolved issues is here:
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?
>> projectId=12311210&version=12324951
>>
>> You can get binary distributions here:
>> https://repository.apache.org/content/repositories/
>> orgapacheactivemq-1016/org/apache/activemq/apache-activemq/5.11.0/
>>
>> Source archives are here:
>> https://repository.apache.org/content/repositories/
>> orgapacheactivemq-1016/org/apache/activemq/activemq-parent/5.11.0/
>>
>> Maven2 repository is at:
>> https://repository.apache.org/content/repositories/
>> orgapacheactivemq-1016/
>>
>> Source tag:
>> https://git-wip-us.apache.org/repos/asf?p=activemq.git;a=tag;h=
>> 66bd5da9405765ddbc950b4f1c5a6ef6195207e5
>>
>> The vote will remain open for 72 hours.
>>
>> [ ] +1  approve the release as Apache ActiveMQ 5.11.0
>> [ ] +0  no opinion
>> [ ] -1  disapprove (and reason why)
>>
>>
>> Here's my +1
>>
>> Regards,
>> Gary.
>>
>>
>
> --
> Tim Bish
> Sr Software Engineer | RedHat Inc.
> tim.b...@redhat.com | www.redhat.com
> skype: tabish121 | twitter: @tabish121
> blog: http://timbish.blogspot.com/
>
>

Re: [VOTE] Apache ActiveMQ 5.11.0 (rc3)

[Timothy Bish]

+1

On 01/30/2015 09:00 AM, Gary Tully wrote:

Hi folks,

I've just cut a third release candidate for the long-awaited 5.11.0 release.
This release has more than 120 bug fixes and improvements.

-note-
this candidate includes the fix for the 'reliably' broken test case from rc2
however there can be no expectation of a 'reliable' full test run from
mvn install.
I have raised https://issues.apache.org/jira/browse/AMQ-5552 to address that.
I think a resolution to that issue would address all of the
disapproving commentary on the rc2 vote. If you voted -1 last time
round, please chime in on AMQ-5552.
-end note-

Could you please review the artifacts and vote?

The list of resolved issues is here:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210&version=12324951

You can get binary distributions here:
https://repository.apache.org/content/repositories/orgapacheactivemq-1016/org/apache/activemq/apache-activemq/5.11.0/

Source archives are here:
https://repository.apache.org/content/repositories/orgapacheactivemq-1016/org/apache/activemq/activemq-parent/5.11.0/

Maven2 repository is at:
https://repository.apache.org/content/repositories/orgapacheactivemq-1016/

Source tag:
https://git-wip-us.apache.org/repos/asf?p=activemq.git;a=tag;h=66bd5da9405765ddbc950b4f1c5a6ef6195207e5

The vote will remain open for 72 hours.

[ ] +1  approve the release as Apache ActiveMQ 5.11.0
[ ] +0  no opinion
[ ] -1  disapprove (and reason why)


Here's my +1

Regards,
Gary.




--
Tim Bish
Sr Software Engineer | RedHat Inc.
tim.b...@redhat.com | www.redhat.com
skype: tabish121 | twitter: @tabish121
blog: http://timbish.blogspot.com/

Re: [VOTE] Apache ActiveMQ 5.11.0 (rc3)

[Krzysztof Sobkowiak]

+1 (non-binding)

Regards
Krzysztof

On 30.01.2015 15:00, Gary Tully wrote:
> Hi folks,
>
> I've just cut a third release candidate for the long-awaited 5.11.0 release.
> This release has more than 120 bug fixes and improvements.
>
> -note-
> this candidate includes the fix for the 'reliably' broken test case from rc2
> however there can be no expectation of a 'reliable' full test run from
> mvn install.
> I have raised https://issues.apache.org/jira/browse/AMQ-5552 to address that.
> I think a resolution to that issue would address all of the
> disapproving commentary on the rc2 vote. If you voted -1 last time
> round, please chime in on AMQ-5552.
> -end note-
>
> Could you please review the artifacts and vote?
>
> The list of resolved issues is here:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210&version=12324951
>
> You can get binary distributions here:
> https://repository.apache.org/content/repositories/orgapacheactivemq-1016/org/apache/activemq/apache-activemq/5.11.0/
>
> Source archives are here:
> https://repository.apache.org/content/repositories/orgapacheactivemq-1016/org/apache/activemq/activemq-parent/5.11.0/
>
> Maven2 repository is at:
> https://repository.apache.org/content/repositories/orgapacheactivemq-1016/
>
> Source tag:
> https://git-wip-us.apache.org/repos/asf?p=activemq.git;a=tag;h=66bd5da9405765ddbc950b4f1c5a6ef6195207e5
>
> The vote will remain open for 72 hours.
>
> [ ] +1  approve the release as Apache ActiveMQ 5.11.0
> [ ] +0  no opinion
> [ ] -1  disapprove (and reason why)
>
>
> Here's my +1
>
> Regards,
> Gary.

Re: [VOTE] Apache ActiveMQ 5.11.0 (rc3)

[Jim Gomes]

+1

On Fri, Jan 30, 2015, 10:34 PM Claus Ibsen  wrote:

> Hi
>
> +1
>
> Tested against Camel in Action source code also.
>
> On Fri, Jan 30, 2015 at 3:00 PM, Gary Tully  wrote:
> > Hi folks,
> >
> > I've just cut a third release candidate for the long-awaited 5.11.0
> release.
> > This release has more than 120 bug fixes and improvements.
> >
> > -note-
> > this candidate includes the fix for the 'reliably' broken test case from
> rc2
> > however there can be no expectation of a 'reliable' full test run from
> > mvn install.
> > I have raised https://issues.apache.org/jira/browse/AMQ-5552 to address
> that.
> > I think a resolution to that issue would address all of the
> > disapproving commentary on the rc2 vote. If you voted -1 last time
> > round, please chime in on AMQ-5552.
> > -end note-
> >
> > Could you please review the artifacts and vote?
> >
> > The list of resolved issues is here:
> > https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> projectId=12311210&version=12324951
> >
> > You can get binary distributions here:
> > https://repository.apache.org/content/repositories/
> orgapacheactivemq-1016/org/apache/activemq/apache-activemq/5.11.0/
> >
> > Source archives are here:
> > https://repository.apache.org/content/repositories/
> orgapacheactivemq-1016/org/apache/activemq/activemq-parent/5.11.0/
> >
> > Maven2 repository is at:
> > https://repository.apache.org/content/repositories/
> orgapacheactivemq-1016/
> >
> > Source tag:
> > https://git-wip-us.apache.org/repos/asf?p=activemq.git;a=tag;h=
> 66bd5da9405765ddbc950b4f1c5a6ef6195207e5
> >
> > The vote will remain open for 72 hours.
> >
> > [ ] +1  approve the release as Apache ActiveMQ 5.11.0
> > [ ] +0  no opinion
> > [ ] -1  disapprove (and reason why)
> >
> >
> > Here's my +1
> >
> > Regards,
> > Gary.
>
>
>
> --
> Claus Ibsen
> -
> Red Hat, Inc.
> Email: cib...@redhat.com
> Twitter: davsclaus
> Blog: http://davsclaus.com
> Author of Camel in Action: http://www.manning.com/ibsen
> hawtio: http://hawt.io/
> fabric8 : http://fabric8.io/
>

Re: [VOTE] Apache ActiveMQ 5.11.0 (rc3)

[Claus Ibsen]

Hi

+1

Tested against Camel in Action source code also.

On Fri, Jan 30, 2015 at 3:00 PM, Gary Tully  wrote:
> Hi folks,
>
> I've just cut a third release candidate for the long-awaited 5.11.0 release.
> This release has more than 120 bug fixes and improvements.
>
> -note-
> this candidate includes the fix for the 'reliably' broken test case from rc2
> however there can be no expectation of a 'reliable' full test run from
> mvn install.
> I have raised https://issues.apache.org/jira/browse/AMQ-5552 to address that.
> I think a resolution to that issue would address all of the
> disapproving commentary on the rc2 vote. If you voted -1 last time
> round, please chime in on AMQ-5552.
> -end note-
>
> Could you please review the artifacts and vote?
>
> The list of resolved issues is here:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210&version=12324951
>
> You can get binary distributions here:
> https://repository.apache.org/content/repositories/orgapacheactivemq-1016/org/apache/activemq/apache-activemq/5.11.0/
>
> Source archives are here:
> https://repository.apache.org/content/repositories/orgapacheactivemq-1016/org/apache/activemq/activemq-parent/5.11.0/
>
> Maven2 repository is at:
> https://repository.apache.org/content/repositories/orgapacheactivemq-1016/
>
> Source tag:
> https://git-wip-us.apache.org/repos/asf?p=activemq.git;a=tag;h=66bd5da9405765ddbc950b4f1c5a6ef6195207e5
>
> The vote will remain open for 72 hours.
>
> [ ] +1  approve the release as Apache ActiveMQ 5.11.0
> [ ] +0  no opinion
> [ ] -1  disapprove (and reason why)
>
>
> Here's my +1
>
> Regards,
> Gary.



-- 
Claus Ibsen
-
Red Hat, Inc.
Email: cib...@redhat.com
Twitter: davsclaus
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen
hawtio: http://hawt.io/
fabric8: http://fabric8.io/

[VOTE] Apache ActiveMQ 5.11.0 (rc3)

[Gary Tully]

Hi folks,

I've just cut a third release candidate for the long-awaited 5.11.0 release.
This release has more than 120 bug fixes and improvements.

-note-
this candidate includes the fix for the 'reliably' broken test case from rc2
however there can be no expectation of a 'reliable' full test run from
mvn install.
I have raised https://issues.apache.org/jira/browse/AMQ-5552 to address that.
I think a resolution to that issue would address all of the
disapproving commentary on the rc2 vote. If you voted -1 last time
round, please chime in on AMQ-5552.
-end note-

Could you please review the artifacts and vote?

The list of resolved issues is here:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210&version=12324951

You can get binary distributions here:
https://repository.apache.org/content/repositories/orgapacheactivemq-1016/org/apache/activemq/apache-activemq/5.11.0/

Source archives are here:
https://repository.apache.org/content/repositories/orgapacheactivemq-1016/org/apache/activemq/activemq-parent/5.11.0/

Maven2 repository is at:
https://repository.apache.org/content/repositories/orgapacheactivemq-1016/

Source tag:
https://git-wip-us.apache.org/repos/asf?p=activemq.git;a=tag;h=66bd5da9405765ddbc950b4f1c5a6ef6195207e5

The vote will remain open for 72 hours.

[ ] +1  approve the release as Apache ActiveMQ 5.11.0
[ ] +0  no opinion
[ ] -1  disapprove (and reason why)


Here's my +1

Regards,
Gary.