Issues

Select view

List view

Detail view

Select search mode

Basic

JQL

Connection errors when running Jira on Java 11 ( > 8)
BAC-1408
Resolved issue: BAC-1408
Provide multi-factor (2FA) or token-based authentication
BAC-1406
Resolved issue: BAC-1406
Synchronizations don't start automatically after restart
BAC-1405
Resolved issue: BAC-1405
Provide option to always use Basic Authentication
BAC-1399
Resolved issue: BAC-1399
Customer Request Types are not shown if >50 exist
BAC-1395
Resolved issue: BAC-1395
Make it possible to modify threadPool values like maxQueueSize
BAC-1383
Resolved issue: BAC-1383
Support correlation mapping for Watchers
BAC-1372
Resolved issue: BAC-1372

7 of 7

Connection errors when running Jira on Java 11 ( > 8)

Fixed

Description

When running Jira on Java 11 (>8) it could be that you cannot start the synchronization anymore due to a connection error in the logs.

Steps to Reproduce:

Run a standalone Jira on Java 8
Create a server <> cloud synchronization
Publish and start the configuration
Stop Jira
Install Java 11 and make it the default (e.g. by using https://sdkman.io/)
Run Jira again on Java 11
Start the synchronization
Restart required error shows up and start synchronization is not possible

Environment

None

Details

Assignee

Unassigned

Reporter

Sync User [K15t]

Deployment

Data Center

Priority

Major

Backbone Issue Sync

Created April 17, 2020 at 2:06 PM

Updated February 15, 2023 at 4:41 PM

Resolved June 15, 2020 at 6:45 AM

Configure

Activity

Show:

Liset de Bruin (K15t) June 26, 2020 at 9:14 AM

Hi Marcin,

thank you for your comment!
I wanted to let you know that we are currently working on fixing this issue to make Backbone work on Java>8 as well. We completely understand how this is a blocker for you at the moment.

As I see you are already watching the issue, you will get notified about further updates on the issue.
If you have any other questions or concerns, then just reach out to us.

Cheers,
Liset

Marcin Cimaszewski June 26, 2020 at 8:34 AM

Hi Team,

Please take that issue as priority task. Java >8 is becomming used wider. We’re in a position that our rollout is blocked due to that issue. Test env is running all other functionas are working but as sync is critical for us we cannot move that further.

Thanks for support and understanding,

Marcin

Former user June 19, 2020 at 8:52 AM

Hello,

unfortunately we had to reopen this issue as we’ve discovered some unexpected problems after merging the changes. The next Backbone release 4.2.0 (coming next week) will be released without this change. However, we’ll be working on this issue again and make sure to release it as soon as possible.

Sorry for the inconveniences.

Cheers,
Sebastian