You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Mario Lukica (JIRA)" <ji...@apache.org> on 2009/12/13 12:01:52 UTC

[jira] Created: (AMQ-2530) memory leak in ConduitBridge (subscriptionMapByRemoteId)

memory leak in ConduitBridge (subscriptionMapByRemoteId)
--------------------------------------------------------

                 Key: AMQ-2530
                 URL: https://issues.apache.org/activemq/browse/AMQ-2530
             Project: ActiveMQ
          Issue Type: Bug
    Affects Versions: 5.3.0
            Reporter: Mario Lukica


I believe there is a memory leak in ConduitBridge - looks like DemandSubscriptions are not removed from subscriptionMapByRemoteId when remote RemoveInfo is received.

removeDemandSubscription normally removes subscription from subscriptionMapByRemoteId in DemanForwardingBridgeSupport, but method is overriden in ConduitBridge and only removes subscription from subscriptionMapByLocalId.

Leak becomes more significant when consumers are connecting very often (i.e. few connections per second), and bridge connection is stable (lasts for couple of days without reconnecting). MessageConsumer's are not pooled and subscriptions are created and removed often (and forwarded via bridge).



-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (AMQ-2530) memory leak in ConduitBridge (subscriptionMapByRemoteId)

Posted by "Rob Davies (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/activemq/browse/AMQ-2530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rob Davies updated AMQ-2530:
----------------------------

    Fix Version/s: 5.3.1

> memory leak in ConduitBridge (subscriptionMapByRemoteId)
> --------------------------------------------------------
>
>                 Key: AMQ-2530
>                 URL: https://issues.apache.org/activemq/browse/AMQ-2530
>             Project: ActiveMQ
>          Issue Type: Bug
>    Affects Versions: 5.3.0
>            Reporter: Mario Lukica
>            Assignee: Rob Davies
>             Fix For: 5.3.1, 5.4.0
>
>
> I believe there is a memory leak in ConduitBridge - looks like DemandSubscriptions are not removed from subscriptionMapByRemoteId when remote RemoveInfo is received.
> removeDemandSubscription normally removes subscription from subscriptionMapByRemoteId in DemanForwardingBridgeSupport, but method is overriden in ConduitBridge and only removes subscription from subscriptionMapByLocalId.
> Leak becomes more significant when consumers are connecting very often (i.e. few connections per second), and bridge connection is stable (lasts for couple of days without reconnecting). MessageConsumer's are not pooled and subscriptions are created and removed often (and forwarded via bridge).

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Resolved: (AMQ-2530) memory leak in ConduitBridge (subscriptionMapByRemoteId)

Posted by "Rob Davies (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/activemq/browse/AMQ-2530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rob Davies resolved AMQ-2530.
-----------------------------

       Resolution: Fixed
    Fix Version/s: 5.4.0

Fixed by SVN revision 902009

> memory leak in ConduitBridge (subscriptionMapByRemoteId)
> --------------------------------------------------------
>
>                 Key: AMQ-2530
>                 URL: https://issues.apache.org/activemq/browse/AMQ-2530
>             Project: ActiveMQ
>          Issue Type: Bug
>    Affects Versions: 5.3.0
>            Reporter: Mario Lukica
>            Assignee: Rob Davies
>             Fix For: 5.4.0
>
>
> I believe there is a memory leak in ConduitBridge - looks like DemandSubscriptions are not removed from subscriptionMapByRemoteId when remote RemoveInfo is received.
> removeDemandSubscription normally removes subscription from subscriptionMapByRemoteId in DemanForwardingBridgeSupport, but method is overriden in ConduitBridge and only removes subscription from subscriptionMapByLocalId.
> Leak becomes more significant when consumers are connecting very often (i.e. few connections per second), and bridge connection is stable (lasts for couple of days without reconnecting). MessageConsumer's are not pooled and subscriptions are created and removed often (and forwarded via bridge).

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Assigned: (AMQ-2530) memory leak in ConduitBridge (subscriptionMapByRemoteId)

Posted by "Rob Davies (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/activemq/browse/AMQ-2530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rob Davies reassigned AMQ-2530:
-------------------------------

    Assignee: Rob Davies

> memory leak in ConduitBridge (subscriptionMapByRemoteId)
> --------------------------------------------------------
>
>                 Key: AMQ-2530
>                 URL: https://issues.apache.org/activemq/browse/AMQ-2530
>             Project: ActiveMQ
>          Issue Type: Bug
>    Affects Versions: 5.3.0
>            Reporter: Mario Lukica
>            Assignee: Rob Davies
>             Fix For: 5.4.0
>
>
> I believe there is a memory leak in ConduitBridge - looks like DemandSubscriptions are not removed from subscriptionMapByRemoteId when remote RemoveInfo is received.
> removeDemandSubscription normally removes subscription from subscriptionMapByRemoteId in DemanForwardingBridgeSupport, but method is overriden in ConduitBridge and only removes subscription from subscriptionMapByLocalId.
> Leak becomes more significant when consumers are connecting very often (i.e. few connections per second), and bridge connection is stable (lasts for couple of days without reconnecting). MessageConsumer's are not pooled and subscriptions are created and removed often (and forwarded via bridge).

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.