Sometimes, a plugin is not ptoperly upgraded because, due some unknown reason, the old version remains active in memory locking some resources. As the newer version needs to access to those locked resources, the plugin does not work. And it seems the only way to unlock such resources is by re-starting JIRA.
Is there any way to force a plugin to fully be unloaded from memory, so unlock all the resources?
I guess just the same...
Usually, it works fine, but from time to time users' report this problem. :(
The plugin (Subversion ALM), uses an internal Java database which remains locked after the older version is un-installed for upgrading. As the database is a single file, I wonder whether there is some OS command to unlock it (without killing JIRA)... ?
Hey Atlassian community, I help lead engineering at Sentry, an open-source error-tracking and monitoring tool that integrates with Jira. We started using Jira Software Cloud internally last year, a...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs