Pete,
I've had many recent incidences where, as it turns out, SNFclient.exe
takes 30 to 90 seconds to respond to every message with a result code
(normally less than a second), and as a result backs up processing.
Restarting the Sniffer service seems to do the trick, but I only tested
that
We were experiencing this several days ago and couldn't find a fix that
worked or worked for long. We uninstalled SNF and reinstalled and have not
detected a problem since. I will check the logs and report back if I see
anything intermittent.
Sent using SmarterSync Over-The-Air sync for
When we had sluggish performance similar that yours, resulting in numerous
sniffer .tmp files in the spool, the cause was eventually traced to a
proliferation of files in the sniffer directory. Clearing them out brought
performance back up to normal.
Darin.
From: e...@protologic.com
Sent:
Darin,
I'm not seeing that sort of thing. With 3.x, there doesn't appear to be
any extraneous file creation in the Sniffer program directory, and never
any TMP files in my spool. I do not have Sniffer modifying headers, so
that may be different on our systems.
Matt
On 6/27/2013 5:25 PM,
HI Matt,
We started having that problem coincidentally right after we upgraded to
3.x. For us the .tmp file creation in the spool was indicative of sniffer
processing delays. We do have Sniffer modifying headers.
Darin.
From: Matt
Sent: Thursday, June 27, 2013 5:32 PM
To: Message Sniffer
unsubscribe
_
From: Message Sniffer Community [mailto:sniffer@sortmonster.com] On Behalf
Of e...@protologic.com
Sent: Thursday, June 27, 2013 3:18 PM
To: Message Sniffer Community
Subject: [sniffer] Re: Slow processing times, errors
We were experiencing this several days ago and
This is an automated message from the mailing list software. In order
to unsubscribe you must issue the command please unsubscribe.
#
This message is sent to you because you are subscribed to
the mailing list
On 2013-06-27 17:25, Darin Cox wrote:
When we had sluggish performance similar that yours, resulting in
numerous sniffer .tmp files in the spool, the cause was eventually
traced to a proliferation of files in the sniffer directory. Clearing
them out brought performance back up to normal.
On 2013-06-27 16:04, Matt wrote:
like this:
20130627155608, arg1=F:\\proc\work\D6063018a2550.smd : Could
Not Connect!
That is SNFClient giving up after waiting for SNF to process the message
for too long.
At the same time, my Sniffer logs start showing frequent
ERROR_MSG_FILE
