[DERBY-6518] JVMInfo should not use parseFloat() to parse java.specification.version

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 10.10.1.1
• Fix Version/s: 10.10.2.1, 10.11.1.1
• Component/s: Services
• Labels: derby_backport_reject_10_9
• Urgency: Normal
• Assignee: Knut Anders Hatlen
• Reporter: Knut Anders Hatlen
• Created: 18/Mar/14 10:08
• Updated: 09/Sep/16 09:51
• Resolved: 08/Oct/14 18:19

Description

JVMInfo uses parseFloat() to parse the java.specification.version property. That won't work correctly if the minor version has more than one digit. It should order the versions like this:

1.7 < 1.8 < 1.9 < 1.10 < 1.11

With parseFloat(), they are ordered like this instead:

1.10 < 1.11 < 1.7 < 1.8 < 1.9

The result is that newer Java versions will be classified as older, less capable ones, and some functionality might be disabled because Derby thinks the platform is not capable of providing it.

Issue Links

• is related to: DERBY-6755 Error in MathTrigFunctionsTest.testRadians
• is related to: DERBY-6756 intermittent test failure with 10.10 in tests.compatibility.VersionedNetworkServerTestSetup and ClientCompatibilityRunControl
• relates to: DERBY-6759 Derby 10.10 backport issue (fall 2014)