Re: RES: about java.lang.outofmemory error
If I understand the situation right, the sum total of all memory demands (both tomcat's and others) exceded the sum of all memory on the system, both real and virtual. Reducing the memory allocation to tomcat dropped the total demand to a level the system could provide. If that's the case, you'll end up having to get a bigger box in the long run. Decreasing tomcat's memory will most likely be only a short term solution. --David Milanez, Marcus wrote: Ok... I don't want this thread to be any longer, but the fact is that we haven't configured the heap for mor space them physical plus swap. Anyway, I got it solved when we decreased initial memory and maximum memory. -Mensagem original- De: Caldarale, Charles R [mailto:[EMAIL PROTECTED] Enviada em: segunda-feira, 17 de março de 2008 12:16 Para: Tomcat Users List Assunto: RE: about java.lang.outofmemory error From: Milanez, Marcus [mailto:[EMAIL PROTECTED] Subject: RES: about java.lang.outofmemory error GC never (ever) ran and Tomcat proccess could never acquire the amout of memory we'd specified The fact that GC never ran is irrelevant. As someone else pointed out, you likely configured the heap for more space than the sum of real plus swap, thereby causing a failure when attempting to allocate pages for the process. Also be aware that the JVM wil throw an OOME for *any* resource failure, including such things as running out of file descriptors. - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RES: about java.lang.outofmemory error
Ok... I don't want this thread to be any longer, but the fact is that we haven't configured the heap for mor space them physical plus swap. Anyway, I got it solved when we decreased initial memory and maximum memory. -Mensagem original- De: Caldarale, Charles R [mailto:[EMAIL PROTECTED] Enviada em: segunda-feira, 17 de março de 2008 12:16 Para: Tomcat Users List Assunto: RE: about java.lang.outofmemory error > From: Milanez, Marcus [mailto:[EMAIL PROTECTED] > Subject: RES: about java.lang.outofmemory error > > GC never (ever) ran and Tomcat proccess could never acquire the amout > of memory we'd specified The fact that GC never ran is irrelevant. As someone else pointed out, you likely configured the heap for more space than the sum of real plus swap, thereby causing a failure when attempting to allocate pages for the process. Also be aware that the JVM wil throw an OOME for *any* resource failure, including such things as running out of file descriptors. - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: about java.lang.outofmemory error
> From: Milanez, Marcus [mailto:[EMAIL PROTECTED] > Subject: RES: about java.lang.outofmemory error > > GC never (ever) ran and Tomcat proccess could never > acquire the amout of memory we'd specified The fact that GC never ran is irrelevant. As someone else pointed out, you likely configured the heap for more space than the sum of real plus swap, thereby causing a failure when attempting to allocate pages for the process. Also be aware that the JVM wil throw an OOME for *any* resource failure, including such things as running out of file descriptors. - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RES: RES: about java.lang.outofmemory error
Gabe, Quite like that. In my case, we didn't exceed the amout of physical memory available, but as our server shared its resources with other applications, it happened lots of times... -Mensagem original- De: Gabe Wong [mailto:[EMAIL PROTECTED] Enviada em: segunda-feira, 17 de março de 2008 11:41 Para: Tomcat Users List Assunto: Re: RES: about java.lang.outofmemory error Milanez, Marcus wrote: > Chuck, > > Sorry if I haven't been clear enough, but we did have several situations in > which such a thing happened in production. We'd specified too much memory to > tomcat, and as our server shared its physical with other applications such as > IIS, GC never (ever) ran and Tomcat proccess could never acquire the amout of > memory we'd specified, causing java.lang.OutOfMemory error plenty of times. > We could just solve it decreasing tomcat's proccess initial and maximum > amount of memory, that's why I've warned about it. I really apologize if I'm > wrong, but is there another explanation for it? > > It sounds like in your case, you were allocating more memory to the JVM that was available from the system. Thus quite naturally when you lowered the allocation you encountered less problems. However if your application had indeed required the larger allocation, you would have experienced OutOfMemory. Point is, larger memory allocation is a good thing, but it cannot exceed what is available on the system. -- Regards Gabe Wong NGASI AppServer Manager JAVA AUTOMATION and SaaS Enablement http://www.ngasi.com NEW! 8.0 - Centrally manage multiple physical servers - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: RES: about java.lang.outofmemory error
Milanez, Marcus wrote: Chuck, Sorry if I haven't been clear enough, but we did have several situations in which such a thing happened in production. We'd specified too much memory to tomcat, and as our server shared its physical with other applications such as IIS, GC never (ever) ran and Tomcat proccess could never acquire the amout of memory we'd specified, causing java.lang.OutOfMemory error plenty of times. We could just solve it decreasing tomcat's proccess initial and maximum amount of memory, that's why I've warned about it. I really apologize if I'm wrong, but is there another explanation for it? It sounds like in your case, you were allocating more memory to the JVM that was available from the system. Thus quite naturally when you lowered the allocation you encountered less problems. However if your application had indeed required the larger allocation, you would have experienced OutOfMemory. Point is, larger memory allocation is a good thing, but it cannot exceed what is available on the system. -- Regards Gabe Wong NGASI AppServer Manager JAVA AUTOMATION and SaaS Enablement http://www.ngasi.com NEW! 8.0 - Centrally manage multiple physical servers - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RES: about java.lang.outofmemory error
Chuck, Sorry if I haven't been clear enough, but we did have several situations in which such a thing happened in production. We'd specified too much memory to tomcat, and as our server shared its physical with other applications such as IIS, GC never (ever) ran and Tomcat proccess could never acquire the amout of memory we'd specified, causing java.lang.OutOfMemory error plenty of times. We could just solve it decreasing tomcat's proccess initial and maximum amount of memory, that's why I've warned about it. I really apologize if I'm wrong, but is there another explanation for it? Thank you! -Mensagem original- De: Caldarale, Charles R [mailto:[EMAIL PROTECTED] Enviada em: segunda-feira, 17 de março de 2008 11:06 Para: Tomcat Users List Assunto: RE: about java.lang.outofmemory error > From: Milanez, Marcus [mailto:[EMAIL PROTECTED] > Subject: RES: about java.lang.outofmemory error > > Just be aware that increasing memory isn't always the best option. In > most cases you should decrease memory instead, giving GC a chance to > run. If you increase memory, it may never run (realising unused > resources) and your process may never be able to allocate the amount > you specify... The above is confused and erroneous. GC will run automatically before any OOME is thrown, freeing up as much memory as is possible, including soft references. If you are referring to balancing heap space against non-heap space within the total process address space, GC has no effect, since the maximum heap size is reserved (but not allocated) at JVM initialization. There's no such thing as "giving GC a chance to run"; it will run, whenever it needs to. - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: about java.lang.outofmemory error
> From: Milanez, Marcus [mailto:[EMAIL PROTECTED] > Subject: RES: about java.lang.outofmemory error > > Just be aware that increasing memory isn't always the best > option. In most cases you should decrease memory instead, > giving GC a chance to run. If you increase memory, it may > never run (realising unused resources) and your process may > never be able to allocate the amount you specify... The above is confused and erroneous. GC will run automatically before any OOME is thrown, freeing up as much memory as is possible, including soft references. If you are referring to balancing heap space against non-heap space within the total process address space, GC has no effect, since the maximum heap size is reserved (but not allocated) at JVM initialization. There's no such thing as "giving GC a chance to run"; it will run, whenever it needs to. - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RES: about java.lang.outofmemory error
Hello, Just be aware that increasing memory isn't always the best option. In most cases you should decrease memory instead, giving GC a chance to run. If you increase memory, it may never run (realising unused resources) and your process may never be able to allocate the amount you specify... -Mensagem original- De: David Fisher [mailto:[EMAIL PROTECTED] Enviada em: segunda-feira, 17 de março de 2008 10:43 Para: Tomcat Users List Assunto: Re: about java.lang.outofmemory error I don't know about BIRT (other than it is a project to generate Excel reports), but I do know that in Apache POI when you read and write an Excel spreadsheet everything is done in memory, and a large amount of memory needs to be available if your spreadsheet is large. I add the following to my catalina.sh to increase memory: -Xms384m -Xmx724m I hope this helps, there are limits. Regards, Dave On Mar 17, 2008, at 8:05 AM, hns wrote: > > hi > i have developed one web application which contains eclipse birt 2.2 > it runs sucessfuly from 2 months but now while data inceresse it cause > problem of showing one report and gives error java.lang.outofmemory > error i have used tomcat 5.5.25 and jdk 1.5 i feel this is the problem > of tomcat 5.5 memory allocation could it solved any way please help me > -- > View this message in context: http://www.nabble.com/about- > java.lang.outofmemory-error-tp16092575p16092575.html > Sent from the Tomcat - User mailing list archive at Nabble.com. > > > - > To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, > e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: about java.lang.outofmemory error
I don't know about BIRT (other than it is a project to generate Excel reports), but I do know that in Apache POI when you read and write an Excel spreadsheet everything is done in memory, and a large amount of memory needs to be available if your spreadsheet is large. I add the following to my catalina.sh to increase memory: -Xms384m -Xmx724m I hope this helps, there are limits. Regards, Dave On Mar 17, 2008, at 8:05 AM, hns wrote: hi i have developed one web application which contains eclipse birt 2.2 it runs sucessfuly from 2 months but now while data inceresse it cause problem of showing one report and gives error java.lang.outofmemory error i have used tomcat 5.5.25 and jdk 1.5 i feel this is the problem of tomcat 5.5 memory allocation could it solved any way please help me -- View this message in context: http://www.nabble.com/about- java.lang.outofmemory-error-tp16092575p16092575.html Sent from the Tomcat - User mailing list archive at Nabble.com. - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: about java.lang.outofmemory error
> From: hns [mailto:[EMAIL PROTECTED] > Subject: about java.lang.outofmemory error > > i feel this is the problem of tomcat 5.5 memory allocation Extremely unlikely. The most probable cause is either a memory leak in your webapp or you simply have too much data for whatever size heap you have specified. Read the FAQ: http://wiki.apache.org/tomcat/FAQ/Memory - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
about java.lang.outofmemory error
hi i have developed one web application which contains eclipse birt 2.2 it runs sucessfuly from 2 months but now while data inceresse it cause problem of showing one report and gives error java.lang.outofmemory error i have used tomcat 5.5.25 and jdk 1.5 i feel this is the problem of tomcat 5.5 memory allocation could it solved any way please help me -- View this message in context: http://www.nabble.com/about-java.lang.outofmemory-error-tp16092575p16092575.html Sent from the Tomcat - User mailing list archive at Nabble.com. - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
