Microsoft Teams app disconnected in Jira
Platform Notice: Cloud, Server, and Data Center - This article applies equally to all platforms.
After connecting Jira to Microsoft Teams, the following symptoms may be displayed:
The app shows disconnected either immediately or a short time later. The longest reported connection was less than 24 hours.
You may see in incrementing number of open files for Jira.
You may see an incrementing number of open threads in Jira.
One of the following appears in the atlassian-jira.log:
ERROR ServiceRunner [c.microsoft.signalr.HubConnection] HubConnection disconnected with an error: Server timeout elapsed without receiving a message from the server.. ERROR [c.microsoft.signalr.HubConnection] HubConnection disconnected with an error: Server timeout elapsed without receiving a message from the server..
ERROR ServiceRunner [c.m.teams.service.SignalRService] startConnectionIfDisconnected() error (java.lang.RuntimeException): Unexpected status code returned from negotiate: 503 Service Unavailable.
This may appear as thousands of threads in a thread dump or in the catalina.out log:
Ok Http WebSocket https://msteams-jira-server.service.signalr.net/... priority:5 - threadId:0x0000000000001784 - nativeId:0 - nativeId (decimal):0 - state:WAITING stackTrace: java.lang.Thread.State: WAITING (parking) at firstname.lastname@example.org/jdk.internal.misc.Unsafe.park(Native Method)
Jira Server deployment
- Connected to Teams via the MS Teams app and/or a Teams webhook
Install the MS Teams app.
- Configure the connection.
- When the app disconnects, you may see:
- the stacktraces above.
- an Out Of Memory exception even though there is enough heap space for Jira.
- a "too many open files" exception if Jira hits the ulimit for open files.
The Teams app appears to open connections without releasing or closing them. It will then attempt to open another new connection without closing the first.
Completely uninstall the Teams app and Jira integration from both sides. Simply disabling the app has been shown to not stop threads from incrementing.
There is no resolution at this time.
Please watch the bug report below for updates