Wondering if others are experiencing this issue with the out-of-box JIRA/Hipchat integration on JIRA 6.4.12. We will sporadically (every couple months or so) notice the hipchat integration die. As a result, throughout the day, threads will spike & build up to the point that it brings our server down.
1. Is there a way to kill the threads being spawned?
2. Can we lower the timeout threshold for the hipchat integration?
3. Have others experienced this issue?
Here is a sample of the hipchat error we see in catalina.out:
2017-04-06 03:24:20,976 jira-hipchat-plugin:thread-3 ERROR z082856 1013x91x31 1ixvyk2 10.113.13.149,0:0:0:0:0:0:0:1 /rest/greenhopper/1.0/sprint/rank [service.listener.impl.DefaultJiraHipChatEventListener] Error processing event
java.util.concurrent.TimeoutException: Timeout waiting for task.
at com.google.common.util.concurrent.AbstractFuture$Sync.get(AbstractFuture.java:301)
at com.google.common.util.concurrent.AbstractFuture.get(AbstractFuture.java:91)
at com.atlassian.jira.plugins.hipchat.service.listener.impl.DefaultJiraHipChatEventListener.filterDuplicateMessages(DefaultJiraHipChatEventListener.java:110)
at com.atlassian.jira.plugins.hipchat.service.listener.impl.DefaultJiraHipChatEventListener.access$400(DefaultJiraHipChatEventListener.java:46)
at com.atlassian.jira.plugins.hipchat.service.listener.impl.DefaultJiraHipChatEventListener$1.call(DefaultJiraHipChatEventListener.java:92)
at com.atlassian.jira.plugins.hipchat.service.listener.impl.DefaultJiraHipChatEventListener$1.call(DefaultJiraHipChatEventListener.java:71)
at com.atlassian.jira.plugins.hipchat.service.task.impl.DefaultTaskExecutorService$2.call(DefaultTaskExecutorService.java:114)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)