On Thu, 14 Jun 2001, Spencer Smith wrote:
This occurs when a very large query is performed. Anyone know of a way
around this?
Weblogic Output:
; nested exception is:
java.lang.OutOfMemoryError:
Start server side stack trace:
java.lang.OutOfMemoryError
It means you are out of memory :-)
What happens is that when the JVM is started, it has an upper limit on the
total amount of memory it will allocate on the heap for Java objects. If
you try to create more objects than you have room for, you get this
exception.
Typically, a JVM will support command line options to change the default
memory maximum (typically 32mb or 64mb). With the standard Sun JVM, for
example, you do this with the -mx command line option. Weblogic's
startup scripts might have some documented ways to do it from the command
line, or from a properties file, or something like that.
Craig
