Hi there, we are currently facing some deployment problems with WebObjects-Applications which most probably has the reasons in our (very big) running WebObjects-Configuration. While thinking about how we start fixing the problem, i faced the following question:
Why is the complete SiteConfiguration of every application and every instance shared with every application server? I just checked the code of JavaMonitor. All default actions like addInstance, updateInstance and so on are sent to EVERY configured application host. And i'm wondering if it wouldn't be enough that every application server only knows about the instances configured to run on itself. Like its now the SiteConfiguration can grow very large. A synch-request which is triggered by the monitor in error cases is then taking a very long time to compute in the wotaskd which leads to configuration read problems in the adaptor. And then another thing. In the default implementation of the GracefulBouncer, the requests for updating scheduling and so on are only sent to the hosts which have instances configured for the current application. Why are these updates not sent to EVERY application server? I'm very interested in your thoughts on this topic. -- Mit freundlichen Grüßen / Kind regards Paul Dunkler
signature.asc
Description: Message signed with OpenPGP using GPGMail
_______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to [email protected]
