IMHO, CFMail and the associated underpinnings are the most fragile part of
ColdFusion.

CFMail doesn't do a very good job in getting the mail to the SMTP box, often
it claims that the mail server is not available and shoves it in to
undeliver, to never be seen again - I guess a script could be written and
implemented to put it back in to spool - but I know I've had CF flake out
when I've done this manually.

I'll send a two pound box of David's cookies (mmmmm mmmmm good) as a gift if
somebody can figure out a way of making cfmail behave well enough to send
out 15,000 customized emails without puking on linux.

Tim Storm
FatWallet.Com


----- Original Message -----
From: "Tobe Goldfinger" <[EMAIL PROTECTED]>
To: "CF-Linux" <[EMAIL PROTECTED]>
Sent: Tuesday, November 27, 2001 1:49 PM
Subject: Linux/CF5 - is mass cfmail a problem?


> I'm starting to think it's not the CF Scheduler per se that's crashing the
> system (see below), but one of the scheduled jobs itself.
>
> Is there a known problem in a Linux/CF5 environment with having a program
> send out a lot of CFMail? (This stuff works fine in Win2k)
>
> tia,
> Tobe Goldfinger
>
>
>
>
> ------------------------------------------------
> Earlier today--------
>
> First: a little background----
>
> I have a client who very recently moved an app from Win2k/CF4.5 to
> Linux/CF5 (both using the same MSSQL db.) With probably only modest
> testing, he decided it was working and went live with the Linux version.
> (fyi--- I just inherited this app written by someone else so I know very
> little about the code)
>
> Now: the problem-----
>
> Yesterday I get reports that people's sessions are timing out every few
> minutes in spite of what the CFAdmin/CFApplication settings are for
session
> timeouts. I track the session timeout issue down to the point where it's
> clear that the problem is that the CFServer is restarting every few
minutes.
>
> Here are some server log entries.
>
> "Information","1024","11/26/01","18:26:23",,"The ColdFusion Application
> Server was stopped."
> "Information","1024","11/26/01","18:29:17",,"The ColdFusion Application
> Server started."
> "Fatal","7175","11/26/01","18:30:02",,"Caught a fatal signal (11) -
> Aborting"
> "Information","1024","11/26/01","18:30:04",,"The ColdFusion Application
> Server started."
>
> We have TONS of these fatal signal(11) / server restarting messages....
> every few minutes.
>
>
> Then I take a look at the scheduled jobs....... look at these log entries:
>
> "Information","4101","11/26/01","18:30:02",,"Scheduled task
> 'Task1' for URL request
> 'http://xxx.net/event1/event.cfm' initiated."
> "Information","5126","11/26/01","18:30:02",,"Scheduled task
> 'Task2' for URL request
> 'http://xxx.net/event2/expire/index.cfm' initiated."
> "Error","7175","11/26/01","18:30:02",,"Status code for task:
> 'Task1' is '500 Internal Server Error'"
> "Information","4101","11/26/01","18:30:02",,"Scheduled task
> 'Task1' for URL request
> 'http://xxx.net/event1/event.cfm' completed."
> "Information","5126","11/26/01","18:30:02",,"Scheduled task
> 'Task2' for URL request
> 'http://xxx.net/event2/expire/index.cfm' completed."
>
>
> It does seem to me that there's something about these scheduled jobs
that's
> crashing the server.
>
>
> So my question to the group is thus:
> a) does anyone have experience with the CF5/Linux scheduler..... good or
> bad to report
> b) could we bypass the scheduler entirely and use CRON to launch the batch
> jobs (if yes... plz supply specific details on how to get that to
work.....
> thx)
>
> tia,
> Tobe Goldfinger
> 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Your ad could be here. Monies from ads go to support these lists and provide more 
resources for the community. http://www.fusionauthority.com/ads.cfm
------------------------------------------------------------------------------
Archives: http://www.mail-archive.com/cf-linux%40houseoffusion.com/
To Unsubscribe visit 
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/cf_linux or send a 
message to [EMAIL PROTECTED] with 'unsubscribe' in the body.

Reply via email to