[DERBY-5519] Update code in JVMInfo#derbyVMLevel to give correct results for Java 7 and provisionally for 8.

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 10.9.1.0
• Component/s: JDBC
• Labels: derby_backport_reject_10_8 newbie
• Issue & fix info: Known fix
• Bug behavior facts: Deviation from standard
• Assignee: Dag H. Wanvik
• Reporter: Dag H. Wanvik
• Created: 02/Dec/11 23:29
• Updated: 15/Nov/13 08:15
• Resolved: 07/Dec/11 01:24

Description

The method derbyVMLevel gives correct result only up to and including Java 6, cf. this snippet:

public static String derbyVMLevel()
{
switch (JDK_ID)

{ case J2SE_14: return J2ME ? "J2ME - JDBC for CDC/FP 1.1" : "J2SE 1.4 - JDBC 3.0"; case J2SE_142: return "J2SE 1.4.2 - JDBC 3.0"; case J2SE_15: return "J2SE 5.0 - JDBC 3.0"; case J2SE_16: return "Java SE 6 - JDBC 4.0"; default: return "?-?"; }

}

This is exposed through our MBean implementation in org.apache.derby.jdbc.JDBC#getDriverLevel

Issue Links

• is related to: DERBY-5521 JDBCMBeanTest#testAttributeDriverLevel uses Java assert in lieu of JUnit assert: no real testing happens