BTW in any kind of memory leak type situation, it can help us to help you quicker if you run a profiler on the test case which will then report the types of objects which are leaking. e.g. if you run JProfiler or YourKit on the test case and attach the memory output file to the JIRA (probably zipped up if its huge) then we can typically diagnose the issue quicker.
On 6/6/06, Hiram Chirino <[EMAIL PROTECTED]> wrote:
Sorry.. not yet. I've been swamped.. I'll try hooking up a memory profiler to your test case perhaps early next week. On 6/6/06, skarthik <[EMAIL PROTECTED]> wrote: > > Hi, > > Just following up. Has anybody from the development team had a chance to > look at this problem and the test code I posted? Was wondering if this is a > geniune problem or is it something I am doing wrong? > > thanks, > karthik > -- > View this message in context: http://www.nabble.com/4.0-Consumer-OutOfMemoryError-bug--t1707655.html#a4733986 > Sent from the ActiveMQ - User forum at Nabble.com. > > -- Regards, Hiram
-- James ------- http://radio.weblogs.com/0112098/
