You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I saw this in a DB with a UsingDocument that had a 300MB attachment(!). While it makes sense that this would hit memory limits, this specific path may be something that we could rectify by writing to a file buffer instead of a ByteArrayOutputStream. It's likely that it would fail on the next step when trying to actually process the XML, though.
[INFO] java.lang.OutOfMemoryError: Java heap space
[INFO] at java.util.Arrays.copyOf(Arrays.java:3236)
[INFO] at java.io.ByteArrayOutputStream.grow(ByteArrayOutputStream.java:118)
[INFO] at java.io.ByteArrayOutputStream.ensureCapacity(ByteArrayOutputStream.java:93)
[INFO] at java.io.ByteArrayOutputStream.write(ByteArrayOutputStream.java:135)
[INFO] at org.openntf.nsfodp.commons.io.SwiperOutputStream.write(SwiperOutputStream.java:76)
[INFO] at java.io.OutputStream.write(OutputStream.java:116)
[INFO] at java.io.OutputStream.write(OutputStream.java:75)
[INFO] at com.darwino.domino.napi.proc.XML_WRITE_FUNCTION$1.callback(XML_WRITE_FUNCTION.java:35)
...
The text was updated successfully, but these errors were encountered:
I saw this in a DB with a UsingDocument that had a 300MB attachment(!). While it makes sense that this would hit memory limits, this specific path may be something that we could rectify by writing to a file buffer instead of a ByteArrayOutputStream. It's likely that it would fail on the next step when trying to actually process the XML, though.
The text was updated successfully, but these errors were encountered: