BUG: JDBC Stored Proc with Output Date Param Causes Exception (195471)
The information in this article applies to:
This article was previously published under Q195471 SYMPTOMS Calling a stored procedure with output Date parameters from
JDBC can cause a java.lang.NumberFormatException. The exception text is of the
form:
*** Number Format Exception ***
java.lang.NumberFormatException: <garbage # here>
at java/lang/Integer.parseInt (Integer.java)
at java/lang/Integer.parseInt (Integer.java)
at java/sql/Timestamp.valueOf (Timestamp.java)
at com/ms/jdbc/odbc/JdbcOdbcCallableStatement.getTimestamp
(JdbcOdbcCallableStatement.java)
at com/ms/jdbc/odbc/JdbcOdbcCallableStatement.getObject
(JdbcOdbcCallableStatement.java)
at sdate.main (sdate.java:30)
CAUSE This happens in the implementation of the JDBC/ODBC bridge.
Note that calling GetTimestamp instead of getObject produces the same problem.
RESOLUTION Avoid using Date as an output parameter in a stored
procedure. STATUSMicrosoft has confirmed that this is a bug in the Microsoft
products that are listed at the beginning of this article.
| Modification Type: | Minor | Last Reviewed: | 2/11/2005 |
|---|
| Keywords: | kbbug kbDatabase kbpending KB195471 |
|---|
|