What can cause a gap between RTC Work Item IDs?
![]()
We've noticed that a Work Item ID for new Work Item does not always follow sequentially from the last created Work Item. We just had a case where we created a Work Item (ID was 16928), rebooted the RTC server, and the next Work Item created had an ID of 17001. Why this gap in IDs? Is this to be expected after a reboot?
We're running RTC 5.0.1, using Tomcat, and an Oracle database, Linux server.
|
2 answers
![]()
Geoffrey Clemm (30.1k●3●30●35)
| answered Jun 03 '15, 8:55 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
I vaguely recall that there are parts of the system that allocate a "batch" of ID's, so they don't have to keep asking the server for a new ID one-by-one. The important qualifier here is "vaguely recall" (:-).
|
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.