You have plenty of tools to analyze a OOM. Either a commercial tool, or free tools. Just googling for 'Memory leak java analyzer' will bring a lot of those guys, like http://www.manageability.org/blog/stuff/open-source-profilers-for-java.
On Dec 24, 2007 6:58 PM, Luis Neves <[EMAIL PROTECTED]> wrote: > Luis Neves wrote: > > > > Hello all. > > > > I think I'm facing a problem in the mina http codec filter, I've been > > using it in previous applications that only deal with the request body > > without issues (SOAP web-services and the like), but in this application > > I have requests with cookies and query strings and I think this is the > > cause of the problem. > > One of the lists in the HttpRequestDecodingState seems to keep > > references to request headers... or at least that is what it seems to me. > > I guess I was wrong. > What seems to be happening is that some of the requests are built in such a > way > that while trying to decode them the codec enters in some weird loop that adds > elements to the headers collection, only stopping when there is no more memory > available. > > Is there something I can do to isolate the offending requests? > > > -- > Luis Neves > -- Regards, Cordialement, Emmanuel Lécharny www.iktek.com
