Printable View
Hello,
I wanted to use the api competitor for executing a task asynchronously, it is actually sending the mail after sending a form http. such as sending mail may take some time, I would return to the page and allow the sending of mail carried in a separate process, here is my code:
Code:Executor etor = Executors.newSingleThreadExecutor();
etor.execute(new Runnable() {
Public void run() {
MailManager.confirmCreation(Instance);
}
});
Hello,
I think the risks are not related to Executors in themselves, but rather to your code. Like any elements that could be used from multiple threads, ensure that everything is thread safe. Clearly he / she should have your code and well on all the objects that are shared by your method (the parameter "instance" to start, but also any static data ...) I think you should think of an alternative for this.
Hi,
I think the risk is possible flooding when the threads providers give more tasks to process the thread executor can process sequentially, the queue grows bigger. But it is a particular case depends on the nature of tasks. Yes, even I agree at the above post, as he has mentioned you should look for an .alternative solution for this
Hello,
You must make sure that all this is thread-safe, meaning that all the shared elements are:
- use of thread-safe manner (see class documentation).
- immutable (String, Integer, etc..), because it implies the next thread-safe.
- manually synchronized with your code.
If all of this is implemented in your code, then to some extent your code will be safe.
Hello,
So this is not a solution to implement without taking into account the rest of the code, the goal was just returning control to the user and let the mail is processed by another thread. I must declare functions synchronized change in StringBuffer, StringBuilder and a little review of the principles of synchronization. If you guys can suggest me some other alternative then it will be appreciated. Thanks in advance.
Hello,
It depends heavily on your code and how you share data. Every sync is not necessarily the best solution either. You can also avoid the maximum sharing of data to work on local objects up to. There are many ways to do it, it depends on your needs, that is how you want your software or application to work. So, just read on this and then think which logic you will apply to your code.