Issues
- Reconnect task for Jira client is not correctly cleaned upBAC-1393Resolved issue: BAC-1393
- Storing timestamp of last change check is causing high load for databaseBAC-1386Resolved issue: BAC-1386
- Allow user to change the connection details when loading the synchronization statusBAC-1376Resolved issue: BAC-1376
- Starting an async task on Jira Data Center runs foreverBAC-1375Resolved issue: BAC-1375
- Email validation fails for valid mail addressesBAC-1357Resolved issue: BAC-1357
- 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
- Allow one-click selection of all troubleshooting errors per pageBAC-1327Resolved issue: BAC-1327
- Replace user mentions in comments and other text fieldsBAC-1321Resolved issue: BAC-1321
- Priority correlation mapping does not work without project admin rightsBAC-1313Resolved issue: BAC-1313
- Delete issue properties after deleting a sync relation between two issuesBAC-1311Resolved issue: BAC-1311
- The public API example can not be build without access to Backbone's parent pomBAC-1308Resolved issue: BAC-1308
- NullPointerException when synchronizing a field if mapping can not be foundBAC-1307Resolved issue: BAC-1307
- Importing a configuration fails for distributed configurations using the REST APIBAC-1306Resolved issue: BAC-1306
- The User Passthrough Mapping (by email) is case sensitiveBAC-1305Resolved issue: BAC-1305
- Improve the way we set the clause name when looking for auto complete suggestionsBAC-1302Resolved issue: BAC-1302
- Sync info panel (sometimes) displays wrong number last received/sentBAC-1287Resolved issue: BAC-1287
- When importing paired issue data also update the Sync Info Panel tooBAC-1283Resolved issue: BAC-1283
- improve wording for "restricting" view of the sync info panelBAC-1264Resolved issue: BAC-1264
- S2S and S2C: Status value not correctly mapped to Textfield if BB performs the status transitionBAC-818Resolved issue: BAC-818
- Use fallback user also if user is inactiveBAC-796Resolved issue: BAC-796
- Add global administration settings UIBAC-173Resolved issue: BAC-173
22 of 22
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.