Searched on Google with the first line of a JAVA stack trace?

We can recommend more relevant solutions and speed up debugging when you paste your entire stack trace with the exception message. Try a sample exception.

Recommended solutions based on your search

Solutions on the web

via Oracle Community by 653908, 1 year ago
allocLargeArray - Object size: 65552, Num elements: 65536
via Oracle Community by 785911, 2 years ago
allocLargeObjectOrArray - Object size: 4096, Num elements: 4080
via Oracle Community by Ramakrishnan_S88, 2 years ago
via Stack Overflow by gowtham ragunath
, 1 year ago
java.lang.OutOfMemoryError: allocLargeArray - Object size: 65552, Num elements: 65536 at weblogic.utils.io.Chunk.<init>(Chunk.java:293) at weblogic.utils.io.Chunk.getChunk(Chunk.java:141) at weblogic.utils.io.ChunkedOutputStream.init(ChunkedOutputStream.java:28) at weblogic.utils.io.ChunkedOutputStream.<init>(ChunkedOutputStream.java:24) at weblogic.utils.io.ChunkedDataOutputStream.<init>(ChunkedDataOutputStream.java:15) at weblogic.servlet.internal.ResponseHeaders.writeHeaders(ResponseHeaders.java:310) at weblogic.servlet.internal.ServletResponseImpl.writeHeaders(ServletResponseImpl.java:1164) at weblogic.servlet.internal.ServletOutputStreamImpl.sendHeaders(ServletOutputStreamImpl.java:238) at weblogic.servlet.internal.ServletOutputStreamImpl.flush(ServletOutputStreamImpl.java:107) at weblogic.servlet.internal.ServletOutputStreamImpl.commit(ServletOutputStreamImpl.java:441) at weblogic.servlet.internal.ServletResponseImpl.send(ServletResponseImpl.java:1325) at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1368) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209) at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)