Max number of locked source/files on the same components
![]()
ryosuke oka (179●8●46●48)
| asked Aug 26 '13, 2:15 a.m.
edited Oct 10 '17, 2:14 p.m. by David Lafreniere (4.8k●7) Version: Rational Team Concert 4.0.1(Enterprise Extension)
|
Accepted answer
![]()
Geoffrey Clemm (30.1k●3●30●35)
| answered Sep 16 '13, 9:20 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER edited Sep 16 '13, 11:27 p.m.
I did some exploring on this issue. Based on my experiments, there is no limit to the number of locks that you can apply in a component, but there are issues in the code that is used to retrieve those locks. In particular, the Eclipse client appears to only display around 512 of those locks in displays like the Package Explorer. I've reported that problem in If more than than 512 files are locked in a component, only about 512 locks are shown in the Eclipse package explorer (280745) .
David Lafreniere selected this answer as the correct answer
Comments Thank you for checking on this issue, Geoffrey!
Note: What Goeffrey explained above was the correct observed behavior. The issue was that the server API did not support paging, and so by default it just returned 512 locks. The defect that he mentioned (Defect 280745) was fixed and delivered for RTC 4.0.6. This introduced an advanced server property called 'Maximum number of locks returned from query' which would allow a larger number to be returned (but there still would be a maximum).
|