Why is multithreading discouraged in a J2EE Servlet?

Asked Apr 17 '15 at 10:15

Active Apr 17 '15 at 10:31

Viewed 72 times

I've been reading about the forbidden Multithreading technique in a servlet. Anyway I don't get the problem, at least in what I was about to try.

I have a long process that needs to be quicker. It has plenty of DB select's (600ms each) to validate some data. I wanted to do concurrently these selects so the data could be validated.

My implementation would create some threads inside the treatment of the request to do the validations concurrently. After the data is validated for each thread (or not validated), after joining all of them to the main thread, I would kill each of these threads and give the answer to the client.

Could you explain me why this is discouraged? Any suggestion?

Thanks!

edited Apr 17 '15 at 10:31

Andrew Ferrier

13,902
11
40
73

asked Apr 17 '15 at 10:15

Pahgo

1

Also see this answer: http://stackoverflow.com/a/19404307/1257372. – Nick Wilson Apr 17 '15 at 10:24
1

You shouldn't do this in *regular* Java. This is exactly what executors are for. – chrylis -cautiouslyoptimistic- Apr 17 '15 at 11:12
I will add that while the marked duplicate is worth reading, the answer indicated by @NickWilson is more up to date if you're using a Java EE 7 platform – Steve C Apr 17 '15 at 12:57

Why is multithreading discouraged in a J2EE Servlet?

0 Answers0