Error in installing Jira Service Management License.
Platform notice: Server and Data Center only. This article only applies to Atlassian products on the Server and Data Center platforms.
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
Problem
Installing a new Jira Service Management and updating the license results in Connection refused error.
- Download Jira Service Management 3 and above OBR.
- Upload the Jira Service Management obr using the Upload an application in Version and licenses.
- Paste the new license.
- Updating the license failed with connection refused error.
The following appears in the atlassian-jira.log
2016-04-20 10:00:12,862 Caesium-1-2 INFO ServiceRunner [c.a.crowd.directory.DbCachingRemoteDirectory] failed synchronisation complete for directory [ 10001 ] in [ 4ms ]
2016-04-20 10:00:12,893 Caesium-1-4 ERROR ServiceRunner [c.atlassian.scheduler.JobRunnerResponse] Unable to synchronise directory
com.atlassian.crowd.exception.OperationFailedException: org.apache.http.conn.HttpHostConnectException: Connect to localhost:8095 [localhost/127.0.0.1, localhost/0:0:0:0:0:0:0:1] failed: Connection refused
at com.atlassian.crowd.integration.rest.service.RestExecutor$MethodExecutor.andReceive(RestExecutor.java:493)
at com.atlassian.crowd.integration.rest.service.RestCrowdClient.searchUsers(RestCrowdClient.java:557)
at com.atlassian.crowd.directory.RemoteCrowdDirectory.searchUsers(RemoteCrowdDirectory.java:371)
at com.atlassian.crowd.directory.ldap.cache.RemoteDirectoryCacheRefresher.findAllRemoteUsers(RemoteDirectoryCacheRefresher.java:55)
at com.atlassian.crowd.directory.ldap.cache.RemoteDirectoryCacheRefresher.synchroniseAllUsers(RemoteDirectoryCacheRefresher.java:90)
..
Caused by: org.apache.http.conn.HttpHostConnectException: Connect to localhost:8095 [localhost/127.0.0.1, localhost/0:0:0:0:0:0:0:1] failed: Connection refused
at org.apache.http.impl.conn.DefaultHttpClientConnectionOperator.connect(DefaultHttpClientConnectionOperator.java:151)
at org.apache.http.impl.conn.PoolingHttpClientConnectionManager.connect(PoolingHttpClientConnectionManager.java:353)
at org.apache.http.impl.execchain.MainClientExec.establishRoute(MainClientExec.java:380)
at org.apache.http.impl.execchain.MainClientExec.execute(MainClientExec.java:236)
at org.apache.http.impl.client.cache.CachingExec.callBackend(CachingExec.java:592)
..
Caused by: java.net.ConnectException: Connection refused
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350)
at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)Diagnosis
Environment
- This happens in Jira 7 and above.
Cause
The cause is not known at the moment.
Workaround
Please restart the server and try to update the license.
If this workaround does not help, please reach out to Atlassian Support for further troubleshooting.
Last modified on May 23, 2022
Powered by Confluence and Scroll Viewport.