Hi Paul;
If your deployment is large enough to justify it, you could use a
messaging service (JMS) to message each instance to change the state?
This avoids having to do the extra database trip on each login but
maybe too much complexity if you don't have the need for a messaging
broker anyway.
cheers.
Is a scheduled re-start via JavaMonitor a hard re-start? In
particular, is Properties re-read? (I should be able to answer
this myself in about 8 hours...) Ideally, I want the semantics
here to be "disallow logins on first launch, not again after every
scheduled re-start". Is there any way to persist this kind of
state across a scheduled re-start? (If all else fails, I can use
the database, of course.)
...
Yes, it is a hard restart. The JVM terminates and a new process
starts. You will need to use the database.
___
Andrew Lindesay
www.lindesay.co.nz
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [email protected]
