Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-27314

Clear Plugin Cache as required

XMLWordPrintable

    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.

      Support is often finding that upon major upgrades (to JIRA 4.4, or to JIRA 5.0 for example) that we have to ask customers to manually perform the following for a wide range of cases, so much so I've written a macro that covers the situatoin:

      Please perform the following:

      • Shut down JIRA
      • Delete the following hidden plugin cache directories: 
        JIRA_HOME/plugins/.bundled-plugins
JIRA_HOME/plugins/.osgi-plugins
      • Restart JIRA (These directories will be recreated on JIRA reboot with new plugin cache)

      Can either one of two things in JIRA be implemented:

      One, after every major point release (4.3 - 4.4 - 5.0) when the user has upgraded to that version can the plugin cache be automatically be deleted by JIRA so it can then be automatically recreated on JIRA reboot.

      Two, please give users a button where they can click "Clear Plugin Cache" and it magically fixes all their plugin cache problems somehow.

        1. image-2021-08-19-10-24-38-152.png
          image-2021-08-19-10-24-38-152.png
          54 kB

            [JRASERVER-27314] Clear Plugin Cache as required

            Michael Andreacchio added a comment -

            Hi christian.schulz,

            We'd be really interested if you were able to give us step-by-step instructions into how this can be reproduced, and any insights into exactly what problems this is causing for you. Could you raise an issue in https://support.atlassian.com referencing this issue so that our support engineers can confirm that this problem is reproducible and accordingly re-open this bug?

            Cheers,

            Michael Andreacchio
            JIRA Support Team Lead

            Michael Andreacchio added a comment - Hi christian.schulz , We'd be really interested if you were able to give us step-by-step instructions into how this can be reproduced, and any insights into exactly what problems this is causing for you. Could you raise an issue in https://support.atlassian.com referencing this issue so that our support engineers can confirm that this problem is reproducible and accordingly re-open this bug? Cheers, Michael Andreacchio JIRA Support Team Lead

            Christian Schulz added a comment -

            @Robert Smart:
            I have similar problems with JIRA 6.1 there are files from an uninstalled plugin kept in .osgi-plugins.
            I need to take JIRA offline delete them and restart it again.
            Why is it necessary and not done by the uninstallation routine?

            Christian Schulz added a comment - @Robert Smart: I have similar problems with JIRA 6.1 there are files from an uninstalled plugin kept in .osgi-plugins . I need to take JIRA offline delete them and restart it again. Why is it necessary and not done by the uninstallation routine?

            Luis Miranda (Inactive) added a comment -

            mdoar, in all reported cases it was found that the problem was solved by removing or otherwise disabling plugins in installed-plugins. So it was not a case of the cache being out of date, but incompatible plugins being present.

            Luis Miranda (Inactive) added a comment - mdoar , in all reported cases it was found that the problem was solved by removing or otherwise disabling plugins in installed-plugins . So it was not a case of the cache being out of date, but incompatible plugins being present.

            MattS added a comment -

            Robert,

            Can you provide more detail for people who find this bug in the future? Was removing the caches not required during an upgrade, and what were the plugin cache problems being seen in the first place?

            ~Matt

            MattS added a comment - Robert, Can you provide more detail for people who find this bug in the future? Was removing the caches not required during an upgrade, and what were the plugin cache problems being seen in the first place? ~Matt

            metapoint added a comment -

            Further investigation proved that this was not actually a problem.

            metapoint added a comment - Further investigation proved that this was not actually a problem.

            MattS added a comment - - edited

            Michael,

            What kind of macro did you use?

            ~Matt

            p.s. I like the idea of magic cache clearing - expelliarmus!

            MattS added a comment - - edited Michael, What kind of macro did you use? ~Matt p.s. I like the idea of magic cache clearing - expelliarmus!

            Jeremy Largman added a comment -

            I've raised one more improvement request around this:
            https://jira.atlassian.com/browse/JRA-27450

            Jeremy Largman added a comment - I've raised one more improvement request around this: https://jira.atlassian.com/browse/JRA-27450

            Pat Pigatti added a comment -

            We are having this problem at QAD too. Actually, I didn't know about these hidden plugins till now. I'm finding there's more to it than that where people occassionally have problems logging into Jira or links not working where clearing the cache and cookies in Google Chrome clears the issue but eventually comes back for some users. It's a pain. We are on 4.4.1 in production and moving to 4.4.4 in April. Any plans on when this whole area will get looked at? Regards, Pat

            Pat Pigatti added a comment - We are having this problem at QAD too. Actually, I didn't know about these hidden plugins till now. I'm finding there's more to it than that where people occassionally have problems logging into Jira or links not working where clearing the cache and cookies in Google Chrome clears the issue but eventually comes back for some users. It's a pain. We are on 4.4.1 in production and moving to 4.4.4 in April. Any plans on when this whole area will get looked at? Regards, Pat

              Unassigned Unassigned
              mandreacchio Michael Andreacchio
              Votes:
              2 Vote for this issue
              Watchers:
              27 Start watching this issue

                Created:
                Updated:
                Resolved: