After upgrading to version 2.13 or higher, the Universal Plugin Manager disappears from JIRA
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Symptoms
Immediately following an upgrade to the Universal Plugin Manager, the Universal Plugin Manager entirely disappears from JIRA
The following appears in the atlassian-jira.log:
1
Could not instantiate bean class [com.atlassian.upm.mac.HamletClientPacProxyImpl]: Constructor threw exception; nested exception is org.apache.http.conn.ssl.SSLInitializationException: Failure initializing default system SSL contextDiagnosis
This is typically seen when JIRA is used with a custom Java TrustStore.
Happens at very old version of UPM from several years ago.
Cause
The Universal Plugin Manager is trying to connect to Atlassian servers to poll for existing plugin licenses to make sure you're getting the plugins you've paid for. As this is somewhat sensitive information, it uses SSL to transmit to our servers. If the SSL component cannot be called, the UPM fails to load and is not part of JIRA.
Workaround
Roll the Universal Plugin Manager back to roll back the UPM to a known-good version. We have reliable reports that 2.9.3 will operate in this condition.
Stop JIRA
Remove the following files: <jira-home>/plugins/installed-plugins/atlassian-universal-plugin-manager-plugin-2.13.jar and <jira-home>/plugins/installed-plugins/plugin-license-storage-plugin-2.9.3.jar
Start JIRA
Upgrade Universal Plugin Manager to version 2.9.3
Resolution
As third party integration is outside of the scope of Atlassian support, the assistance we can give with this operation is limited.
Address the issues that are preventing the SSL components from loading
Ensure that if you've defined a custom truststore using the -Djavax.net.ssl.trustStore= directive, that you've also defined -Djavax.net.ssl.trustStorePassword= and -Djavax.net.ssl.trustStoreAlias= as appropriate.
Was this helpful?