Microsoft Teams app disconnected in Jira

Platform Notice: Cloud and Data Center - This article applies equally to both cloud 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

Summary

Problem

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:

1 2 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..
1 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:

1 2 3 4 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 java.base@11.0.6/jdk.internal.misc.Unsafe.park(Native Method)

Diagnosis

Environment

  • Jira Server deployment

  • Connected to Teams via the MS Teams app and/or a Teams webhook

Diagnostic Steps

  • 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.

Cause

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.

Solution

Workaround

Completely uninstall the Teams app and Jira integration from both sides. Simply disabling the app has been shown to not stop threads from incrementing.

Resolution

There is no resolution at this time.

Note

Please watch the bug report below for updates

Updated on April 2, 2025

Still need help?

The Atlassian Community is here for you.