PM89015: [wi 260564]: Error 500: IDashboardRestService: Query timed out while waiting for index to update

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

APAR status

  • Closed as program error.

Error description

  • Dashboards for CCM and RM no longer load and the following error
    occurs:
    
    Query timed out while waiting for index to update. Please verify
    that the indexing service is running properly and has finished
    indexing, and try again.
    
    The same error is found in the logs.
    Overall system performance is also poor, for example, the login
    seems to take very long.
    
    /jts/indexing and /ccm1/indexing show a backlog of 0 for all
    indexes except for the queryIndexer on the Jazz Team Server
    (JTS) which has a backlog of 1 and a remainingTime of 11 and
    searchIndexer which has a backlog of 1
    and a remainingTime of 14.
    
    Review the following work item on jazz.net for further details:
    https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.Wo
    rkItem/260564
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    Error 500: IDashboardRestService: Query timed out while
    waiting for index to update
    

Problem conclusion

  • The issue was that one change notifier was used for all
    applications. This would cause the following scenario to
    fail:
    1. An rm resource started to be created
    2. A dashboard resource was created at the same time
    3. Since an rm resource was still being created, the
    dashboard resource could not be notified
    4. The rm resource creation completed
    5. The rm resource was notified
    6. The dashboard resource remained in pending state
    
    The fix consists in having one change notifier per
    application. This is the correct approach since there is one
    indexer per application.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM89015

  • Reported component name

    RATL TEAM CONCE

  • Reported component ID

    5724V0400

  • Reported release

    401

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2013-05-14

  • Closed date

    2013-08-07

  • Last modified date

    2014-05-27

  • 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

    RATL TEAM CONCE

  • Fixed component ID

    5724V0400

Applicable component levels

  • R401 PSN

       UP



Rate this page:

(0 users)Average rating

Document information


More support for:

Rational Team Concert

Software version:

4.0.1

Reference #:

PM89015

Modified date:

2014-05-27

Translate my page

Machine Translation

Content navigation