Community
Participate
Working Groups
Build Identifier: 1.2.0.201112221803-r On an OpenVMS 8.4 (IA64) on which JAVA 1.6.0-3.p1 is installed I get the following error when I try the merge command of jgit: bolero-jj) jgit version jgit version 1.2.0.201112221803-r bolero-jj) jgit fetch remote: Counting objects: 13 remote: Compressing objects: 100% (7/7) Receiving objects: 100% (7/7) Resolving deltas: 100% (6/6) Updating references: 100% (1/1) remote: Total 7 (delta 6), reused 0 (delta 0) From git://git.jedsoft.org/git/jed.git 31f10a9..7a116fe master -> origin/master bolero-jj) jgit merge "origin/master" org.eclipse.jgit.api.errors.JGitInternalException: Exception caught during execu tion of merge command. java.io.IOException: Cannot lock /$disk6/JOUKJ/git/jed/je d/.git/index at org.eclipse.jgit.api.MergeCommand.call(MergeCommand.java:260) at org.eclipse.jgit.pgm.Merge.run(Merge.java:85) at org.eclipse.jgit.pgm.TextBuiltin.execute(TextBuiltin.java:148) at org.eclipse.jgit.pgm.Main.execute(Main.java:191) at org.eclipse.jgit.pgm.Main.run(Main.java:120) at org.eclipse.jgit.pgm.Main.main(Main.java:94) Caused by: java.io.IOException: Cannot lock /$disk6/JOUKJ/git/jed/jed/.git/index at org.eclipse.jgit.dircache.DirCache.lock(DirCache.java:193) at org.eclipse.jgit.dircache.DirCache.lock(DirCache.java:239) at org.eclipse.jgit.lib.Repository.lockDirCache(Repository.java:873) at org.eclipse.jgit.api.MergeCommand.call(MergeCommand.java:181) ... 5 more Reproducible: Always Steps to Reproduce: 1.jgit fetch 2.jgit merge "origin/master" 3.
Does a index.lock file exist in the /$disk6/JOUKJ/git/jed/jed/.git directory?
Yes, index does exist Note that file access on an OpenVMS system is quite different from i.e. linux: If you open a file, by default it is locked for all other use, except when you explicitly open it as "shared". My guess is that the file is already in use by some other instance of jgit.
I deleted the index.lock file manually. After that the merge command worked. the index.lock file was created when I did the original "clone" of the repository.
can we close this bug ?
Still the only work-around is deleting the index.lock manually. Is this going to be solved? Jouk