There are indeed memory issues in GlassFish, and we are actively working on
them.
If you can, you might try using GlassFish 3.1 (which is released) to see if
that works better for you thatn 3.0.1. We are working on further
improvements in 3.1.1 (currently being developed).
The code in the stack trace is not necessarily the code that causes the
excessive memory consumption; it is just the code that is requesting memory
that cannot be granted because the heap is full.
- Tim
--
[Message sent by forum member 'tjquinn']
View Post: http://forums.java.net/node/809250