Hi Peter,
Is it possible you have any circular references in your data? I've seen
scenarios where an error occurs which results in the runtime exception
being logged to disk but that runtime exception attempts to include a
dump of the various scopes and if there's data in those scopes that has
a circular reference, it will head into an infinite loop and invariably
run out of memory.
Andy
Peter J. Farrell wrote:
Hi Guys,
I have an OpenBD 1.2 server that on occasionally throws this exception
message in the bluedragon.log file:
ERROR: caught exception when dumping session data -
java.lang.OutOfMemoryError: Java heap space
Now, what is interesting is that the heap space settings are just fine
(768mb and 192mb of perm gen). We use sessions, but the data in the
session is really light. I suspect there is an issue with
onSessionEnd() when using sessions -- the stack trace in the exception
HTML file points to calls to onSessionEnd when this occurs. Any
thoughts on why this is happening?
.pjf
--
Open BlueDragon Public Mailing List
http://www.openbluedragon.org/ http://twitter.com/OpenBlueDragon
online manual: http://www.openbluedragon.org/manual/
mailing list - http://groups.google.com/group/openbd?hl=en
