Shutting down a persistant ap

Question

My mother-in-law's computer wasn't originally wireless so when she got a wireless cable modem I got a USB wireless unit for her. It works fine; signs on at start-up. The problem is that most times it won't quit when I choose to shut down. The shut down usually times-out. After the time-out all I have to do is quit the program and then shut down. The thing is, my mother-in-law isn't very good at if-thens. I can't leave her any dialog boxes, decisions or extra clicks.
My question is; is there anything I can do to force the program to comply and quit when she chooses "Shut Down?"
TIA,
Peter

Answer 1

Hi Sairam,
first you have to block producers.
Afterwards you can ensure that the write-behind queue is written out on all nodes by (optionally calling the flush method on the read-write backing map on each node e.g. from an Invocation and then) waiting for JMX showing that the write-behind queue is empty on each node.
Once there are no dirty entries in the wb queue, then you can just shut down consumers (anyone who reads from the cache).
After ensuring that no one wants to read from the cache, there is no point in having the data in the cache, therefore you can clear the caches with NamedCache.clear().
After this who cares that there is a redistribution of entry partitions.
No need to destroy() the caches, clear()-ing them is enough, except if you have backing map listeners which would hold up the execution of the clear() method.
Best regards,
Robert