It means you have a memory leak problem. One of the first cause is if you deploy some custom code that does not respect the JBI semantics of the exchanges and forget to send a DONE status. This usually means that threads are blocked waiting forever for a response, hence it leads to memory leaks. Another option is that you changed the thread pools configuration with too high values.
On Thu, Jul 31, 2008 at 8:36 AM, pratibhaG <[EMAIL PROTECTED]> wrote: > > Also I found that when I hit 89 requests third time, the available memory is > 506 MB and consumed varies between 320MB to 350MB servicemix throws out of > memory error. > If has not even reached 400 MB then why it says out of memory? > > Pratibha > -- > View this message in context: > http://www.nabble.com/Why-memory-utilization-is-so-high-for-servicemix--tp18712344p18748569.html > Sent from the ServiceMix - User mailing list archive at Nabble.com. > > -- Cheers, Guillaume Nodet ------------------------ Blog: http://gnodet.blogspot.com/
