Double value 'infinity' causes IllegalArgumentException

Question

Trying to bind the value Double.POSITIVE_INFINITY in a prepared statement causes an IllegalArgumentException using ojdbc6 11.2.0.4.0 but it works fine in version 11.2.0.3.0:
Exception in thread "main" java.lang.IllegalArgumentException: Overflow
    at oracle.jdbc.driver.OraclePreparedStatement.setDoubleInternal(OraclePreparedStatement.java:7605)
    at oracle.jdbc.driver.OraclePreparedStatement.setDouble(OraclePreparedStatement.java:7513)
    at oracle.jdbc.driver.OraclePreparedStatementWrapper.setDouble(OraclePreparedStatementWrapper.java:494)
    at DoubleOverflow.main(DoubleOverflow.java:26)
Source:
import java.sql.*;
import oracle.jdbc.pool.OracleDataSource;
public class DoubleOverflow
  public static void main (String[] args) throws SQLException {
    OracleDataSource ods = new OracleDataSource();
    ods.setUser(System.getProperty("DB_USER"));
    ods.setPassword(System.getProperty("DB_PASSWORD"));
    ods.setURL(System.getProperty("JDBC_URL"));
    Connection conn = ods.getConnection();
    PreparedStatement pstmtCreateTable = conn.prepareStatement("create table ojdbc6test (d BINARY_DOUBLE)");
    try {
        pstmtCreateTable.execute();
    } catch (Exception ex) {
        if (ex.getMessage().contains("ORA-00955")) {
            System.err.println("Test table already created - ignore SQL error and continue");
        } else throw ex;
    pstmtCreateTable.close();
    PreparedStatement pstmt = conn.prepareStatement ("insert into ojdbc6test (d) VALUES (?)");
    // This will cause an IllegalArgumentException in ojdbc6 11.2.0.4.0 but not in 11.2.0.3.0
    pstmt.setDouble(1, Double.POSITIVE_INFINITY);
    pstmt.execute ();
    pstmt.close();
    conn.close();
The database used is 'Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production'. I don't see any mention regarding changes to this in the 11.2.0.4.0 change log. Is this a bug in the driver or is there some other explanation?

Answer 1

Thanks -
Testing shows that the driver code was changed to check for underflow/overflow but doesn't appear to take the two INFINITY constant values into account properly.
Whether that was done INTENTIONALLY or not I don't know.
I suspect it is a bug in the new driver code.
If you have a MOS account you shouild submit a bug report to Oracle and include the example code you posted above.
I doubt if there is any workaround.