You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Dejan Bosanac (JIRA)" <ji...@apache.org> on 2010/05/06 08:48:37 UTC

[jira] Assigned: (AMQ-2706) Memory leak & huge thread count in broker

     [ https://issues.apache.org/activemq/browse/AMQ-2706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dejan Bosanac reassigned AMQ-2706:
----------------------------------

    Assignee: Dejan Bosanac

> Memory leak & huge thread count in broker
> -----------------------------------------
>
>                 Key: AMQ-2706
>                 URL: https://issues.apache.org/activemq/browse/AMQ-2706
>             Project: ActiveMQ
>          Issue Type: Bug
>    Affects Versions: 5.3.1
>         Environment: Linux ubuntu/Java HotSpot(TM) 64-Bit Server VM (build 14.1-b02, mixed mode)
>            Reporter: Andres
>            Assignee: Dejan Bosanac
>         Attachments: memtest.zip, snapshot6.png, snapshot7.png
>
>
> I'm using request/replay pattern where client on BrokerA  creates message and start listening response from temporary-queue, consumer listening on BrokerB, after getting message it sends respond back to the temporary queue.
> After getting message back, client on BrokerA removes temporary queue and closes session and closes connection
> Now if I take a look to the jmx then everythink is OK on BrokerA side. No hangig tmp queues no too many threads. On BrokerB every message lives hanging temporary queue and thread. Even if I shut down BrokerA there are still hanging tmp queue on brokerB and one extra thread.
> Now if I send 10k messages from BrokerA there is 10K temporary quest and 10K threads on brokerA
> Example setup:
> | Broker A  <NetworkConnector duplex=true> | ----->  |  Broker B |

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