On Thu, 23 Dec 2010, Clemens wrote:
Try increasing your Java memory
our tomcat has 1G available. The heap dump reveals that the thread executing
the request consumed 630M (!) when the OOM was thrown...
I bring up my question again, this time (hopefully) in the right "context"
;-)
Do we approx. know what file sizes (of xlsx, etc.) can cause OOM problems?
Or is it not just a question of size but of content?
I personally haven't done much testing, as I tend to use the event model
for text extraction rather than the usermodel for read/edit/write
However, a small file probably ought not to need to use as much memory as
you've found. Any chance you could run it in a profiler, and try to
identify where the memory goes?
Nick
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
