RE: Thread question

Ooops, I forgot that this is for Java on the iSeries.  This particular 
application isn't running on the iSeries.  In fact, due to certain 
changes, we won't have an iSeries in about 3 years... being phased out for 
Windows Servers.  Sorry for the mixup.  Does the same apply for that then?

Ron Power
Programmer
Information Services
City Of St. John's, NL
P.O. Box 908
St. John's, NL
A1C 5M2
709-576-8132
rpower@xxxxxxxxxx
http://www.stjohns.ca/
___________________________________________________________________________
Success is going from failure to failure without a loss of enthusiasm. - 
Sir Winston Churchill




"Walden H. Leverich" <WaldenL@xxxxxxxxxxxxxxx> 
Sent by: java400-l-bounces@xxxxxxxxxxxx
2006/06/21 04:27 PM
Please respond to
Java Programming on and around the iSeries / AS400 
<java400-l@xxxxxxxxxxxx>


To
"Java Programming on and around the iSeries / AS400" 
<java400-l@xxxxxxxxxxxx>
cc

Subject
RE: Thread question

Is this efficient to do?

Define "efficient." From a machine performance point of view, sure. The
sleeping thread won't take any machine resources so it's "efficient."
However, it's probably not how I'd do it. 

Don't forget you're still on an iSeries. Why not simply add something to
the job scheduler to run a job once a day to look for expiry dates? The
job could be either a "simple" RPG program or a java application. Why
make it a web application? If you need it to be a "Web" application I'd
still use the job scheduler and just use something like Brad's GetURI to
kick off the web page needed to invoke the process. What's starting the
sleeping thread? What restarts it on application start?

-Walden