Hey Kelly, I just added a configuration option so that the size of the cache can be set. I've also reduced the default cache size to 1024. http://issues.apache.org/activemq/browse/AMQ-1001 tracked the issue.
Changes are committed to trunk in case you want to test them out. On 10/6/06, Kelly Campbell <[EMAIL PROTECTED]> wrote:
I filed a bug regarding that behaviour a while back. It's 64k for the openwire structures even when they're empty. This uses up the available heap quickly. :-( On 10/5/06, Hiram Chirino <[EMAIL PROTECTED]> wrote: > > It's normal for open wire to hang on to some cached objects for each > connection while the connection is still active. This is part of the > value > caching feature of openwire. Openwire will hang on to up to 16383 cached > values per connection. Perhaps this number is a little high. We should > make that a negotiated option in openwire. > > On 10/4/06, HU <[EMAIL PROTECTED]> wrote: > > > > > > > > >>Yes - but which object is retaining it? > > > > I am not sure but I guess if those objects concern with the holding > > LocalTransactionId: > > > > 1, [47] of org.apache.activemq.command.DataStructure[16383] > > marshallCache of org.apache.activemq.openwire.OpenWireFormat [Stack > > Local] > > 2, key of java.util.HashMap$Entry > > [3940] of java.util.HashMapA$Entry[4097] > > table of java.util.HashMap > > marshallCacheMap of > > org.apache.activemq.openwire.OpenWireFormat[Stack Local] > > > > Those are copy from yourKit tool: > > GC Roots -> Instances of class > > 'org.apache.activemq.command.LocalTransactionId' > > > > > > -- > > View this message in context: > > http://www.nabble.com/Broker-used-up-the-memory-tf2316972.html#a6635134 > > Sent from the ActiveMQ - User mailing list archive at Nabble.com. > > > > > > > -- > Regards, > Hiram > > Blog: http://hiramchirino.com > >
-- Regards, Hiram Blog: http://hiramchirino.com
