Mixing
OutOfMemoryException on spring job execution context
0
I'm getting the below error when I put a large object in the JobApplicationContext. The object is converted to JSON and saved in BATCH_JOB_EXECUTION_CONTEXT, but not sure why we are getting the out of memory while processing the writer step.
java.lang.OutOfMemoryError: Java heap space
at java.util.Arrays.copyOf(Arrays.java:3332)
at java.lang.AbstractStringBuilder.ensureCapacityInternal(AbstractStringBuilder.java:124)
at java.lang.AbstractStringBuilder.append(AbstractStringBuilder.java:448)
at java.lang.StringBuffer.append(StringBuffer.java:270)
at java.io.StringWriter.write(StringWriter.java:101)
at org.codehaus.jettison.json.JSONObject.write(JSONObject.java:1238)
at org.codehaus.jettison.json.JSONArray.write(JSONArray.java:848)
at org.codehaus.jettison.json.JSONObject.write(JSONObject.java:1236)
at org.codehaus.jettison.json.JSONArray.write(JSONArray.java:848)
at org.codehaus.jettison.json.JSONObject.write(JSONObject.java:1236)
at org.codehaus.jettison.json.JSONObject.write(JSONObject.java:1234)
at org.codehaus.jettison.json.JSONArray.write(JSONArray.java:848)
at org.codehaus.jettison.json.JSONObject.write(JSONObject.java:1236)
at org.codehaus.jettison.json.JSONArray.write(JSONArray.java:848)
at org.codehaus.jettison.json.JSONObject.write(JSONObject.java:1236)
at org.codehaus.jettison.json.JSONArray.write(JSONArray.java:848)
at org.codehaus.jettison.json.JSONObject.write(JSONObject.java:1236)
at org.codehaus.jettison.json.JSONObject.write(JSONObject.java:1234)
at org.codehaus.jettison.json.JSONArray.write(JSONArray.java:848)
at org.codehaus.jettison.json.JSONObject.write(JSONObject.java:1236)
at org.codehaus.jettison.json.JSONObject.write(JSONObject.java:1234)
at org.codehaus.jettison.json.JSONArray.write(JSONArray.java:848)
at org.codehaus.jettison.json.JSONObject.write(JSONObject.java:1236)
at org.codehaus.jettison.json.JSONArray.write(JSONArray.java:848)
at org.codehaus.jettison.json.JSONObject.write(JSONObject.java:1236)
at org.codehaus.jettison.mapped.MappedXMLStreamWriter.writeJSONObject(MappedXMLStreamWriter.java:258)
at org.codehaus.jettison.mapped.MappedXMLStreamWriter.writeEndDocument(MappedXMLStreamWriter.java:244)
at com.thoughtworks.xstream.io.xml.StaxWriter.endNode(StaxWriter.java:149)
at com.thoughtworks.xstream.io.WriterWrapper.endNode(WriterWrapper.java:37)
at com.thoughtworks.xstream.io.path.PathTrackingWriter.endNode(PathTrackingWriter.java:48)
at com.thoughtworks.xstream.core.TreeMarshaller.start(TreeMarshaller.java:83)
at com.thoughtworks.xstream.core.AbstractTreeMarshallingStrategy.marshal(AbstractTreeMarshallingStrategy.java:37)
out-of-memory spring-batch
edited Nov 21 '18 at 8:37
Mahmoud Ben Hassine
4,2751714
asked Nov 21 '18 at 0:52
Ram ChRam Ch
1
add a comment |
0
I'm getting the below error when I put a large object in the JobApplicationContext. The object is converted to JSON and saved in BATCH_JOB_EXECUTION_CONTEXT, but not sure why we are getting the out of memory while processing the writer step.
java.lang.OutOfMemoryError: Java heap space
at java.util.Arrays.copyOf(Arrays.java:3332)
at java.lang.AbstractStringBuilder.ensureCapacityInternal(AbstractStringBuilder.java:124)
at java.lang.AbstractStringBuilder.append(AbstractStringBuilder.java:448)
at java.lang.StringBuffer.append(StringBuffer.java:270)
at java.io.StringWriter.write(StringWriter.java:101)
at org.codehaus.jettison.json.JSONObject.write(JSONObject.java:1238)
at org.codehaus.jettison.json.JSONArray.write(JSONArray.java:848)
at org.codehaus.jettison.json.JSONObject.write(JSONObject.java:1236)
at org.codehaus.jettison.json.JSONArray.write(JSONArray.java:848)
at org.codehaus.jettison.json.JSONObject.write(JSONObject.java:1236)
at org.codehaus.jettison.json.JSONObject.write(JSONObject.java:1234)
at org.codehaus.jettison.json.JSONArray.write(JSONArray.java:848)
at org.codehaus.jettison.json.JSONObject.write(JSONObject.java:1236)
at org.codehaus.jettison.json.JSONArray.write(JSONArray.java:848)
at org.codehaus.jettison.json.JSONObject.write(JSONObject.java:1236)
at org.codehaus.jettison.json.JSONArray.write(JSONArray.java:848)
at org.codehaus.jettison.json.JSONObject.write(JSONObject.java:1236)
at org.codehaus.jettison.json.JSONObject.write(JSONObject.java:1234)
at org.codehaus.jettison.json.JSONArray.write(JSONArray.java:848)
at org.codehaus.jettison.json.JSONObject.write(JSONObject.java:1236)
at org.codehaus.jettison.json.JSONObject.write(JSONObject.java:1234)
at org.codehaus.jettison.json.JSONArray.write(JSONArray.java:848)
at org.codehaus.jettison.json.JSONObject.write(JSONObject.java:1236)
at org.codehaus.jettison.json.JSONArray.write(JSONArray.java:848)
at org.codehaus.jettison.json.JSONObject.write(JSONObject.java:1236)
at org.codehaus.jettison.mapped.MappedXMLStreamWriter.writeJSONObject(MappedXMLStreamWriter.java:258)
at org.codehaus.jettison.mapped.MappedXMLStreamWriter.writeEndDocument(MappedXMLStreamWriter.java:244)
at com.thoughtworks.xstream.io.xml.StaxWriter.endNode(StaxWriter.java:149)
at com.thoughtworks.xstream.io.WriterWrapper.endNode(WriterWrapper.java:37)
at com.thoughtworks.xstream.io.path.PathTrackingWriter.endNode(PathTrackingWriter.java:48)
at com.thoughtworks.xstream.core.TreeMarshaller.start(TreeMarshaller.java:83)
at com.thoughtworks.xstream.core.AbstractTreeMarshallingStrategy.marshal(AbstractTreeMarshallingStrategy.java:37)
out-of-memory spring-batch
edited Nov 21 '18 at 8:37
Mahmoud Ben Hassine
4,2751714
asked Nov 21 '18 at 0:52
Ram ChRam Ch
1
Welcome to stackoverflow. Please take a minute to take the tour, especially How to Ask, and edit your question accordingly.
– JohnB
Nov 21 '18 at 1:18
You are getting the OOM error because your object is too large. Try to minimize the size of data that is added to the job execution context (add only the bare minimum) or, if this is not possible, you need to increase the size of your JVM's memory.
– Mahmoud Ben Hassine
Nov 21 '18 at 8:39
1
Found the root cause of the issue. Spring batch saves the job application context data in the DB. To save the data, spring batch uses a serializer which creates a JSON string for the context. Since that string is huge and it's in the memory, we got the out of memory exception.
– Ram Ch
Nov 21 '18 at 19:34
add a comment |
0
0
0
I'm getting the below error when I put a large object in the JobApplicationContext. The object is converted to JSON and saved in BATCH_JOB_EXECUTION_CONTEXT, but not sure why we are getting the out of memory while processing the writer step.
java.lang.OutOfMemoryError: Java heap space
at java.util.Arrays.copyOf(Arrays.java:3332)
at java.lang.AbstractStringBuilder.ensureCapacityInternal(AbstractStringBuilder.java:124)
at java.lang.AbstractStringBuilder.append(AbstractStringBuilder.java:448)
at java.lang.StringBuffer.append(StringBuffer.java:270)
at java.io.StringWriter.write(StringWriter.java:101)
at org.codehaus.jettison.json.JSONObject.write(JSONObject.java:1238)
at org.codehaus.jettison.json.JSONArray.write(JSONArray.java:848)
at org.codehaus.jettison.json.JSONObject.write(JSONObject.java:1236)
at org.codehaus.jettison.json.JSONArray.write(JSONArray.java:848)
at org.codehaus.jettison.json.JSONObject.write(JSONObject.java:1236)
at org.codehaus.jettison.json.JSONObject.write(JSONObject.java:1234)
at org.codehaus.jettison.json.JSONArray.write(JSONArray.java:848)
at org.codehaus.jettison.json.JSONObject.write(JSONObject.java:1236)
at org.codehaus.jettison.json.JSONArray.write(JSONArray.java:848)
at org.codehaus.jettison.json.JSONObject.write(JSONObject.java:1236)
at org.codehaus.jettison.json.JSONArray.write(JSONArray.java:848)
at org.codehaus.jettison.json.JSONObject.write(JSONObject.java:1236)
at org.codehaus.jettison.json.JSONObject.write(JSONObject.java:1234)
at org.codehaus.jettison.json.JSONArray.write(JSONArray.java:848)
at org.codehaus.jettison.json.JSONObject.write(JSONObject.java:1236)
at org.codehaus.jettison.json.JSONObject.write(JSONObject.java:1234)
at org.codehaus.jettison.json.JSONArray.write(JSONArray.java:848)
at org.codehaus.jettison.json.JSONObject.write(JSONObject.java:1236)
at org.codehaus.jettison.json.JSONArray.write(JSONArray.java:848)
at org.codehaus.jettison.json.JSONObject.write(JSONObject.java:1236)
at org.codehaus.jettison.mapped.MappedXMLStreamWriter.writeJSONObject(MappedXMLStreamWriter.java:258)
at org.codehaus.jettison.mapped.MappedXMLStreamWriter.writeEndDocument(MappedXMLStreamWriter.java:244)
at com.thoughtworks.xstream.io.xml.StaxWriter.endNode(StaxWriter.java:149)
at com.thoughtworks.xstream.io.WriterWrapper.endNode(WriterWrapper.java:37)
at com.thoughtworks.xstream.io.path.PathTrackingWriter.endNode(PathTrackingWriter.java:48)
at com.thoughtworks.xstream.core.TreeMarshaller.start(TreeMarshaller.java:83)
at com.thoughtworks.xstream.core.AbstractTreeMarshallingStrategy.marshal(AbstractTreeMarshallingStrategy.java:37)
out-of-memory spring-batch
edited Nov 21 '18 at 8:37
Mahmoud Ben Hassine
4,2751714
asked Nov 21 '18 at 0:52
Ram ChRam Ch
1
I'm getting the below error when I put a large object in the JobApplicationContext. The object is converted to JSON and saved in BATCH_JOB_EXECUTION_CONTEXT, but not sure why we are getting the out of memory while processing the writer step.
java.lang.OutOfMemoryError: Java heap space
at java.util.Arrays.copyOf(Arrays.java:3332)
at java.lang.AbstractStringBuilder.ensureCapacityInternal(AbstractStringBuilder.java:124)
at java.lang.AbstractStringBuilder.append(AbstractStringBuilder.java:448)
at java.lang.StringBuffer.append(StringBuffer.java:270)
at java.io.StringWriter.write(StringWriter.java:101)
at org.codehaus.jettison.json.JSONObject.write(JSONObject.java:1238)
at org.codehaus.jettison.json.JSONArray.write(JSONArray.java:848)
at org.codehaus.jettison.json.JSONObject.write(JSONObject.java:1236)
at org.codehaus.jettison.json.JSONArray.write(JSONArray.java:848)
at org.codehaus.jettison.json.JSONObject.write(JSONObject.java:1236)
at org.codehaus.jettison.json.JSONObject.write(JSONObject.java:1234)
at org.codehaus.jettison.json.JSONArray.write(JSONArray.java:848)
at org.codehaus.jettison.json.JSONObject.write(JSONObject.java:1236)
at org.codehaus.jettison.json.JSONArray.write(JSONArray.java:848)
at org.codehaus.jettison.json.JSONObject.write(JSONObject.java:1236)
at org.codehaus.jettison.json.JSONArray.write(JSONArray.java:848)
at org.codehaus.jettison.json.JSONObject.write(JSONObject.java:1236)
at org.codehaus.jettison.json.JSONObject.write(JSONObject.java:1234)
at org.codehaus.jettison.json.JSONArray.write(JSONArray.java:848)
at org.codehaus.jettison.json.JSONObject.write(JSONObject.java:1236)
at org.codehaus.jettison.json.JSONObject.write(JSONObject.java:1234)
at org.codehaus.jettison.json.JSONArray.write(JSONArray.java:848)
at org.codehaus.jettison.json.JSONObject.write(JSONObject.java:1236)
at org.codehaus.jettison.json.JSONArray.write(JSONArray.java:848)
at org.codehaus.jettison.json.JSONObject.write(JSONObject.java:1236)
at org.codehaus.jettison.mapped.MappedXMLStreamWriter.writeJSONObject(MappedXMLStreamWriter.java:258)
at org.codehaus.jettison.mapped.MappedXMLStreamWriter.writeEndDocument(MappedXMLStreamWriter.java:244)
at com.thoughtworks.xstream.io.xml.StaxWriter.endNode(StaxWriter.java:149)
at com.thoughtworks.xstream.io.WriterWrapper.endNode(WriterWrapper.java:37)
at com.thoughtworks.xstream.io.path.PathTrackingWriter.endNode(PathTrackingWriter.java:48)
at com.thoughtworks.xstream.core.TreeMarshaller.start(TreeMarshaller.java:83)
at com.thoughtworks.xstream.core.AbstractTreeMarshallingStrategy.marshal(AbstractTreeMarshallingStrategy.java:37)
out-of-memory spring-batch
out-of-memory spring-batch
edited Nov 21 '18 at 8:37
Mahmoud Ben Hassine
4,2751714
asked Nov 21 '18 at 0:52
Ram ChRam Ch
1
edited Nov 21 '18 at 8:37
Mahmoud Ben Hassine
4,2751714
asked Nov 21 '18 at 0:52
Ram ChRam Ch
1
edited Nov 21 '18 at 8:37
Mahmoud Ben Hassine
4,2751714
edited Nov 21 '18 at 8:37
Mahmoud Ben Hassine
4,2751714
edited Nov 21 '18 at 8:37
Mahmoud Ben Hassine
4,2751714
4,2751714
asked Nov 21 '18 at 0:52
Ram ChRam Ch
1
asked Nov 21 '18 at 0:52
Ram ChRam Ch
1
asked Nov 21 '18 at 0:52
Ram ChRam Ch
1
1
Welcome to stackoverflow. Please take a minute to take the tour, especially How to Ask, and edit your question accordingly.
– JohnB
Nov 21 '18 at 1:18
You are getting the OOM error because your object is too large. Try to minimize the size of data that is added to the job execution context (add only the bare minimum) or, if this is not possible, you need to increase the size of your JVM's memory.
– Mahmoud Ben Hassine
Nov 21 '18 at 8:39
1
Found the root cause of the issue. Spring batch saves the job application context data in the DB. To save the data, spring batch uses a serializer which creates a JSON string for the context. Since that string is huge and it's in the memory, we got the out of memory exception.
– Ram Ch
Nov 21 '18 at 19:34
add a comment |
Welcome to stackoverflow. Please take a minute to take the tour, especially How to Ask, and edit your question accordingly.
– JohnB
Nov 21 '18 at 1:18
You are getting the OOM error because your object is too large. Try to minimize the size of data that is added to the job execution context (add only the bare minimum) or, if this is not possible, you need to increase the size of your JVM's memory.
– Mahmoud Ben Hassine
Nov 21 '18 at 8:39
1
Found the root cause of the issue. Spring batch saves the job application context data in the DB. To save the data, spring batch uses a serializer which creates a JSON string for the context. Since that string is huge and it's in the memory, we got the out of memory exception.
– Ram Ch
Nov 21 '18 at 19:34
Welcome to stackoverflow. Please take a minute to take the tour, especially How to Ask, and edit your question accordingly.
– JohnB
Nov 21 '18 at 1:18
Welcome to stackoverflow. Please take a minute to take the tour, especially How to Ask, and edit your question accordingly.
– JohnB
Nov 21 '18 at 1:18
You are getting the OOM error because your object is too large. Try to minimize the size of data that is added to the job execution context (add only the bare minimum) or, if this is not possible, you need to increase the size of your JVM's memory.
– Mahmoud Ben Hassine
Nov 21 '18 at 8:39
You are getting the OOM error because your object is too large. Try to minimize the size of data that is added to the job execution context (add only the bare minimum) or, if this is not possible, you need to increase the size of your JVM's memory.
– Mahmoud Ben Hassine
Nov 21 '18 at 8:39
1
1
Found the root cause of the issue. Spring batch saves the job application context data in the DB. To save the data, spring batch uses a serializer which creates a JSON string for the context. Since that string is huge and it's in the memory, we got the out of memory exception.
– Ram Ch
Nov 21 '18 at 19:34
Found the root cause of the issue. Spring batch saves the job application context data in the DB. To save the data, spring batch uses a serializer which creates a JSON string for the context. Since that string is huge and it's in the memory, we got the out of memory exception.
– Ram Ch
Nov 21 '18 at 19:34
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53403809%2foutofmemoryexception-on-spring-job-execution-context%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
draft saved
draft discarded
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53403809%2foutofmemoryexception-on-spring-job-execution-context%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Welcome to stackoverflow. Please take a minute to take the tour, especially How to Ask, and edit your question accordingly.
– JohnB
Nov 21 '18 at 1:18
You are getting the OOM error because your object is too large. Try to minimize the size of data that is added to the job execution context (add only the bare minimum) or, if this is not possible, you need to increase the size of your JVM's memory.
– Mahmoud Ben Hassine
Nov 21 '18 at 8:39
1
Found the root cause of the issue. Spring batch saves the job application context data in the DB. To save the data, spring batch uses a serializer which creates a JSON string for the context. Since that string is huge and it's in the memory, we got the out of memory exception.
– Ram Ch
Nov 21 '18 at 19:34