[jetty-dev] [jira] (JETTY-1535) handle failed java.lang.OutOfMemoryError

Greg Wilkins
resolved JETTY-1535 as Not A Bug

handle failed java.lang.OutOfMemoryError

running out of memory mostly not a bug, unless there is a leak somewhere. More importantly, the code that runs out of memory is often not the cause of the leak.

In this case, it may have been the application or some other code that has consumed all the free memory and the ChannelEndPoint is just the straw that broke the camels back and not the cause of the memory consumption.

So firstly you need to evaluate how much memory your application needs in Idle and per connection - then determine if you have allocated enough memory for the load offered.

Secondly you need to look for any memory leaks. Does memory consumption return to previous levels after load is removed.

If you see memory problems, you need to profile them. Only if you see evidence of Jetty using excessive memory or not releasing memory should it be considered a Jetty bug.

If you need help analysing your application for such memory issues, please contact http://www.webtide.com as we offer application tuning as a service.

Change By:

Greg Wilkins
(07/Aug/12 5:49 PM)

Resolution:

Not A Bug

Status:

Open
Resolved

This message is automatically generated by JIRA.

If you think it was sent incorrectly, please contact your JIRA administrators .

For more information on JIRA, see: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email