A fix is available
APAR status
Closed as program error.
Error description
DRS/CM: RCR apply timed out during conflict detection DOORS: 9304 Change: 5204 DWA: 1404 The Change team had previously supplied this customer (Hung-Chih from Panasonic) a test fix for this issue. Below are the logs as well as the response from the Hung-Chih. I finally got a chance this morning to try the timeout fix. Below are the logs: ========================= Before applying the fix: ========================= 08/03/11 19:11:41 P9: cleanupScopeRcrData--continueProcessRCR 08/03/11 19:11:41 getBeginModule(/PAW/Training Area/Sample module C)[000064c2]: begin module found. 08/03/11 19:11:41 Working and review RCRs query = oslc_cm:closed=false and oslc_cm:approved=false and oslc_cm:status!='rcr_closed' 08/03/11 19:11:41 prepareScopeRcrData(): 08/03/11 19:11:42 Validating url http://tlogic-socal06.mascorp.com:8600/change/oslc with user name chuangh 08/03/11 19:11:42 Arguments to OSLC QueryForCmObjects_New: 08/03/11 19:11:42 url = http://tlogic-socal06.mascorp.com:8600/change/oslc/db/30d54fdf-9 e91-461e -a821-6e02b7338298/role/User/cr 08/03/11 19:11:42 user name = chuangh 08/03/11 19:11:42 query string = oslc_cm:closed=false and oslc_cm:approved=false and oslc_cm:status!='rcr_closed' 08/03/11 19:11:42 query member name = changeRequest 08/03/11 19:11:42 if for RTC = 08/03/11 19:12:13 oleGet cmOslcApi.QueryForCmObjects error : OSLC request failed ========================= After applying the fix: ========================= 09/09/11 11:54:22 P9: cleanupScopeRcrData--continueProcessRCR 09/09/11 11:54:22 getBeginModule(/PAW/Training Area/New for 9.3 RCR practice)[000064c8]: begin module found. 09/09/11 11:54:22 Working and review RCRs query = oslc_cm:closed=false and oslc_cm:approved=false and oslc_cm:status!='rcr_closed' 09/09/11 11:54:22 prepareScopeRcrData(): 09/09/11 11:54:23 Validating url http://tlogic-socal06.mascorp.com:8600/change/oslc with user name chuangh 09/09/11 11:54:23 Arguments to OSLC QueryForCmObjects_New: 09/09/11 11:54:23 url = http://tlogic-socal06.mascorp.com:8600/change/oslc/db/30d54fdf-9 e91-461e -a821-6e02b7338298/role/User/cr 09/09/11 11:54:23 user name = chuangh 09/09/11 11:54:23 query string = oslc_cm:closed=false and oslc_cm:approved=false and oslc_cm:status!='rcr_closed' 09/09/11 11:54:23 query member name = changeRequest 09/09/11 11:54:23 if for RTC = 09/09/11 11:59:24 oleGet cmOslcApi.QueryForCmObjects error : OSLC request failed ========================= As you can see the timeout has been extend from 30 seconds to 5 minutes. So, the timeout extension does work as expected. However, due to the large (or huge) number of 'alive' RCRs in my Company's Change database, the OSLC request still failed even with 5 minutes timeout. So, here are what I am thinking: 1. I believe the 5 minutes timeout is already long enough (in fact, maybe too long). So, I think we should not consider extending it even further. 2. A better solution might be the query scope. Is it possible to narrow down the query for RCRs only associated with the target DOORS module? My company's Change database has around 6000 alive RCRs at any given time. However, there are only 2 or 3 alive RCRs associated with the target module. This solution will scale very well regardless the size (or the number of alive RCRs) of Change database. 3. Of course, in my side, we will try to see how to reduce the number of those alive outstanding RCRs. This will involve lifecycle and process changes in my company. And it won't happen very soon.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: * **************************************************************** * PROBLEM DESCRIPTION: * **************************************************************** * RECOMMENDATION: * **************************************************************** Queries that return a large number of RCRs causes the HTTP call to timeout and the OSLC request to fail after 5 minutes.
Problem conclusion
DOORS 9.3.0.6 updated the queries used by the Integration to return a smaller amount of RCRs, but with more HTTP calls. This should prevent HTTP calls timeout and OSLC request failures.
Temporary fix
Comments
This happens in versions of DOORS prior to DOORS 9.3.0.6
APAR Information
APAR number
PM47559
Reported component name
TLOGIC DOORS
Reported component ID
5724V61DR
Reported release
930
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2011-09-09
Closed date
2011-12-02
Last modified date
2011-12-02
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
TLOGIC DOORS
Fixed component ID
5724V61DR
Applicable component levels
R930 PSN
UP
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSYQBZ","label":"Rational DOORS"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"9.3","Line of Business":{"code":"LOB59","label":"Sustainability Software"}}]
Document Information
Modified date:
28 October 2021