Out of memory need help!

[starki fox]

CIAO!
We failed in a performance test in a cluster

Here are the meages perhaps someone has an idea!!!

Server 1
####<Oct 31, 2006 3:30:57 PM CET> <Error> <HTTP> <la0107> <laapp1_mdba> <ExecuteThread: '22' for queue: 'weblogic.kernel.Default'> <<WLS Kernel>> <> <BEA-101017> <[ServletContext(id=10876681,name=gis,context-path=/gis)] Root cause of ServletException.
java.lang.OutOfMemoryError
>
and after some seconds:
java.lang.NullPointerException
at weblogic.socket.SocketMuxer.deliverExceptionAndCleanup(SocketMuxer.java:541)
at weblogic.socket.SocketMuxer.deliverHasException(SocketMuxer.java:521)
at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:125)
at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:32)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)


Server 2
WebLogic Server 8.1 SP3 Tue Jun 29 23:11:19 PDT 2004 404973
<TCP/IP socket failure occurred while fetching statedump

[Joe Ess]

Out of memory exceptions are almost always caused by application code. You can delay the problem a little by increasing the JVM heap size (see -Xms and -Xmx here). Go through your code and wherever there is something (socket, db connection, file, URLConnection) that has a close method, make sure it is called in a finally block. That's probably the most common cause of OOM's.
You may need a profiler like OptimizeIt to identify where memory is being consumed. In any case, OOM's are tedious to identify and solve.

[starki fox]

HI JOE!
Thanks but perhaps it's because where are 20 users which create graphics could you imagine that a memory
128 is much too few there?

Profiling would come after!
CIAO Starki

[Joe Ess]

Originally posted by starki fox:
. . . 20 users which create graphics. . .

Are you working with Java Image classes or just serving up file data? Java Image classes are notorious for memory consumption and leaking memory if not properly disposed.

[starki fox]

YES We use image classes,
so I think there might be some
need to increase the memory!

Thanks Starki

[Joe Ess]

In your other post you showed a try-catch-finally block. The most important object in that snippet is the database connection and you do not show closing it. Make sure you handle that properly too.