cfmail message spooling once, sending twice

[gkyle001CF]

Hi there

For the last few weeks, one of my CF instances has started sending outgoing emails twice.  For the last few years, the pages have sent one copy only, but now they are sending out 2 copies of each message.  A second instance, running the identical page (from a different domain) only sends one copy of each message.

Even a simple, hardcoded <cfmail> tag, with nothing else on the page whatsoever, is sending twice.

I have confirmed through logs and tests that

- the cfmail tag runs only once

- only 1 physical message is added to the /Mail/Spool/ folder

- 2 identical messages are logged in the mailsent.log

- 2 emails are delivered

I have confirmation that the outgoing mail server is receiving 2 commands to send each message

As mentioned, the exact same page, run on instance 1 results in 2 messages and run on instance 2 results in 2 messages.

I have had confirmation that 2 copies of the first instance are not running at the same time.

Make any sense at all?

Any help would be appreciated greatly

[Adam Cameron. · Accepted solution]

Sounds to me like you've got two JRun instances running (somehow), and both are running a mail watcher on the same spooler dir.  Or something like that.

Do you have an extra jrun process running?

--

Adam

[gkyle001CF]

Thanks very much for the response Adam.

In jRun Management, there is only one copy of the specific instance running.  I tried stopping and restarting it with no change.

There are 5 instances overall in jRun.  main, plus 3 production instances, all running and a 5th instance which is not running.

In Task Manager > Processes, there are 5 jrun.exe processes running.  Is that one for each instance, whether the instance is running or not?  Or should there only be 4 processes, for each "running" instance.

Any further help is greatly appreciated.

[Owainnorth]

What does the cfmail.log say? And what do the logs from your SMTP engine say?

[gkyle001CF]

The cf mail.log wasn't saying anything.  The mailsent.log was logging 2 of all messages.

The smtp log on the mail server was showing unique ID's for each of the messages.

[Owainnorth]

gkyle001CF wrote:

The cf mail.log wasn't saying anything.  The mailsent.log was logging 2 of all messages.

The smtp log on the mail server was showing unique ID's for each of the messages.

Ah, at least you know it's a CF issue not an SMTP one then.

[Adam Cameron.]

There are 5 instances overall in jRun.  main, plus 3 production instances, all running and a 5th instance which is not running.

In Task Manager > Processes, there are 5 jrun.exe processes running.

OK, so from that... you've got an extra JRun instance running... you're only expecting four to be running (one of the five is not supposed to be running) but you have five JRun.exe processes running.

I dunno if there's a way to identify which process ID belongs to which JRun instance (that's not to say there isn't one, but I just don't know it), but it sounds like you've got a clustered / load-balanced environment so it should be OK to restatr each in turn, and find out which is the bogus one.  Note the PIDs of each jrun.exe process, then restart each of your JRun instances in turn... each time they'll get a new PID. After doing that, there'll be one jrun.exe PID which has not changed... that'll be the dodgy one.  Kill it.

I've seen this sort of thing happen - albeit only in DEV - where the jrunsvc.exe process gets muddled up, and tries to restart its jrun.exe process, and the STOP fails but the START succeeds, meaning there's now two jrun.exe processes running.  usually the one that failed to stop has hung, but I guess perhaps it might have just been unresponsive for a bit, but then recovered.  Or something.

This is entirely speculation, obviously.

--

Adam

[gkyle001CF]

Thanks again for the replies and suggestions.

I still need to look into the fact that there are 5 jrun.exe processes running.  I tried stopping one of the running instances and there were still 5 jrun.exe instances running however.

Oddly though, for the last 7 hours, no duplicates were sent out.  Now, as of a few minutes ago, the duplicates have started again.

[gkyle001CF]

Thanks very much Adam.  It was indeed an extra jrun.exe process running for some reason.