I think the problem might be the default Subscription Recovery Policy in ActiveMQ 4.1.1 (support for retroactive consumers). See https://issues.apache.org/activemq/browse/AMQ-1321 for the problem and http://activemq.apache.org/subscription-recovery-policy.html for more information. I'd probably set the policy to <noSubscriptionRecoveryPolicy/>.
Mario On Tue, Jun 24, 2008 at 8:36 PM, Edwin Babadaglian <[EMAIL PROTECTED]> wrote: > > Greetings! > > How would an ActiveMQ 4.1.1 installation need to be configured so that > non-persistent messages to non-durable topic subscribers are purged more > eagerly? > > My JMS applications are transferring files, using ~1MB sized messages, and > it appears that jconsole reveals 50 messages being left behind completing a > 50MB file. Also, jmap reports a byte-array accumulation of about 80MB at > this point. When I remove the topic with jconsole, the heap usage returns to > around 10MB. The apps are transferring over auto-acknowledged sessions and > the broker's at the default configuration. > > Thanks in advance for any help. > > -- > View this message in context: > http://www.nabble.com/Purging-non-persistent-topic-messages-more-eagerly.-tp18097270p18097270.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. > >
