Troubleshooting
Problem
With JDBC tracing parameter set to true (i.e.,
Symptom
If you examine the WebLogic application server log or the Content Engine error/trace logs, you'll see an "Out Of Memory" exception with a stack similar to the example below:
Caused by: java.lang.OutOfMemoryError: allocLargeObjectOrArray - Object size: 1073741840, Num elements: 1073741824
at java.io.ByteArrayOutputStream.write(ByteArrayOutputStream.java:70)
at weblogic.logging.LoggingOutputStream.write(LoggingOutputStream.java:45)
at java.io.OutputStream.write(OutputStream.java:98)
at java.io.PrintStream.write(PrintStream.java:413)
at sun.nio.cs.StreamEncoder$CharsetSE.writeBytes(StreamEncoder.java:336)
at sun.nio.cs.StreamEncoder$CharsetSE.implWrite(StreamEncoder.java:395)
at sun.nio.cs.StreamEncoder.write(StreamEncoder.java:136)
at java.io.OutputStreamWriter.write(OutputStreamWriter.java:192)
...
...
From the stack, you can see that WebLogic logging it trying to allocate 1GB (1073741824 bytes) of heap memory, thus causing the Out Of Memory exception.
Log InLog in to view more of this document
Was this topic helpful?
Document Information
Modified date:
28 April 2025
UID
swg21431108