[IVY-1489] Still seeing *.lck files if ivy is aborted abruptly

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Not A Problem
• Affects Version/s: 2.3.0

Environment

Linux sauron 3.13.0-36-generic #63-Ubuntu SMP Wed Sep 3 21:30:07 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
java version "1.7.0_67"
Java(TM) SE Runtime Environment (build 1.7.0_67-b01)
Java HotSpot(TM) 64-Bit Server VM (build 24.65-b04, mixed mode)

• Assignee: Unassigned
• Reporter: Shawn Heisey
• Created: 04/Oct/14 05:07
• Updated: 02/Nov/17 03:33
• Resolved: 02/Nov/17 03:33

Description

IVY-1388 is still happening after upgrading to 2.3.0.

For me, this is seen when building the lucene-solr project. Frequently after starting a build I will realize that I've typed the ant command line wrong, or that I haven't fixed a problem correctly, so I will use ctrl-c to abort the build, fix the problem, and start it back up. Often the interruption will result in a .lck file being left behind and the build hanging at "resolve:" until the .lck file is deleted.

Issue Links

• is related to: IVY-1388 *.lck files created by "artifact-lock" lock strategy are not cleaned up if ivy quits abruptly
• is related to: LUCENE-6144 Upgrade ivy to 2.4.0