Excessive access to JIRA Issue from IE 11

Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.

Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. 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

JIRA exhausted the threads available in the pool due to excessive access to some JIRA issues. The request made can be seen without referrer and occur hundreds of time on a particular issue per minute.

The following appears A LOT in JIRA Tomcat's access log:

1 127.0.0.1 1149x1798992x2 xxx.username [07/Feb/2017:19:09:27 +0900] - 200 303 4 "https://myownjira/jira/browse/TEST-680" "Mozilla/5.0 (Windows NT 6.1; WOW64; Trident/7.0; rv:11.0) like Gecko" "xxxx"

Diagnosis

Environment

  • JIRA 6.4.x - known to occur on

  • IE 11 as browser

  • Recently update Java on client machine

Diagnostic Steps

  • Large number of access (500+) to a JIRA Issue per minute

  • The access appear to come from IE 11 browser

  • Identify the IP address and the username of the user to check for the cause

Cause

The following two browser add-ons that comes bundled with Java is installed in the IE 11 browser

  • Amazon Assistant

  • Amazon 1 Button App

Solution

Resolution

Uninstall the following two add-ons that come bundled with Java on the affected client's machine

    • Amazon Assistant

    • Amazon 1 Button App

Updated on April 2, 2025

Still need help?

The Atlassian Community is here for you.