It's all about the answers!

Ask a question

Is there a limit on the number of results (requirements) that can be fetched from RRC?


VIJAY SUNDARESHWARAN (25247) | asked Apr 05 '13, 1:11 p.m.
retagged Apr 05 '13, 5:06 p.m. by Suzanne Swierkowski (1862)
 I have about 750 to 800 requirements in my project in Rational requirements Composer. I am trying to upload test cases for these requirements in Rational Quality manager (RQM) using the RQMWordExceImporter utility. 
While doing the upload, I try to link the test cases to existing requirements which are fetched from RRC.

This requirements fetch works fine for lesser number of requirements example: around 300-400. 
But when the number of requirements increases (to the order of 500s and 600s), i start seeing the following error:


Is there any limit on RRC, for the number of requirements that can be fetched by the client. In this case, the RQMExcelWordImporter Utility?
Is there any configuration setting that can be modified to return all the requirements from RRC?

Please advice!!

5 answers



permanent link
Diane Everitt (27835) | answered Jun 20 '13, 11:53 a.m.
It has been identified that this is a limitation of RM OSLC REST API as
there is, in fact, no timeout option provided by the RM server when
querying the requirement url.

An enhancement request has been submitted to use pagination:

https://jazz.net/jazz02/web/projects/Rational%20Quality%20Manager#action=com.ibm.team.workitem.viewWorkItem&id=88033

permanent link
Stephane Leroy (1.4k149) | answered Apr 08 '13, 4:45 a.m.
JAZZ DEVELOPER
Hi Vijay,

I'm not aware of such limit.  I presume you're using CLM 4.0.1 :
Could you share the RQMExcelWordImporter logs ?
See https://jazz.net/wiki/bin/view/Main/RQMExcelWordImporter#Troubleshooting for details on where it's located.

Regards,
Stéphane


Comments
VIJAY SUNDARESHWARAN commented Apr 08 '13, 11:10 a.m. | edited Apr 08 '13, 4:22 p.m.

 @Stephane Leroy....


I will paste the entries from the Mso2Rqm_Debug.log in my next answer below. I see the follwoing "Operation Timed out" error at the end:

4/8/2013 10:51:52 AM: INFO: <Unknown Caller Context>: response from project has response content key 
4/8/2013 10:51:52 AM: INFO: <Unknown Caller Context>: response has keys: System.Collections.Hashtable+HashtableEnumerator

4/8/2013 10:54:04 AM: ERROR: <Unknown Caller Context>: Exception when get from RM server: The operation has timed out

I have about 793 Requirements on RRC for my project. This same procedure using the Utility works when I have less number of requirements (less than 475 or 500). But when the number of requirements increases, the upload fails consistently and I get the "Operation timed out" error in the debug log and the error as shown above in the screen shot.

Is there any way to turn on Debugging on the utility side? Or is there any other config setting I need to check on RRC side?

Please advice.

Thanks,
Vijay.S


permanent link
VIJAY SUNDARESHWARAN (25247) | answered Apr 08 '13, 11:11 a.m.
Entries from the Mso2Rqm_Debug.log:

4/8/2013 10:50:41 AM: 
SESSION: 4/8/2013 10:50:41 AM
4/8/2013 10:50:41 AM: INFO: <Unknown Caller Context>: RQMExporter created!
4/8/2013 10:50:42 AM: INFO: <Unknown Caller Context>: RQMExporter Startup!
4/8/2013 10:50:42 AM: INFO: <Unknown Caller Context>: Mso2Rqm: Mso2Rqm instantiated
4/8/2013 10:50:42 AM: INFO: <Unknown Caller Context>: ExcelApplicationContext: Destroyed commands
4/8/2013 10:50:44 AM: INFO: <Unknown Caller Context>: caption : RQM
4/8/2013 10:50:44 AM: INFO: <Unknown Caller Context>: ExcelApplicationContext: Created commands
4/8/2013 10:51:52 AM: INFO: <Unknown Caller Context>: response from project contained <?xml version="1.0" encoding="UTF-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
.
.
.
.
.
.
.
.
.4/8/2013 10:51:52 AM: INFO: <Unknown Caller Context>: response from project has response content key 
4/8/2013 10:51:52 AM: INFO: <Unknown Caller Context>: response has keys: System.Collections.Hashtable+HashtableEnumerator
4/8/2013 10:54:04 AM: ERROR: <Unknown Caller Context>: Exception when get from RM server: The operation has timed out
4/8/2013 10:54:27 AM: INFO: <Unknown Caller Context>: ExcelApplicationContext: Destroyed commands
4/8/2013 10:54:27 AM: INFO: <Unknown Caller Context>: ExcelApplicationContext: Destroyed commands
4/8/2013 10:54:27 AM: INFO: <Unknown Caller Context>: Mso2Rqm Shutdown!


permanent link
Stephane Leroy (1.4k149) | answered Apr 09 '13, 3:57 a.m.
JAZZ DEVELOPER
Vijay,

I see there are currently 3 open forum questions on this topics :
- (this one) https://jazz.net/forum/questions/108603/is-there-a-limit-on-the-number-of-results-requirements-that-can-be-fetched-from-rrc
- https://jazz.net/forum/questions/103937/rqmexcelimporter-time-out-loading-requirements
- https://jazz.net/forum/questions/102314/rqmexcelwordimporter-exception-when-get-from-rm-server-the-operation-has-timed-out

In the 2 other forum questions, Hao Wan suggested you to increase the "SPARQL Query abort timeout (in ms) in "Advanced Properties" on the admin properties page"
While the timeout error you experience appears at approx. min 4 (vs. the 5 min default value in the JTS properties), I have the two following questions :
1) have you ever tried to change that value (let's says to 10 mn) ?
2) are you running in a virtualized environment ?

Depending on the result of this test (see question (1)), if nothing changes, at least we'll have definitely eliminated a possible root cause.

Regards,

Comments
VIJAY SUNDARESHWARAN commented Apr 09 '13, 8:55 a.m.

Hi Stephane.... 


1) The value is currently set to 5 minutes. We will try to change it to 10 minutes and retry the test and I will let you know how that goes.
2) I will check about the environment being used and will let you know.

Thanks for your response.

Vijay.S


VIJAY SUNDARESHWARAN commented Apr 11 '13, 12:49 p.m.

Hi Stephane, 

We did try to increase the timeout value to 10 minutes and re-ran the test. I have provided the results, observations and answer to your question regarding the environment in my post below.
Thanks,
Vijay.S


permanent link
VIJAY SUNDARESHWARAN (25247) | answered Apr 11 '13, 12:47 p.m.
Hi  Stephane,
We increased the SPARQL Query Abort Timeout to 10 minutes and re-ran the tests. With more number of requirements (>500) on RRC, we still get the "Exception when get from RM server" error.
And, regarding the environment, Yes the Jazz applications are hosted on Virtual Servers.
One other observation when I ran the tests today is mentioned below.
In all the cases (successful/failed tests), the test runs do not take more than 5 minutes. Usually it takes around 3.5 to 4 minutes to complete the "full test run". A "full test run" consists of the following events/steps:
1.Open the MS-Excel Spread Sheet containing the Test cases.
2.Click on the RQM Add-ins in the excel sheet and enter the Credentials. Then, click on "Validate".
3.Available projects get populated in the "Project" drop down list. It takes approximately 15-30 seconds for the project list to get populated.
4.Select the Project from the drop down list, check "Link to Existing Requirement" and click on "Export".
5.In the next dialog box, select the RM project, enter the credentials and then click on "Export".
6.The Utility starts to fetch the Requirements from RRC, once "Export" is clicked. 
7.From this point, it takes about 100 seconds (1 minute and 40 seconds) for the utility to: 
either return all the requirements and display it in the right pane 
or report the "Exception when get from RM server" error.

From this time line, I believe the utility takes about 100 seconds to fetch the requirements from RRC and succeed/fail. I tried multiple tests with these requirements and found this 100 second timeline to be consistent. The log entries from the Mso2Rqm_Debug.log, where these events listed above take place are as shown below:

###################################################################################
>>>>>  ~~ 4/11/2013 10:56:41 AM --> Opened the MS-Excel Spread Sheet containing the Test cases
###################################################################################
4/11/2013 10:56:41 AM: SESSION: 4/11/2013 10:56:41 AM
4/11/2013 10:56:41 AM: INFO: <Unknown Caller Context>: RQMExporter created!
4/11/2013 10:56:41 AM: INFO: <Unknown Caller Context>: RQMExporter Startup!
4/11/2013 10:56:41 AM: INFO: <Unknown Caller Context>: Mso2Rqm: Mso2Rqm instantiated
4/11/2013 10:56:41 AM: INFO: <Unknown Caller Context>: ExcelApplicationContext: Destroyed commands
4/11/2013 10:56:41 AM: INFO: <Unknown Caller Context>: caption : RQM
4/11/2013 10:56:41 AM: INFO: <Unknown Caller Context>: ExcelApplicationContext: Created commands

#################################################################################
>>>>>  ~~ 4/11/2013 10:56:45 AM --> Clicked on RQM Add-in and entered the Credentials and Clicked on "Validate". 
>>>>>  ~~ 4/11/2013 10:56:45 AM --> The following entries got logged when all the projects got populated in the Drop Down List.
#################################################################################
4/11/2013 10:57:12 AM: INFO: <Unknown Caller Context>: response from project contained <?xml version="1.0" encoding="UTF-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
.
.
.
.
4/11/2013 10:57:12 AM: INFO: <Unknown Caller Context>: response from project has response content key 
4/11/2013 10:57:12 AM: INFO: <Unknown Caller Context>: response has keys: System.Collections.Hashtable+HashtableEnumerator
###########################################################################################
>>>>>  ~~ 4/11/2013 10:58:00 AM --> Selected the Project from the drop down list and clicked on "Export". 
>>>>>  ~~ 4/11/2013 10:58:00 AM --> In the next dialog box, selected the RM project, entered Credentials and clicked on "Export". 
>>>>>  ~~ 4/11/2013 10:58:00 AM --> The Utility started to Fetch Requirements
###########################################################################################
4/11/2013 10:59:41 AM: ERROR: <Unknown Caller Context>: Exception when get from RM server: The operation has timed out
		

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.