How bad is its impact? (Severity)
Limited, but we at this point we lag one minor JavaDB release behind.
How often does it happen? Will many users see this problem?
How much effort is required to fix it?
Minimal, updated JavaDB version is available and only needs to be integrated into 3.1 workspace as binary dependency.
What is the risk of fixing it and how will the risk be mitigated? (Risk)
Minimal risk - preliminary CTS and smoke testing have been done with JavaDB 10.6.2.1 and we got a green light to integrate from Lance Andersen.