I have a question:
Why when we annotate method with @Scheduled
and @Transaction
, transaction doesn't work?
I know that the @Scheduled
call my class instead of proxy class that created by Spring, but can't understand this behavior.
import org.springframework.scheduling.annotation.Scheduled;
import org.springframework.transaction.annotation.Transactional;
@Service
public class UserServiceImpl implements UserService {
@Override
@Scheduled(fixedRateString = "${somestring}",initialDelayString = "${anotherstring}")
@Transactional
public void doSomething() {
}
}
I have two solutions of this problem:
Call proxy from Scheduled
method.
Implement ConcurrentTaskScheduler
and replace object of ScheduledMethodRunnable
(that is with my class)
with object of ScheduledMethodRunnable
with proxy.
But this solutions is very inconvenient.
Can you explaim me why @Scheduled
works like this?
Thank you!
We can turn any method in a Spring bean for scheduling by adding the @Scheduled annotation to it. The @Scheduled is a method-level annotation applied at runtime to mark the method to be scheduled. It takes one attribute from cron , fixedDelay , or fixedRate for specifying the schedule of execution in different formats.
Note that scheduled tasks don't run in parallel by default. So even if we used fixedRate, the next task won't be invoked until the previous one is done. Now this asynchronous task will be invoked each second, even if the previous task isn't done.
The @Transactional annotation is metadata that specifies that an interface, class, or method must have transactional semantics; for example, "start a brand new read-only transaction when this method is invoked, suspending any existing transaction".
It happens because to process both annotations MAGIC is used.
I suppose there are several things happens:
UserServiceImpl
is created.@Scheduled
annotation is processed and reference to bean is stored to invoke it at appropriate time.@Transactional
annotation is processed. It create proxy which store reference to original bean. Original bean is replaced to proxy in application context.If step 2 and 3 passed in different order then you had no problem.
I don't know how to control order in which annotation is processed. I don't even sure it is possible at all.
There is basically two solution.
@Transaction
. Default way is to create proxy object, but it is possible to instruct Spring
to instrument current class.Example:
@Service
public class UserServiceImpl implements UserService {
@Override
@Transactional
public void doSomething() {
}
}
@Service
public class UserServiceScheduler {
@Inject
private UserService service;
@Scheduled(fixedRateString = "${somestring}",initialDelayString = "${anotherstring}")
public void doSomething() {
service.doSomething();
}
}
I'm personally recommend second approach.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With