Uploaded image for project: 'Jira Software Data Center'
  1. Jira Software Data Center
  2. JSWSERVER-10873

Slow / not working due to errors with gh.lexorank.service.error.retrytimeout

XMLWordPrintable

      Our Jira has the following problems

      • create / edit tasks is slow
      • move tasks does not work for some users.

      In the log I only see the following:

      2014-07-01 07:14:11,610 ajp-bio-8009-exec-5 WARN kny 434x30614x1 erwwi5 192.168.8.54 /secure/QuickEditIssue.jspa [greenhopper.customfield.lexorank.LexoRankCFType] Unable to retrieve rank for field [10201] and issue [12604]
2014-07-01 07:14:11,610 ajp-bio-8009-exec-5 WARN kny 434x30614x1 erwwi5 192.168.8.54 /secure/QuickEditIssue.jspa [greenhopper.customfield.lexorank.LexoRankCFType] gh.lexorank.service.error.retrytimeout
2014-07-01 07:14:11,610 ajp-bio-8009-exec-5 WARN kny 434x30614x1 erwwi5 192.168.8.54 /secure/QuickEditIssue.jspa [greenhopper.customfield.lexorank.LexoRankIndexer] Could not retrieve LexoRank value for issue[id=12604]. Indexing max LexoRank value instead.

      I see that there was some similar bugs in 6.4.0.6-7, but they should be fixed in 6.4.0.8 and 6.4.0.9.

            [JSWSERVER-10873] Slow / not working due to errors with gh.lexorank.service.error.retrytimeout

            Andrej Kvasnica added a comment -

            agreed with @andreas.schoen:
            It seems that minimum process on jira-6.2.3 with postgresql db is to backup data, create new database with C collation and then restore data.

            Andrej Kvasnica added a comment - agreed with @andreas.schoen: It seems that minimum process on jira-6.2.3 with postgresql db is to backup data, create new database with C collation and then restore data.

            Andreas Schön added a comment -

            Update: We found the issue causing our slow performance. Our SQL-database was set-up using non-neutral language settings. The Jira install instruction specifically says that language-neutral settings must be used. When we changed this setting (required some scripting / parsing of the database) the performance issue is gone, and it is possible to use agile ranking (drag-drop prioritizing of issues in the agile view).

            Andreas Schön added a comment - Update: We found the issue causing our slow performance. Our SQL-database was set-up using non-neutral language settings. The Jira install instruction specifically says that language-neutral settings must be used. When we changed this setting (required some scripting / parsing of the database) the performance issue is gone, and it is possible to use agile ranking (drag-drop prioritizing of issues in the agile view).

            Daniel Törnqvist added a comment -

            gh.lexorank.service.error.retrytimeout is more like 4 seconds (at least on our system Jira 6.3.15 and Agile 6.6.51).
            If you open an issue that have linked issues, like an epic with stories, you do however have to wait for all the issues to sequentially time out.

            Daniel Törnqvist added a comment - gh.lexorank.service.error.retrytimeout is more like 4 seconds (at least on our system Jira 6.3.15 and Agile 6.6.51). If you open an issue that have linked issues, like an epic with stories, you do however have to wait for all the issues to sequentially time out.

            Andreas Schön added a comment - - edited

            We upgraded to Jira Agile 6.6.60 (with Jira 6.3.14). Performance problem remains.

            It almost always takes about 55-60 seconds after clicking the "create"-button. Does this reflect the timeout set for "gh.lexorank.service.error.retrytimeout" ?

            Andreas Schön added a comment - - edited We upgraded to Jira Agile 6.6.60 (with Jira 6.3.14). Performance problem remains. It almost always takes about 55-60 seconds after clicking the "create"-button. Does this reflect the timeout set for "gh.lexorank.service.error.retrytimeout" ?

            Andreas Schön added a comment -

            We're using Jira Agile 6.6.13. We experience the performance issue too.

            Andreas Schön added a comment - We're using Jira Agile 6.6.13. We experience the performance issue too.

            Mateusz Janiszewski added a comment -

            How do I resolve this problem? I'm using Jira Agile v6.5.0

            Mateusz Janiszewski added a comment - How do I resolve this problem? I'm using Jira Agile v6.5.0

            Andrej Kvasnica added a comment -

            same problem here since JIRA Agile v6.4.2 (0cd4a6346e37e226).
            upgrade to latest JIRA Agile v6.4.3 (8b64c9843d011df8) didn't solve this issue.

            Andrej Kvasnica added a comment - same problem here since JIRA Agile v6.4.2 (0cd4a6346e37e226). upgrade to latest JIRA Agile v6.4.3 (8b64c9843d011df8) didn't solve this issue.

            Lee Macdonald added a comment -

            Yes, same problem with Agile 6.4.2. Performance when creating issues is extremely slow.

            Lee Macdonald added a comment - Yes, same problem with Agile 6.4.2. Performance when creating issues is extremely slow.

            RDK added a comment -

            Same problem here with Agile 6.4.2.

            RDK added a comment - Same problem here with Agile 6.4.2.

            Manuel Ramprecht added a comment -

            We experience the same issue after upgrading to Agile 6.4.0.9.

            Manuel Ramprecht added a comment - We experience the same issue after upgrading to Agile 6.4.0.9.

              Unassigned Unassigned
              ea3a8fcb299c Kjetil Nygård
              Affected customers:
              1 This affects my team
              Watchers:
              14 Start watching this issue

                Created:
                Updated:
                Resolved: