Issues
- Reconnect task for Jira client is not correctly cleaned upBAC-1393Resolved issue: BAC-1393
- XSS vulnerability in Backbone Issue Sync admin interface (2019-10-02)BAC-1350Resolved issue: BAC-1350
- For the Sync Info Panel, use Jira's REST API instead of Jira's Java API on Jira ServerBAC-1331Resolved issue: BAC-1331
- Outgoing changes fail due to NullPointerExceptionBAC-1328Resolved issue: BAC-1328
- Replace user mentions in comments and other text fieldsBAC-1321Resolved issue: BAC-1321
- When importing paired issue data also update the Sync Info Panel tooBAC-1283Resolved issue: BAC-1283
- Use fallback user also if user is inactiveBAC-796Resolved issue: BAC-796
7 of 7
Reconnect task for Jira client is not correctly cleaned up
Fixed
Description
Environment
None
Created February 12, 2020 at 10:28 AM
Updated February 15, 2023 at 4:41 PM
Resolved February 24, 2020 at 8:41 AM
Activity
Show:
In order to access Jira, we are using an internal Jira client to make HTTP requests. In case we temporarily can not connect to a Jira instance, we start a reconnect task to wait until a Jira instance is reachable again. This task is not cleaned up properly and in some circumstances in can run forever until Jira is restarted again.
Workaround
Restart your Jira instance.