Andrés González wrote:
Maybe a little OT, but: do you think it is a good "architecture" to
have such a background thread processing those records periodically?.
YMMV.
For me I have many jobs running, some timed on a regular schedule, some
timed and/or triggered from events (message passing),
Maybe a little OT, but: do you think it is a good "architecture" to
have such a background thread processing those records periodically?.
I mean, wouldn't it be preferable to create a separate process
(another JVM) which would execute that thread?
That way your design is more modular, and you can
Thanks,
I'm running tests on 2 machines and I'll share the results and concept in
case of sucess or ask for more help in case of failure. I'll stick to
starting background thread for now.
Thanks again,
Velja
Velja Radenkovic wrote:
I need to periodicaly (12 hrs) check few thousands of database records and
to perform some transactions. My first intention was to start a thread in
contextInitialized for this purpose. After searching the internet
(including
this mailing list), I'm in doubt. There are l
Velja Radenkovic wrote:
What I'm looking for are pros, cons and experiences for implementing
ServletContextListener and starting a thread in contextInitialized.
Thread
neads to perform 1 min processing every 12 hrs. Reliability is most
important aspect.
Google for MBean timer. You can also use
