It's all about the answers!

Ask a question
QuestionsTagsUsersBadges
Guidelines | FAQ
Follow this question
Question details

×42,884
×10,917
×1,201
×127
×4

question asked: Oct 28 '14, 8:43 a.m.
question was seen: 4,652 times
last updated: Oct 12 '17, 12:52 p.m.

Related questions

" Team ->Share project " Custom implementation deadlock issue , eclipse client not responding (suspended)

0
Linu Chacko (1●1●1) | asked Oct 28 '14, 8:43 a.m.
edited Nov 12 '14, 2:54 p.m. by Krzysztof Kaźmierczyk (7.5k●4●80●103)
Hi, We have a custom implementation for sharing projects from sandbox to repository. (called "Auto-share") However this custom auto-share implementation goes into a deadlock with
one of the IBM operation "Updating out of sync share".

To fix this deadlock issue we had to remove the below code from our custom
implementation. 

// Obtain the CFA lock so metadata updates will happen in-thread

AbstractLock lock = CFALockUtil.lockExistingForGlobalUpdate(entry.getKey(), progress.newChild(1));


Is the above code mandatory while sharing projects ? Do you foresee any issues?
Do we have any documentation for the same?

(Our tests indicates most the use cases to be working, but wanted an expert
opinion on the same.)


Thanks and regards
Linu Chacko









Accepted answer

1
permanent link
Michael Valenta (3.7k●3) | answered Nov 13 '14, 1:25 p.m.
FORUM MODERATOR / JAZZ DEVELOPER
edited Oct 12 '17, 12:52 p.m. by David Lafreniere (4.8k●7)

Linu,

This code is internal to the SCM API and should not be called by 3rd parties. You shouldn't need to call this as the proper locking should be done through the SCM API you are calling to share projects.

David Lafreniere selected this answer as the correct answer

Your answer

Register or 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.