[jira] [Commented] (AMQ-5564) activemq-pool - Either adds new mbeans or add/remove pair of mbean for each producer in use

["Claus Ibsen (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/AMQ-5564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14307288#comment-14307288 ] 

Claus Ibsen commented on AMQ-5564:
----------------------------------

Okay after using git bitsect on the 5.10.x branch between the working 5.10.0 and not working 5.10.1 releases, I was able to narrow it down to this commit causing the breakings

{code}
davsclaus:~/workspace/activemq ((no branch))/$ git bisect good
ac57ce9f68e2b3c5f2d004f507383d64161de3ec is the first bad commit
commit ac57ce9f68e2b3c5f2d004f507383d64161de3ec
Author: Timothy Bish <ta...@gmail.com>
Date:   Thu Jun 12 19:12:56 2014 -0400

    https://issues.apache.org/jira/browse/AMQ-5015

    Refactor the way sessions are pooled.  We don't need to keep the
    PooledSession instances around since the state is unique to the session
    it wraps we only need to keep the Session instances in the SessionPool
    and create a new PooledSession on borrow to manage that session.  This
    allows the PooledSession to have a real closed state that protects
    against multiple close calls placing duplicate PooledSession instances
    into the SessionPool.  This also simplifies the code in the
    XaConnectionPool since it doesn't need to try and reset state in
    PouledSessions before placing them back as it gets a fresh wrapper each
    time with the correct state.

:040000 040000 d2fcf1c9eee5b8405cf0923e72484be53385fc78 fac1f9bec90c049bf21a9cdd986b76f010cfb90e M	activemq-jms-pool
{code}

> activemq-pool - Either adds new mbeans or add/remove pair of mbean for each producer in use
> -------------------------------------------------------------------------------------------
>
>                 Key: AMQ-5564
>                 URL: https://issues.apache.org/jira/browse/AMQ-5564
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: activemq-pool
>    Affects Versions: 5.10.1, 5.11.0
>            Reporter: Claus Ibsen
>         Attachments: amq-5100.png, amq-5101.png, amq-5110.png
>
>
> On the AMQ dev mailing list we have talked about a new issue.
> http://activemq.2283324.n4.nabble.com/VOTE-Apache-ActiveMQ-5-11-0-rc3-tp4690743.html
> I found out that using the camel-example-management, which has an embedded AMQ broker and using Camel with the VM transport to produce/consume messages, then there is mbean issues.
> It works fine in AMQ 5.10.0. But is wrong in AMQ 5.10.1 and 5.11.0.
> See the attached screenshots.
> Notice how the mbean tree for dynamic producers keeps growing for 5.10.1 and 5.11.0.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)