Jazz Forum Welcome to the Jazz Community Forum Connect and collaborate with IBM Engineering experts and users

Build - Could not acquire lock on *\.jazz5\.jazzlock

Hello,

Very new to RTC and I am trying to get some CI set-up. It looks like the there is a jazz lock file in my build workspace causing an issue.

any ideas?

2010-10-04 13:50:57 running on host: DENDWEBEPOTLS01
2010-10-04 13:50:57 Should build occur?
2010-10-04 13:50:57 Yes: Always build a user initiated request.
2010-10-04 13:50:57 Invoking pre-build participant "com.ibm.team.build.jazzscm"
Accepting changes into workspace "DTP CI" ...
Fetching files to fetch destination "\dendwebepotls01\dtp_temp" ...
com.ibm.team.build.internal.scm.SourceControlUtility$2: Status ERROR: com.ibm.team.filesystem.client code=209 Copy file area locked by another process. Could not acquire lock on \dendwebepotls01\dtp_temp.jazz5.jazzlock null
at com.ibm.team.build.internal.scm.SourceControlUtility.updateFileCopyArea(SourceControlUtility.java:365)
at com.ibm.team.build.internal.engine.JazzScmPreBuildParticipant.preBuild(JazzScmPreBuildParticipant.java:193)
at com.ibm.team.build.internal.engine.BuildLoop.invokePreBuildParticipants(BuildLoop.java:628)
at com.ibm.team.build.internal.engine.BuildLoop$2.run(BuildLoop.java:466)
at java.lang.Thread.run(Thread.java:619)

0 votes


Accepted answer

Permanent link

Hi

Are you creating a repo workspace for the "build" user to work on? Is \dendwebepotls01\dtp_temp a workspace owned by the build rather than using your own workspace? Generally, the build user grabs the files from the stream and loads them into their own workspace and runs the build. Set the build to access the build user's workspace.

If this is the build workspace - any chance you have overlapping builds (build not completed before you try and start the new one).

anthony

David Lafreniere selected this answer as the correct answer

1 vote

Comments

This answer is old, and was never replied to. The questions that were posed by Anthony would help in identifying the correct answer however and thus I am marking this as the accepted answer.
This issue happens if another SCM daemon is running at '\dendwebepotls01\dtp_temp'.
This can happen if different builds are running on the same machine and both trying to load to the same directory, or if a user is using an RTC client (Eclipse, CLI, etc.) and has also loaded to that same directory.

Your answer

Register or log in to post your answer.

Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.

Search context
Follow this question

By Email: 

Once you sign in you will be able to subscribe for any updates here.

By RSS:

Answers
Answers and Comments
Question details
× 562

Question asked: Oct 04 '10, 4:31 p.m.

Question was seen: 7,793 times

Last updated: Oct 10 '17, 11:58 a.m.

Confirmation Cancel Confirm