Details
-
Bug
-
Resolution: Unresolved
-
Low
-
None
-
1
-
Severity 2 - Major
-
Description
Issue Summary
Getting 504 errors when the object is in the search is too complex
API endpoint: /v1/objectconnectedtickets/
/tickets
This is reproducible on Data Center: (yes) / (no): No
Steps to Reproduce
- Make a request to JSM using the payload similar to the below:
https://api.atlassian.com/jsm/insight/workspace/d39e07b7-8f61-4985-9ceb-f21cb0a12345/v1/objectconnectedtickets/65185/tickets?hideResolved=false&limit=1
Expected Results
The response should include all the related objects
Actual Results
The response fails at endpoint /rest/api/3/search with the following errors:
stack: java.lang.RuntimeException at com.atlassian.jira.user.util.UserKeyStoreImpl.lambda$getUsersForKeys$1(UserKeyStoreImpl.java:177) at com.atlassian.jira.consistency.ConsistencyCheckBuilderForRolloutService$TypeAwareRollout.lambda$with$3(ConsistencyCheckBuilderForRolloutService.java:240) at com.atlassian.workcontext.metrics.Timer.timeWithException(Timer.java:215) at com.atlassian.jira.consistency.ConsistencyCheckServiceImpl.lambda$wrapWithTimer$6(ConsistencyCheckServiceImpl.java:271) at com.atlassian.jira.consistency.ConsistencyCheckServiceImpl.wrapWithTimer(ConsistencyCheckServiceImpl.java:278) … at com.atlassian.jira.security.ratelimit.heimdall.filter.JiraHeimdallRateLimitingCostUpdateRegistrationFilter.doFilterOnce(JiraHeimdallRateLimitingCostUpdateRegistrationFilter.java:27) at com.atlassian.jira.web.filters.FilterOnceAbstractHttpFilter.doFilter(FilterOnceAbstractHttpFilter.java:25) at com.atlassian.core.filters.AbstractHttpFilter.doFilter(AbstractHttpFilter.java:41) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:189) … at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1789) at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49) at org.apache.tomcat.util.threads.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1191) at org.apache.tomcat.util.threads.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:659) at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61) at java.base/java.lang.Thread.run(Thread.java:829) } ext: { [-] err: { [-] location: com.atlassian.jira.user.util.UserKeyStoreImpl:lambda$getUsersForKeys$1 type: java.lang.RuntimeException } jira: { [-] request: { [-] asap_iss: micros-group/jsm-cmdb id: XXXXXXXX ipaddr: XX.XX.XX.XXX method: POST normuri: /rest/api/3/search traceId: XXXXXXXX traceSampled: false url: /rest/api/3/search } tenant: { [-] rds_host: <hostname> sitename: <siteURL>.atlassian.net } username: anonymous } } hostname: XXXXXXXX level: INFO logger: com.atlassian.jira.user.util.UserKeyStoreImpl m: { [+] } message: [Limited to 5 per PT1M] getUsersForKeys with size 60 micros_container: jira pid: 54 product: jira thread: http-nio-8090-exec-66 time: 2023-03-06T06:57:28.309092352Z timestamp: 2023-03-06T06:57:28,306Z }
Workaround
Currently there is no known workaround for this behavior. A workaround will be added here when available