"Ivanco, Maros" wrote:
>
>
> After the web-application starts, it should start too and periodicly
> send some reports to some mail addresses.
>
> I believe, the Application server thread can be better and faster (?)
> solution than NT service. Am I right? And if so, is there any way to
> automaticly start new thread after web-app starts and any way to destroy
> the thread when the web-app is destroyed? In WAS? In Tomcat?
>
Short answer: Don't use servlets for this, that's not what
servlets are for (but if you've got a fancy application server,
it might provide you with an application-server-specific way
to get what you want)
Longer answer:
http://www.distributopia.com/servlet_stuff/background_threads.txt
The above link doesn't mention the additional problem that
you may not be able to assume that spawned threads can have
access to your session (since the session is only guaranteed
to exist while one of your servlets is being called)
Good luck.
--
Christopher St. John [EMAIL PROTECTED]
DistribuTopia http://www.distributopia.com
___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".
Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
