java.io.IOException: Couldn't get lock for

Question

Get error as

"java.io.IOException: Couldn't get lock for ..\log\abc.log", not sure why this happen.

Can somebody help me out? Thank you

        logger = LogManager.getLogManager().getLogger(className);
        FileHandler logFile = new FileHandler(file);

        // create txt Formatter
        SimpleFormatter formatterTxt = new SimpleFormatter();
        logFile.setFormatter(formatterTxt);         
        logger.addHandler(logFile);

Are you sure you can use ".." in the filename pattern? I've never seen that done before. — Dawood ibn Kareem, Nov 21 '13 at 02:57
I would assume that some other process already has the log file open...or you don't have permission to write to the location... — MadProgrammer, Nov 21 '13 at 03:01

score 6 · Answer 1 · edited Sep 19 '14 at 07:13

6

@Catheryan

I also had the same issue. For me issue was:

private static final String FILE_PATH="/home/jeril/Logs.log";
handler = new FileHandler(FILE_PATH);

FILE_PATH was WRONG

edited Sep 19 '14 at 07:13

SANN3

9,459
6
61
97

answered Jan 24 '14 at 09:41

Jeril Kuruvila

17,190
1
20
23

score 3 · Answer 2 · answered Aug 28 '15 at 21:23

This issue is a long standing bug in FileHandler (reported way back in March 2005, in Java 4):

JDK-6244047 : impossible to specify directories to logging FileHandler unless they exist

Quoting from the description of this bug:

If you specify a patern to the FileHandler that contains directories that don't currently exist then the FileHandler will fail to initialise even if the directories can be created

Its mentioned that it has been fixed in Java 8. For versions earlier than 8, the workaround is to either not use any directory in the pattern used for a FileHandler or use a directory which actually exists on the disk.

Checking if the folder exists and if not, creating it before using the file handler solved the problem! — RamValli, Apr 12 '18 at 11:15

score 2 · Answer 3 · answered Nov 21 '13 at 03:58

2

I think this is due to there being more than one instance of the logger that has it open or some other external application has it open with a read/write lock.

answered Nov 21 '13 at 03:58

Mukus

4,870
2
43
56

java.io.IOException: Couldn't get lock for

3 Answers3

Linked