> 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
> 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
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
> 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 s
