I have not yet been able to reproduce it, but now that I have a Windows
7 VM setup, I'm going to try. Windows sysinternals has a program called
handle.exe which I have used for years in determining who is holding
file handles. If we could install this on our test machines and invoke
it after a failed test like this, we'd have a better shot at tracking
this down.
Jim
On 01/10/2013 06:34 AM, Alan Bateman wrote:
On 09/01/2013 19:46, Jim Gish wrote:
It's a Windows feature. We discovered this recently in debugging
another test failure. Windows is documented to do asynchronous
deletes. You can't depend on a file.delete() which returns true to
have actually deleted the file. It may be the case that another
process has a file handle which it has not yet released, or it's
simply a delay.
I don't get this, the issue sounds more like AV software or Windows
application quality service/agent thing accessing the file but I might
be wrong of course. Are you able to duplicate this reliably and if so,
have you looked at it with any tools to see what/who is accessing it
that is causing the delay?
-Alan.
--
Jim Gish | Consulting Member of Technical Staff | +1.781.442.0304
Oracle Java Platform Group | Core Libraries Team
35 Network Drive
Burlington, MA 01803
jim.g...@oracle.com
