One possible workaround is to use a combination of permanent queue and header property (e.g., correlationId). See the following
http://activemq.apache.org/how-should-i-implement-request-response-with-jms.html Joe ActiveMQ Reference Guide: http://bit.ly/AMQRefGuide easyl wrote: > > I am using embedded AMQ 4.1.2 (in geronimo 2.1.4) > and find there is a memory problem similar to this: > https://issues.apache.org/activemq/browse/AMQ-1681 > > I run a system (64bit, 3G mem) after 8 hours, about 1000000 temp queue was > created for send/reply. > I can find 400~500 MB (and counting) for Log4j instance from memory dump > (jmap). > > Is there any workaround so that I don't need to upgrade AMQ, compile, > patch AMQ, and etc. > Can I possible remove those log4j instance for temporary queue at runtime? > -- View this message in context: http://old.nabble.com/finding-workaround-to-solve-memory-leak-problem-when-creating-large-numbers-of-TemporaryQueues-%28Log4J-related%29-tp28287983p28332227.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
