It's all about the answers!

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

×6,019
×3,953

question asked: Sep 30 '15, 5:09 p.m.
question was seen: 1,732 times
last updated: Oct 01 '15, 1:05 p.m.

Related questions

Where do you set projectcontext or GLOBAL_CONTEXT value?

0
Stuart Jewell (16●9●15) | asked Sep 30 '15, 5:09 p.m.
When executing an artifacts list query with various given filters in RRC, the query took to long and failed to return results.  The following warning message was seen in the logs:

fronting.server.core.jpi.internal.JTSQueryService  - **** WARNING **** THIS QUERY IS SLOW **** This query specifies 'null' for 'projectContext' and is therefore searching across ALL projects. If this is intended, please supply QueryServiceParameters.GLOBAL_CONTEXT which will supress this message.


Where does one set these values so that the query is more efficient assuming that this will help our queries not time out?

Accepted answer

0
permanent link
ian green (178●1●4) | answered Sep 30 '15, 5:15 p.m.
JAZZ DEVELOPER
This is a log message intended for developers of DOORS Next Generation.  There is no action to be taken as an end-user. 
Stuart Jewell selected this answer as the correct answer
Comments
Stuart Jewell commented Oct 01 '15, 10:23 a.m.

Any suggestions on where to look on why queries time out.  In particular, I'm trying to do RRC query view that allows me to see what artifacts are under suspicion for given modules associated with a given release collection.  Therefore, my filter is "Requirement", Modified after a given date, where used = list of use case modules that are part of a given collection.  Suspicion column added to view.  This works for one view, but times out for a different collections view. Also would like to add where used column.  But again, seems to really load the system.  We had the default timeout of 30seconds but doubled this and it doesn't seem to help.  Takes about 2 minutes before timeout message appears.

Stuart Jewell commented Oct 01 '15, 1:05 p.m.

Some more clarifications:
- not a "collections view" but the artifacts view which is filtered based on use case modules specified in a given collection (i.e. view collection, write down use cases and manually add to filter, and filtered on artifact type = requirement, modified date >= 6/1/2015
- not "where used" column but "used in modules" column
- there are currently 9247 artifacts of type requirement

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.