I can't say for sure that we know/knew the limit before it would crash publishing, but one of my coworkers would just stay awake until 2-3am every night to make sure it was running with the "fixes" suggested by Reddot...none of them really worked 100%. It usually stopped working during our largest publishing job (broken down by department) and then wouldn't publish anything until we restarted the service or rebooted that particular server.
We also use clustering (we have 3 authoring and 3 publishing servers) but 1.91 didn't seem to adversely affect it as much as it did publishing in general. How many sites do you have? We currently have 4 How big are they? 2 are very big, 1 medium-sized, 1 smaller Are you using workflow publishing at all or just full overnight jobs? We are using workflow publishing for 2 of the projects (1 big and 1 smaller-sized) and every project has overnight jobs to catch anything that might've been missed (changes that do not kick off workflow). Hope this helps and gives you an idea of what to watch out for.. Let me know if you have any other questions. ------------------------------ ---------- Forwarded message ---------- From: Henry Lu, Sun Certified Java Programmer <[EMAIL PROTECTED]> Date: Sat, Sep 13, 2008 at 6:51 AM Subject: Re: Your favourite version of CMS 7.5? To: [email protected] Mike, What kind of size makes the memory overflow issue noticeable? The immediate patch to sql injection issues was 1.86 (I think) and that caused many users losing access to their projects (not neccessarily related to the com+ settings.) For a couple of days RedDot support were flooded with calls about 1.86 making their projects not accessible. They first recommend to guys who did not mind getting their hands dirty to manually modify iord.asp in order to achieve the patch then released 1.91 pretty swiftly. I have not noticed the publishing memory leak issues. Accidentally though, 1.91 fixed a lot issues I was having with CMS clustering. Whether that was really attributable to 1.91 is beyond my guess as I did not bother to dig it. I was just happy that the constant page caching and query timeout issue on 2 clustered CMS server disappeared after I installed 1.91 on both. Henry On Fri, Sep 12, 2008 at 10:44 PM, Searles, Mike S. <[EMAIL PROTECTED]> wrote: > I would avoid 7.5.1.91 like the plague..we were on it for 2 weeks when we > made the decision to go to .103 - to fix the publishing memory overflow > issues (as Pollo mentioned previously) that .91 caused. Apparently Reddot > was made aware of these types of issues with .91 just a day or two after we > upgraded and recommended .103 and we havent had issues since. Those issues > were not immediately apparent - but the size of our sites made it surface > within a week or so.... > > Hope this helps! > > On Fri, Sep 12, 2008 at 5:30 PM, El Pollo Loco <[EMAIL PROTECTED] > > wrote: >> >> The biggest thing about .103 is that there are new configurations in >> RedDotCMSServiceProcess.exe.config. >> >> A new implementation of managing the max memory of the >> RedDotCMSServiceProcess.exe is available. In versions prior to .103, >> it is possible (but unlikely) for this .exe to consume all available >> RAM and bring the server to a halt. >> >> And as far as upgrades in general, they should be tested in a DEV in >> environment first (like any other software), >> >> On Sep 12, 4:18 pm, "Henry Lu, Sun Certified Java Programmer" >> <[EMAIL PROTECTED]> wrote: >> > It is laughable in the ideal world. But in reality, you've got to >> > choose the lesser of the evils. >> > >> > And some of us do not have the luxury of laughing at it. >> > >> > On Fri, Sep 12, 2008 at 4:08 PM, Team Macromedia >> > >> > <[EMAIL PROTECTED]> wrote: >> > > Doesn't this whole thread reek of "WTF?!" Hotfixes/updates on all >> > > fronts of >> > > RedDot in my experience have been a nightmare - never tested, rarely >> > > fixing >> > > as many bugs as it creates. >> > >> > > The simple fact you talk about WHICH hotfix to use (sometimes >> > > infererior to >> > > the current release) is ludicrous. >> > >> > > 2008/9/12 Henry Lu, Sun Certified Java Programmer <[EMAIL PROTECTED] > >> > >> > >> I've not used 7.5.1.103. >> > >> > >> However, I will cast vote of confidence to 7.5.1.91. >> > >> > >> On Fri, Sep 12, 2008 at 11:51 AM, Jonathan W >> > >> <[EMAIL PROTECTED]> >> > >> wrote: >> > >> > >> > The README for the upgrade from 7.5.1.91 to 7.5.1.103 is as follows >> > >> > and seems to be a handful of relatively small bug-fixes, but who >> > >> > knows >> > >> > if they've introduced instability again? >> > >> > >> > * #14404 Converting to PDF in landscape only works with one page >> > >> > * #24439 DIN A5 is not saved when using ?Convert to PDF? >> > >> > * #24440 The defined format is ignored when using 2Convert to >> > >> > PDF? >> > >> > * #25631 Error with new pages in Translation Editor TLE when ?Do >> > >> > Not Translate? is selected >> > >> > * #26147 Errors when processing render tags cause messages in >> > >> > the >> > >> > event log if there are too many characters >> > >> > * #26543 When importing pages in navigation manager, >> > >> > disconnected >> > >> > pages are displayed in the page navigation >> > >> > * #26547 Setting ?Convert to PDF? in the project variant >> > >> > converts >> > >> > only the first page of a PDF document correctly >> > >> > * #26772 Possible RDCMS_XMLServer crashes have been corrected by >> > >> > using a new version of ImageMagick >> > >> > * #26774 Restricting Media elements (e.g. maximum file size) is >> > >> > not possible in CMS 7.5.1.32 and later >> > > > > > The information contained in this message and any attachment may be proprietary, confidential, and privileged or subject to the work product doctrine and thus protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify me immediately by replying to this message and deleting it and all copies and backups thereof. Thank you. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "RedDot CMS Users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/RedDot-CMS-Users?hl=en -~----------~----~----~----~------~----~------~--~---
