Mixing
Value set using Setter method in Runnable implimentation with bean scope prototype is not accessible in run...
0
Dummy Code snippet of problem statement:
Scheduler method
@Scheduled(fixedRate = 30000)
@Transactional(readOnly = true)
public void scheduledTask() {
TaskExecutor threadPool = ctx.getBean(TaskExecutor.class);
long totalCount = someDao.someOperation("argument");
Runner runner;
for (int offset = 0; offset < totalCount; offset += 50) {
runner = ctx.getBean(Runner.class);
runner.setOffset(offset);
threadPool.execute(runner);
}
}
Runnable Implimentaion
@Component
@Scope(scopeName="prototype", proxyMode=ScopedProxyMode.TARGET_CLASS)
@Transactional
public class Runner implements Runnable {
private Integer offset;
private Integer limit;
private ISomeDao someDao;
public Runner(ISomeDao someDao) {
this.someDao = someDao;
}
public void setOffset(int offset) {
this.offset = offset;
this.limit = this.offset + 50;
}
@Override
public void run() {
List<Operation> operations = someDao.fetchData(offset, limit, someCriteria);
///
/// other business logic
}
}
Problem that i am facing:
In scheduledTask, program set the value of offset correctly(check in debug mode),
but it is not accessible in run method of the Runner class, offset it always null.
When i remove the spring annotation from Runner class and instantiate it mannuly in
scheduledTask then i can access the offset value, but it will throw exception as
there is no transaction manager available which is expected.
I also tried to inject the EntityManger in the
runner = ctx.getBean(Runner.class, ctx.getBean(EntityManager.class);
in the scheduledTask
when i remove the Spring annotation, but the problem remain the same as Thread is not managed by Spring
I have spent hour finding the solution.
spring spring-boot spring-data-jpa
asked Jan 1 at 7:54
Deepak KumarDeepak Kumar
286
add a comment |
0
Dummy Code snippet of problem statement:
Scheduler method
@Scheduled(fixedRate = 30000)
@Transactional(readOnly = true)
public void scheduledTask() {
TaskExecutor threadPool = ctx.getBean(TaskExecutor.class);
long totalCount = someDao.someOperation("argument");
Runner runner;
for (int offset = 0; offset < totalCount; offset += 50) {
runner = ctx.getBean(Runner.class);
runner.setOffset(offset);
threadPool.execute(runner);
}
}
Runnable Implimentaion
@Component
@Scope(scopeName="prototype", proxyMode=ScopedProxyMode.TARGET_CLASS)
@Transactional
public class Runner implements Runnable {
private Integer offset;
private Integer limit;
private ISomeDao someDao;
public Runner(ISomeDao someDao) {
this.someDao = someDao;
}
public void setOffset(int offset) {
this.offset = offset;
this.limit = this.offset + 50;
}
@Override
public void run() {
List<Operation> operations = someDao.fetchData(offset, limit, someCriteria);
///
/// other business logic
}
}
Problem that i am facing:
In scheduledTask, program set the value of offset correctly(check in debug mode),
but it is not accessible in run method of the Runner class, offset it always null.
When i remove the spring annotation from Runner class and instantiate it mannuly in
scheduledTask then i can access the offset value, but it will throw exception as
there is no transaction manager available which is expected.
I also tried to inject the EntityManger in the
runner = ctx.getBean(Runner.class, ctx.getBean(EntityManager.class);
in the scheduledTask
when i remove the Spring annotation, but the problem remain the same as Thread is not managed by Spring
I have spent hour finding the solution.
spring spring-boot spring-data-jpa
asked Jan 1 at 7:54
Deepak KumarDeepak Kumar
286
1
Did you try to use the default spring scope singleton? Does it work? If it work it means that in order to execute the job spring creates a new runner object where offset is not set
– Angelo Immediata
Jan 1 at 8:24
Agree with @AngeloImmediata. You need to try different scope to your bean. prototype will create different objects for different requests. So it might be the problem.
– Damith
Jan 1 at 10:07
@AngeloImmediata It works in default scope, but my requirement is prototype. Also I added debug point in Runner constructor to check how many time object is created and for every loop spring is creating 2 instance and when i comment out the runner.setOffset(offset) line in scheduledTask() , object is created only once. Is it expected behaviour in spring. With my understanding, in prototype scope new object is created by spring every time Bean is referenced, which in my case is runner = ctx.getBean(Runner.class); Am i wrong ?
– Deepak Kumar
Jan 1 at 10:08
It seems really strange to me that just executgingrunner.setOffset(offset)the object is created twice. With prototype scope creates a new instance every time the object is injected in other beans or thegetBeanmethod is used (docs.spring.io/spring/docs/current/spring-framework-reference/…). I guess there are 2 instances not for the setOffset but because the runner is injected in some way
– Angelo Immediata
Jan 1 at 10:33
add a comment |
0
0
0
Dummy Code snippet of problem statement:
Scheduler method
@Scheduled(fixedRate = 30000)
@Transactional(readOnly = true)
public void scheduledTask() {
TaskExecutor threadPool = ctx.getBean(TaskExecutor.class);
long totalCount = someDao.someOperation("argument");
Runner runner;
for (int offset = 0; offset < totalCount; offset += 50) {
runner = ctx.getBean(Runner.class);
runner.setOffset(offset);
threadPool.execute(runner);
}
}
Runnable Implimentaion
@Component
@Scope(scopeName="prototype", proxyMode=ScopedProxyMode.TARGET_CLASS)
@Transactional
public class Runner implements Runnable {
private Integer offset;
private Integer limit;
private ISomeDao someDao;
public Runner(ISomeDao someDao) {
this.someDao = someDao;
}
public void setOffset(int offset) {
this.offset = offset;
this.limit = this.offset + 50;
}
@Override
public void run() {
List<Operation> operations = someDao.fetchData(offset, limit, someCriteria);
///
/// other business logic
}
}
Problem that i am facing:
In scheduledTask, program set the value of offset correctly(check in debug mode),
but it is not accessible in run method of the Runner class, offset it always null.
When i remove the spring annotation from Runner class and instantiate it mannuly in
scheduledTask then i can access the offset value, but it will throw exception as
there is no transaction manager available which is expected.
I also tried to inject the EntityManger in the
runner = ctx.getBean(Runner.class, ctx.getBean(EntityManager.class);
in the scheduledTask
when i remove the Spring annotation, but the problem remain the same as Thread is not managed by Spring
I have spent hour finding the solution.
spring spring-boot spring-data-jpa
asked Jan 1 at 7:54
Deepak KumarDeepak Kumar
286
Dummy Code snippet of problem statement:
Scheduler method
@Scheduled(fixedRate = 30000)
@Transactional(readOnly = true)
public void scheduledTask() {
TaskExecutor threadPool = ctx.getBean(TaskExecutor.class);
long totalCount = someDao.someOperation("argument");
Runner runner;
for (int offset = 0; offset < totalCount; offset += 50) {
runner = ctx.getBean(Runner.class);
runner.setOffset(offset);
threadPool.execute(runner);
}
}
Runnable Implimentaion
@Component
@Scope(scopeName="prototype", proxyMode=ScopedProxyMode.TARGET_CLASS)
@Transactional
public class Runner implements Runnable {
private Integer offset;
private Integer limit;
private ISomeDao someDao;
public Runner(ISomeDao someDao) {
this.someDao = someDao;
}
public void setOffset(int offset) {
this.offset = offset;
this.limit = this.offset + 50;
}
@Override
public void run() {
List<Operation> operations = someDao.fetchData(offset, limit, someCriteria);
///
/// other business logic
}
}
Problem that i am facing:
In scheduledTask, program set the value of offset correctly(check in debug mode),
but it is not accessible in run method of the Runner class, offset it always null.
When i remove the spring annotation from Runner class and instantiate it mannuly in
scheduledTask then i can access the offset value, but it will throw exception as
there is no transaction manager available which is expected.
I also tried to inject the EntityManger in the
runner = ctx.getBean(Runner.class, ctx.getBean(EntityManager.class);
in the scheduledTask
when i remove the Spring annotation, but the problem remain the same as Thread is not managed by Spring
I have spent hour finding the solution.
spring spring-boot spring-data-jpa
spring spring-boot spring-data-jpa
asked Jan 1 at 7:54
Deepak KumarDeepak Kumar
286
asked Jan 1 at 7:54
Deepak KumarDeepak Kumar
286
asked Jan 1 at 7:54
Deepak KumarDeepak Kumar
286
asked Jan 1 at 7:54
Deepak KumarDeepak Kumar
286
asked Jan 1 at 7:54
Deepak KumarDeepak Kumar
286
286
1
Did you try to use the default spring scope singleton? Does it work? If it work it means that in order to execute the job spring creates a new runner object where offset is not set
– Angelo Immediata
Jan 1 at 8:24
Agree with @AngeloImmediata. You need to try different scope to your bean. prototype will create different objects for different requests. So it might be the problem.
– Damith
Jan 1 at 10:07
@AngeloImmediata It works in default scope, but my requirement is prototype. Also I added debug point in Runner constructor to check how many time object is created and for every loop spring is creating 2 instance and when i comment out the runner.setOffset(offset) line in scheduledTask() , object is created only once. Is it expected behaviour in spring. With my understanding, in prototype scope new object is created by spring every time Bean is referenced, which in my case is runner = ctx.getBean(Runner.class); Am i wrong ?
– Deepak Kumar
Jan 1 at 10:08
It seems really strange to me that just executgingrunner.setOffset(offset)the object is created twice. With prototype scope creates a new instance every time the object is injected in other beans or thegetBeanmethod is used (docs.spring.io/spring/docs/current/spring-framework-reference/…). I guess there are 2 instances not for the setOffset but because the runner is injected in some way
– Angelo Immediata
Jan 1 at 10:33
add a comment |
1
Did you try to use the default spring scope singleton? Does it work? If it work it means that in order to execute the job spring creates a new runner object where offset is not set
– Angelo Immediata
Jan 1 at 8:24
Agree with @AngeloImmediata. You need to try different scope to your bean. prototype will create different objects for different requests. So it might be the problem.
– Damith
Jan 1 at 10:07
@AngeloImmediata It works in default scope, but my requirement is prototype. Also I added debug point in Runner constructor to check how many time object is created and for every loop spring is creating 2 instance and when i comment out the runner.setOffset(offset) line in scheduledTask() , object is created only once. Is it expected behaviour in spring. With my understanding, in prototype scope new object is created by spring every time Bean is referenced, which in my case is runner = ctx.getBean(Runner.class); Am i wrong ?
– Deepak Kumar
Jan 1 at 10:08
It seems really strange to me that just executgingrunner.setOffset(offset)the object is created twice. With prototype scope creates a new instance every time the object is injected in other beans or thegetBeanmethod is used (docs.spring.io/spring/docs/current/spring-framework-reference/…). I guess there are 2 instances not for the setOffset but because the runner is injected in some way
– Angelo Immediata
Jan 1 at 10:33
1
1
Did you try to use the default spring scope singleton? Does it work? If it work it means that in order to execute the job spring creates a new runner object where offset is not set
– Angelo Immediata
Jan 1 at 8:24
Did you try to use the default spring scope singleton? Does it work? If it work it means that in order to execute the job spring creates a new runner object where offset is not set
– Angelo Immediata
Jan 1 at 8:24
Agree with @AngeloImmediata. You need to try different scope to your bean. prototype will create different objects for different requests. So it might be the problem.
– Damith
Jan 1 at 10:07
Agree with @AngeloImmediata. You need to try different scope to your bean. prototype will create different objects for different requests. So it might be the problem.
– Damith
Jan 1 at 10:07
@AngeloImmediata It works in default scope, but my requirement is prototype. Also I added debug point in Runner constructor to check how many time object is created and for every loop spring is creating 2 instance and when i comment out the runner.setOffset(offset) line in scheduledTask() , object is created only once. Is it expected behaviour in spring. With my understanding, in prototype scope new object is created by spring every time Bean is referenced, which in my case is runner = ctx.getBean(Runner.class); Am i wrong ?
– Deepak Kumar
Jan 1 at 10:08
@AngeloImmediata It works in default scope, but my requirement is prototype. Also I added debug point in Runner constructor to check how many time object is created and for every loop spring is creating 2 instance and when i comment out the runner.setOffset(offset) line in scheduledTask() , object is created only once. Is it expected behaviour in spring. With my understanding, in prototype scope new object is created by spring every time Bean is referenced, which in my case is runner = ctx.getBean(Runner.class); Am i wrong ?
– Deepak Kumar
Jan 1 at 10:08
It seems really strange to me that just executging
runner.setOffset(offset) the object is created twice. With prototype scope creates a new instance every time the object is injected in other beans or the getBean method is used (docs.spring.io/spring/docs/current/spring-framework-reference/…). I guess there are 2 instances not for the setOffset but because the runner is injected in some way– Angelo Immediata
Jan 1 at 10:33
It seems really strange to me that just executging
runner.setOffset(offset) the object is created twice. With prototype scope creates a new instance every time the object is injected in other beans or the getBean method is used (docs.spring.io/spring/docs/current/spring-framework-reference/…). I guess there are 2 instances not for the setOffset but because the runner is injected in some way– Angelo Immediata
Jan 1 at 10:33
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%2f53993896%2fvalue-set-using-setter-method-in-runnable-implimentation-with-bean-scope-prototy%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%2f53993896%2fvalue-set-using-setter-method-in-runnable-implimentation-with-bean-scope-prototy%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
1
Did you try to use the default spring scope singleton? Does it work? If it work it means that in order to execute the job spring creates a new runner object where offset is not set
– Angelo Immediata
Jan 1 at 8:24
Agree with @AngeloImmediata. You need to try different scope to your bean. prototype will create different objects for different requests. So it might be the problem.
– Damith
Jan 1 at 10:07
@AngeloImmediata It works in default scope, but my requirement is prototype. Also I added debug point in Runner constructor to check how many time object is created and for every loop spring is creating 2 instance and when i comment out the runner.setOffset(offset) line in scheduledTask() , object is created only once. Is it expected behaviour in spring. With my understanding, in prototype scope new object is created by spring every time Bean is referenced, which in my case is runner = ctx.getBean(Runner.class); Am i wrong ?
– Deepak Kumar
Jan 1 at 10:08
It seems really strange to me that just executging
runner.setOffset(offset)the object is created twice. With prototype scope creates a new instance every time the object is injected in other beans or thegetBeanmethod is used (docs.spring.io/spring/docs/current/spring-framework-reference/…). I guess there are 2 instances not for the setOffset but because the runner is injected in some way– Angelo Immediata
Jan 1 at 10:33