It seems the number one issue with MX 6.1 is that it doesn't handle issues gracefully.

Whereas CF 5 would restart after x unresponsive requests (and that restart was fast). MX will never restart and problems appear to compound on top of each other, often rendering the server unresponsive, yet running.

While it also true that CF 5 often masked serious issues with that behavior, it also seems that the current situation isn't necessarily an improvement.

Just some random thoughts...

- Calvin
  ----- Original Message -----
  From: Mike Kear
  To: CF-Talk
  Sent: Sunday, November 02, 2003 6:54 PM
  Subject: Update: Memory Leak on Win2k/CMX6.1

  It looks as though we might at last have identified the culprit:   After our
  Sysadmin spent ages searching the forums about stalled servers, we thought
  it might be our mail server, since we're also getting mail issues.   So on
  Friday we stopped the SMTP server and left everything else alone.    Now on
  Monday morning, the sites are all still running fine - in fact they're
  running fast - and everything else seems to be operating normally.   I
  checked nervously a dozen times during the weekend and everything remained
  going well.

  So .. while the jury's still out, it doesn't look good for the SMTP server.

  More detailed information once we have finally determined that's the cause.

  Cheers,

  Michael Kear

  Windsor, NSW, Australia

  AFP Webworks.



  -----Original Message-----
  From: Mike Kear [mailto:[EMAIL PROTECTED]
  Sent: Saturday, 1 November 2003 5:44 PM
  To: CF-Talk
  Subject: RE: Memory Leak on Win2k/CMX6.1

  Well we have major issues with our server locking up every day.   EVERY Day.

  [snip]


[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]

Reply via email to