Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
We’ve run into a big discussion with colleagues about using threads in web-applications in Java.
Their point is that it is not recommended to use threading in Java web applications because they are not managed by the container.
Generally, I’m OK with this, because threads may interfere with the container. But, what should one use instead of it if, for example, it is not a Java EE application but a simple servlet-app?
Using threads in a webapp is not a problem per se. It just depends why and how you use them. In particular, if you have 1000 users, and you start one thread for each of these users, you’ll bring the JVM to its knees.
But if threads are launched very raraely, for a specific, reduced set of users and use-cases, and if you use a thread pool to limit the number of such threads, you shouldn’t have any problem. It’s just important to understand what you’re doing.
Also, make sure to not pass a HttpServletRequest or HttpServletResponse object to such a thread, because they aren’t meant to be used by several concurrent threads, and they are not supposed to be used anymore once the request has been handled.