Re: mutithreading in webapps

From:

=?ISO-8859-1?Q?Arne_Vajh=F8j?= <arne@vajhoej.dk>

Newsgroups:

comp.lang.java.programmer

Date:

Sun, 05 Aug 2007 16:49:46 -0400

Message-ID:

<46b637ea$0$90269$14726298@news.sunsite.dk>

ameyas7 wrote:

It is legal according to the spec to start multiple threads, so
you could:
   - web request comes in
   - you start N threads
   - you wait to all threads are done
   - web response go back out

But if it takes a long time, the the browser will consider
it a timeout.

So it is not a problem whether multi threading will work in Tomcat - it
is a question whether it is a good way of solving the problem.

well my web request will not be waiting till the job is done.
it is actually a notification service, ppl will keep posting it and
then it will pick up all queued requests and notify the recepients
(say by mail or other means)
so the web response is not blocked on the completion of the worker
thread.

If you could upgrade from a servlet container (Tomcat) to a full
J2EE application server (like JBoss with Tomcat embedded as servlet
container), then you could:
   - web request comes in
   - servlet queue task to message queue
   - web response go back out
   - a message driven bean process the input from the message queue

Your solution will also work, but I believe the above is "the J2EE way".

Arne