-
Bug
-
Resolution: Unresolved
-
Low (View bug fix roadmap)
-
None
-
7.13.0, 7.12.3, 9.12.10, 9.4.30, 9.12.19
-
None
-
7.12
-
18
-
Severity 3 - Minor
-
1
-
Summary
Adding in -Dupm.pac.disable=true to JVM parameters does not stop Jira from connecting to the Marketplace as indicated in problems connecting to the Atlassian marketplace.
While this works for Confluence.
Steps to reproduce
- Set -Dupm.pac.disable=true in setenv.sh or Windows Service Java Options (depends which OS is running Jira).
- Start Jira
- Navigate to Jira Administration > Add ons
Expected results
Find new apps should not appear or allow searching of apps in marketplace.
Actual results
Find new apps is present and connecting to the marketplace, searching and downloading plugins and updates work as normal.
Verify
You can verify if its disabled without going to Find new apps via - http://yourjira/rest/plugins/1.0/settings
Results shows -
{"settings":[{"key":"pacDisabled","value":false,"requiresRefresh":true,"defaultCheckedValue":true,"readOnly":false},{"key":"requestsDisabled","value":false,"requiresRefresh":true,"defaultCheckedValue":true,"readOnly":false},{"key":"emailDisabled","value":false,"requiresRefresh":false,"defaultCheckedValue":true,"readOnly":false},{"key":"autoUpdateEnabled","value":false,"requiresRefresh":false,"defaultCheckedValue":false,"readOnly":false}]}
Where "pacDisabled","value":false value false shows that it was not disabling pac.
While in start up parameters show that -Dupm.pac.disable=true is set in the application logs -
upm.pac.disable : true
In Confluence this works and shows results -
{"settings":[{"key":"pacDisabled","value":true,"requiresRefresh":true,"defaultCheckedValue":true,"readOnly":false},{"key":"requestsDisabled","value":false,"requiresRefresh":true,"defaultCheckedValue":true,"readOnly":false},{"key":"emailDisabled","value":false,"requiresRefresh":false,"defaultCheckedValue":true,"readOnly":false},{"key":"autoUpdateEnabled","value":false,"requiresRefresh":false,"defaultCheckedValue":false,"readOnly":false}]}
Where "pacDisabled","value":true
Tested on UPM versions 2.22.9, 2.22.14, 2.22.19, 3.0.1
Workaround
Can only disable this in Jira via Jira Administration > Add ons > Manage apps go to the settings and uncheck the Connect to the Atlassian Marketplace option.
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[JSWSERVER-19792] -Dupm.pac.disable=true JVM parameter does not disable Marketplace connectivity in Jira
| Affects Version/s | Original: 10.3.4 [ 110309 ] | |
| Affects Version/s | Original: 10.1.2 [ 109900 ] | |
| Affects Version/s | Original: 9.17.5 [ 109417 ] | |
| Affects Version/s | Original: 10.2.1 [ 108822 ] | |
| Affects Version/s | New: 9.12.10 [ 108207 ] | |
| Affects Version/s | New: 9.4.30 [ 110405 ] |
| Affects Version/s | New: 10.2.1 [ 108822 ] | |
| Affects Version/s | New: 9.17.5 [ 109417 ] | |
| Affects Version/s | New: 10.1.2 [ 109900 ] | |
| Affects Version/s | New: 9.12.19 [ 110409 ] | |
| Affects Version/s | New: 10.3.4 [ 110309 ] |
| Support reference count | Original: 17 | New: 18 |
| UIS | Original: 2 | New: 1 |
| UIS | Original: 3 | New: 2 |
| UIS | Original: 2 | New: 3 |
| Support reference count | Original: 16 | New: 17 |
| UIS | Original: 3 | New: 2 |
| UIS | Original: 2 | New: 3 |
| Comment |
[ We were experiencing the same issue. However, the 'Applications' page itself was also timing out. This made it so that there was no way to disable the marketplace.
Our work-around was to add a host entry on the server running Jira to point marketplace.atlassian.com to 127.0.0.1. This way the page would not timeout and instead simply load with a connection error. This allowed us to access the 'Applications' page and disable marketplace connectivity. ] |