Re: blat process freezing intermittently

Hi Mike,

Thanks for the tip. I do create the tmpfile shortly before calling blat so
that gives me some direction on where to look.

Adam

On Wed, Mar 29, 2017 at 4:01 PM, 'Mike Mattos' [email protected] [blat] <
[email protected]> wrote:

>
>
> Not specific to blat, but I have encountered errors lately with newly
> created files not being available to calling processes, and the calling
> process fails.
>
>
>
> Example:  A database query creates a text file, and blat tries to send the
> file, but fails.  However, it isn’t so much file not found as it is that
> the file locking fails.  No idea why but it seems to happen at random work
> stations perhaps 1 in 500 times.
>
>
>
> This isn’t new, but seems to be more frequent than a few years ago.
>
>
>
> Mike Mattos
>
>
>
> “To succeed in the world it is not enough to be stupid, you must also be
> well-mannered”
>
> Voltaire
>
>
>
> *From:* [email protected] [mailto:[email protected]]
> *Sent:* March 29, 2017 9:21 AM
> *To:* [email protected]
> *Subject:* [blat] blat process freezing intermittently
>
>
>
>
>
> I use blat at my job in scripts to FTP files. We've been using blat for
> years without any issues until recently. We are starting to see our script
> jobs hang intermittently when they execute a blat process. I've modified
> the parameters to capture the debug output but I'm not getting any useful
> information. These scripts run upwards of 100 times a day and we only see
> this once every few days. This is running on 64-bit Windows 7 Enterprise
> OS. Here is an example of what I'm seeing in the log file:
>
>
>
>
>
> blat tmpfile -s "subject" -t "recipient" -log debugfile -debug -timestamp
>
>
>
> 2017.03.28 12:30:12 (Tue)------------Start of Session-----------------
>
> Blat v3.1.2 (build : Dec 27 2013 14:33:12)
>
> 32-bit Windows, Full, Unicode
>
>
>
>
>
> I have verified that the debug output is correct when the blat process
> runs successfully. I haven't upgraded to the current version because I was
> hoping to identify the root cause first. What are next steps for
> troubleshooting?
>
> 
>