> what I cannot understand is that why those ActiveMQTempQueue are always
> there even I close the connection.
Because the connection is not closed actually, it is just returned to the pool.
If I understand correctly, the following kinds of ActiveMQ objects
involve sync request to ActiveMQ broker
your connections, how do you manage to create
> the 1.5 GB of connection objects?
>
> By the way, why do you use TCP transport for connection to embedded
> ActiveMQ? Why not use VM transport, designed for exactly this purpose?
>
> Best regards, Ivan
>
>
--
View this message in context:
http://old.nabble.com/ActiveMQConnection-leaks-memory-by-caching-ActiveMQTempQueue-objects-tp28397951p28398408.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Hello,
2010/4/29 easyl :
> AMQ 5.3 in Geronimo 2.2
>
> I found ActiveMQConnection always hold the ActiveMQTempQueue and should lead
> to memory leak,
> especially using massive send/reply through temp queues.
>
> I create a ticket here https://issues.apache.org/activemq/browse/AMQ-2716
There is s
://old.nabble.com/ActiveMQConnection-leaks-memory-by-caching-ActiveMQTempQueue-objects-tp28397951p28397951.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
