Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Slack integration with JIRA breaking (Slack TLSv1.3 change?)

Jeff Turner
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Apr 16, 2020

I am a consultant who manages companies' Atlassian apps.

Over the past 24h, two companies have reported that Jira's integration with Slack has suddenly broken. Restarting Jira lets a few Slack webhook calls through before it gets stuck again. Once stuck, no webhooks (even non-Slack) will go through.

To cut a long story short, this is due to a bug in Java 11's TLSv1.3 support. Jira is failing to close the TLS connection, which blocks the webhook thread queue:

This can be diagnosed by taking a thread dump (jstack -l <pid>) and looking for a BLOCKED thread named Web-Hook-Publisher-n, e.g.:

"Web-Hook-Publisher-2" #480 daemon prio=5 os_prio=0 cpu=2725.90ms elapsed=116091.79s tid=0x00007f6a6c794800 nid=0x2201 waiting for monitor entry [0x00007f68a43fa000]
java.lang.Thread.State: BLOCKED (on object monitor)
at org.apache.http.nio.reactor.ssl.SSLIOSession.close(
- waiting to lock <0x0000000724634b18> (a org.apache.http.nio.reactor.ssl.SSLIOSession)


There is a workaround in the JRASERVER reports. The bug is fixed in Java 12, and should be backported to the forthcoming Java 11.0.8.

Two instances hitting the same problem could be a coincidence, but it could be that Slack recently updated TLS somehow in their endpoint. They did remove TLSv1.0 and v1.1 support last month.

Has anyone else running Java 11 with Slack integration noticed this problem?



Log in or Sign up to comment