That sort of beats the whole purpose of the whole concept of having server groups though. When working like it should, the secondary servers 'do not know' about the def changes that have occured due to changes made from the primary server, until the new cache on the primary server has been recreated, and the primary server then signals the secondary servers that there has been a change...
When properly setup it does work as designed. Anthony, are all your servers in the server group of the same configuration, and running the same applications? What is the physical memory on the servers? Joe ________________________________ From: Lyle Taylor <tayl...@ldschurch.org> To: arslist@ARSLIST.ORG Sent: Tuesday, February 24, 2009 2:20:43 PM Subject: Re: ARS 7.1 server group issue ** While AR is supposed to support it, in my experience it is best to shut down everything but the primary server, make your changes, and then bring everything back up again. Things just go more smoothly that way. Lyle From:Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of Anthony K R Sent: Tuesday, February 24, 2009 11:37 AM To: arslist@ARSLIST.ORG Subject: ARS 7.1 server group issue ** Hi, In Remedy server group environment, when the def changes on primary server other servers either throw malloc error ( so the updates not reflected) or crash. Anyone seen this? Env: ARS 7.1 patch 5 with ITSM 7.0 suite Windows 2003 Oracle 10g Thanks, Anthony _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: RMI Solutions ARSlist: "Where the Answers Are"
