Cannot connect to UPM
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
Summary
Symptoms
When in the plugins area of JIRA, you get a warning that you are not able to connect to the UPM
The following appears in the atlassian-jira.log:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
2012-07-17 12:11:21,883 QuartzWorker-0 WARN ServiceRunner NotificationCacheUpdateJob-job [upm.notification.cache.NotificationCacheUpdaterImpl] Automatic plugin update check failed
com.atlassian.plugins.PacException: 404
at com.atlassian.plugins.client.service.AbstractServiceClient.getEntityFromResponse(AbstractServiceClient.java:248)
at com.atlassian.plugins.client.service.AbstractRestServiceClient$4.apply(AbstractRestServiceClient.java:134)
at com.atlassian.plugins.client.service.AbstractRestServiceClient$4.apply(AbstractRestServiceClient.java:130)
at com.atlassian.plugins.client.service.AbstractServiceClient.executeMethod(AbstractServiceClient.java:411)
at com.atlassian.plugins.client.service.AbstractRestServiceClient.list(AbstractRestServiceClient.java:129)
at com.atlassian.plugins.client.service.plugin.PluginVersionServiceClientImpl.findUpdates(PluginVersionServiceClientImpl.java:81)
at com.atlassian.upm.pac.PacClientImpl.getUpdates(PacClientImpl.java:154)
at com.atlassian.upm.notification.cache.NotificationCacheUpdaterImpl.updatePluginUpdateNotification(NotificationCacheUpdaterImpl.java:70)
at com.atlassian.upm.notification.cache.NotificationCacheUpdaterImpl.updateAllNotifications(NotificationCacheUpdaterImpl.java:56)
at com.atlassian.upm.notification.cache.NotificationCacheUpdateScheduler$NotificationCacheUpdateJob.execute(NotificationCacheUpdateScheduler.java:78)
at com.atlassian.sal.jira.scheduling.JiraPluginSchedulerService.run(JiraPluginSchedulerService.java:93)
at com.atlassian.jira.service.JiraServiceContainerImpl.run(JiraServiceContainerImpl.java:61)
at com.atlassian.jira.service.ServiceRunner.execute(ServiceRunner.java:47)
at org.quartz.core.JobRunShell.run(JobRunShell.java:195)
at com.atlassian.multitenant.quartz.MultiTenantThreadPool$MultiTenantRunnable.run(MultiTenantThreadPool.java:72)
at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:520)Diagnosis
The automatic checking for updated plugins will not function correctly, but you will still be able to find and download plugins from the UPM despite the error message.
ℹ️ This will prove true only if there are no other proxy or firewall connections creating an issue.
Cause
At the moment this looks to be an issue with the UPM and more specifically JIRA 5.0.6.
There is a bug associated with this issue at the following:
https://ecosystem.atlassian.net/browse/AMKT-2001
Solution
Workaround
Upgrade JIRA to a newer version than 5.0.6
Resolution
For now, there is no hard resolution. The only known way to get past this issue is to upgrade to a newer version of JIRA. All updates related to this issue will be on the bug link above.
Was this helpful?