Java ThreadPoolExecutor limit queue size
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}
I am using threadpool to insert data to database. This is a secondary test database and once in a while the request to it start failing and the threadpool queue starts getting huge. I am trying to limit the queue size of the threadpool so that if there are any issues with the database it does not take over the memory of the application by filling up the queue. Note the queueSize below.
threadpool = new ThreadPoolExecutor(corePoolSize, threadPoolSize, keepAliveTime, TimeUnit.SECONDS, new LinkedBlockingQueue<Runnable>(queueSize), new MyThreadFactory());
I did a little research and found that when the queue is full, the submit method throws RejectedExecutionException. Since I don't want to do anything more than the queue size and I don't care much about the test data I could safely ignore the request. So I am thinking, I could simply do something like this below.
try {
threadPool.submit(task);
} catch (RejectedExecutionException ree){
//log the request was rejected and ignore the request
}
If I am fine ignoring the requests once the queue is full is this operation safe? I wanted to ask if it could create any other issues that I am not aware of? I read other similar posts but their requirement was different because they didn't have an option to simply ignore the request.
ThreadPoolExecutor Block When Queue Is Full?
How to make ThreadPoolExecutor's submit() method block if it is saturated?
java multithreading concurrency executorservice threadpoolexecutor
asked Nov 23 '18 at 16:00
Doctor WhiteDoctor White
6513
add a comment |
I am using threadpool to insert data to database. This is a secondary test database and once in a while the request to it start failing and the threadpool queue starts getting huge. I am trying to limit the queue size of the threadpool so that if there are any issues with the database it does not take over the memory of the application by filling up the queue. Note the queueSize below.
threadpool = new ThreadPoolExecutor(corePoolSize, threadPoolSize, keepAliveTime, TimeUnit.SECONDS, new LinkedBlockingQueue<Runnable>(queueSize), new MyThreadFactory());
I did a little research and found that when the queue is full, the submit method throws RejectedExecutionException. Since I don't want to do anything more than the queue size and I don't care much about the test data I could safely ignore the request. So I am thinking, I could simply do something like this below.
try {
threadPool.submit(task);
} catch (RejectedExecutionException ree){
//log the request was rejected and ignore the request
}
If I am fine ignoring the requests once the queue is full is this operation safe? I wanted to ask if it could create any other issues that I am not aware of? I read other similar posts but their requirement was different because they didn't have an option to simply ignore the request.
ThreadPoolExecutor Block When Queue Is Full?
How to make ThreadPoolExecutor's submit() method block if it is saturated?
java multithreading concurrency executorservice threadpoolexecutor
asked Nov 23 '18 at 16:00
Doctor WhiteDoctor White
6513
2
If you want to safely ignore the request then you shoud add the last parameter - new ThreadPoolExecutor.DiscardPolicy()
– Evgeniy Dorofeev
Nov 23 '18 at 18:45
add a comment |
I am using threadpool to insert data to database. This is a secondary test database and once in a while the request to it start failing and the threadpool queue starts getting huge. I am trying to limit the queue size of the threadpool so that if there are any issues with the database it does not take over the memory of the application by filling up the queue. Note the queueSize below.
threadpool = new ThreadPoolExecutor(corePoolSize, threadPoolSize, keepAliveTime, TimeUnit.SECONDS, new LinkedBlockingQueue<Runnable>(queueSize), new MyThreadFactory());
I did a little research and found that when the queue is full, the submit method throws RejectedExecutionException. Since I don't want to do anything more than the queue size and I don't care much about the test data I could safely ignore the request. So I am thinking, I could simply do something like this below.
try {
threadPool.submit(task);
} catch (RejectedExecutionException ree){
//log the request was rejected and ignore the request
}
If I am fine ignoring the requests once the queue is full is this operation safe? I wanted to ask if it could create any other issues that I am not aware of? I read other similar posts but their requirement was different because they didn't have an option to simply ignore the request.
ThreadPoolExecutor Block When Queue Is Full?
How to make ThreadPoolExecutor's submit() method block if it is saturated?
java multithreading concurrency executorservice threadpoolexecutor
asked Nov 23 '18 at 16:00
Doctor WhiteDoctor White
6513
I am using threadpool to insert data to database. This is a secondary test database and once in a while the request to it start failing and the threadpool queue starts getting huge. I am trying to limit the queue size of the threadpool so that if there are any issues with the database it does not take over the memory of the application by filling up the queue. Note the queueSize below.
threadpool = new ThreadPoolExecutor(corePoolSize, threadPoolSize, keepAliveTime, TimeUnit.SECONDS, new LinkedBlockingQueue<Runnable>(queueSize), new MyThreadFactory());
I did a little research and found that when the queue is full, the submit method throws RejectedExecutionException. Since I don't want to do anything more than the queue size and I don't care much about the test data I could safely ignore the request. So I am thinking, I could simply do something like this below.
try {
threadPool.submit(task);
} catch (RejectedExecutionException ree){
//log the request was rejected and ignore the request
}
If I am fine ignoring the requests once the queue is full is this operation safe? I wanted to ask if it could create any other issues that I am not aware of? I read other similar posts but their requirement was different because they didn't have an option to simply ignore the request.
ThreadPoolExecutor Block When Queue Is Full?
How to make ThreadPoolExecutor's submit() method block if it is saturated?
java multithreading concurrency executorservice threadpoolexecutor
java multithreading concurrency executorservice threadpoolexecutor
asked Nov 23 '18 at 16:00
Doctor WhiteDoctor White
6513
asked Nov 23 '18 at 16:00
Doctor WhiteDoctor White
6513
asked Nov 23 '18 at 16:00
Doctor WhiteDoctor White
6513
asked Nov 23 '18 at 16:00
Doctor WhiteDoctor White
6513
asked Nov 23 '18 at 16:00
Doctor WhiteDoctor White
6513
6513
2
If you want to safely ignore the request then you shoud add the last parameter - new ThreadPoolExecutor.DiscardPolicy()
– Evgeniy Dorofeev
Nov 23 '18 at 18:45
add a comment |
2
If you want to safely ignore the request then you shoud add the last parameter - new ThreadPoolExecutor.DiscardPolicy()
– Evgeniy Dorofeev
Nov 23 '18 at 18:45
2
2
If you want to safely ignore the request then you shoud add the last parameter - new ThreadPoolExecutor.DiscardPolicy()
– Evgeniy Dorofeev
Nov 23 '18 at 18:45
If you want to safely ignore the request then you shoud add the last parameter - new ThreadPoolExecutor.DiscardPolicy()
– Evgeniy Dorofeev
Nov 23 '18 at 18:45
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
});
}
});
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%2f53449747%2fjava-threadpoolexecutor-limit-queue-size%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
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.
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%2f53449747%2fjava-threadpoolexecutor-limit-queue-size%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
2
If you want to safely ignore the request then you shoud add the last parameter - new ThreadPoolExecutor.DiscardPolicy()
– Evgeniy Dorofeev
Nov 23 '18 at 18:45