Insight unavailable with 503 or 504 statuses

XMLWordPrintable

    • 3
    • Major
    • 1

      Issue Summary

      When trying to return Insight fields values, it will not return any objects and it will fail with the error Unexpected response received from jsm-cmdb-gateway response with status 503

      Steps to Reproduce

      Problem is intermittent.

      Expected Results

      Insight will load normally and Insight fields will populate their values on JSM projects and Customer Portal

      Actual Results

      In the UI, customer will see a There's been a problem loading the object schemas. Try refreshing the page error message and the below exception is thrown in our logs:

      Unexpected response received from jsm-cmdb-gateway response with status 503
      Unexpected HTTP response received from the CMDB service. Details: com.atlassian.jira.httpclient.impl.UnexpectedHttpResponseException@2473fc55[statusCode=503,body=no healthy upstream,headers={date: <date>,content-type: text/plain,content-length: 19,server: envoy,x-envoy-upstream-service-time: 53,atl-traceid: <traceid>}]
      com.atlassian.jira.httpclient.impl.UnexpectedHttpResponseException: Unexpected response received from jsm-cmdb-gateway response with status 503
	at com.atlassian.jira.httpclient.impl.SynchronousHttpClient.classifyResponse(SynchronousHttpClient.java:107)
	at com.atlassian.jira.httpclient.impl.SynchronousHttpClient.lambda$withResponseClassifying$3(SynchronousHttpClient.java:92)
	at com.atlassian.jira.httpclient.impl.SynchronousHttpClient.callWithExceptionConversion(SynchronousHttpClient.java:70)
	at com.atlassian.jira.httpclient.impl.SynchronousHttpClient.doExecute(SynchronousHttpClient.java:47)
	at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:83)
	at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:108)
	at com.atlassian.servicedesk.cmdb.client.rest.CmdbRestClient.executeRequest(CmdbRestClient.java:374)
	at io.atlassian.fugue.Either$RightProjection.flatMap(Either.java:1128)
	at io.atlassian.fugue.Either.flatMap(Either.java:233)
	at com.atlassian.servicedesk.cmdb.client.rest.CmdbRestClient.lambda$get$2(CmdbRestClient.java:149)
	at com.atlassian.servicedesk.cmdb.client.rest.CmdbRestClient.withMetrics(CmdbRestClient.java:225)
	at com.atlassian.servicedesk.cmdb.client.rest.CmdbRestClient.get(CmdbRestClient.java:147)
	at com.atlassian.servicedesk.cmdb.client.service.CmdbObjectClient.lambda$null$23(CmdbObjectClient.java:280)
	at io.atlassian.fugue.Either$RightProjection.flatMap(Either.java:1128)
	at io.atlassian.fugue.Either.flatMap(Either.java:233)
	at com.atlassian.servicedesk.cmdb.client.service.CmdbObjectClient.lambda$searchObjectIdsWithPermissionElevation$25(CmdbObjectClient.java:279)

      Workaround

      Currently there is no known workaround for this behavior. A workaround will be added here when available

            Assignee:
            Unassigned
            Reporter:
            Gabriele Franck
            Votes:
            1 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: