db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kathey Marsden (JIRA)" <derby-...@db.apache.org>
Subject [jira] Commented: (DERBY-149) Server hang when invalid string is bound to datetime columns.
Date Mon, 26 Sep 2005 19:42:48 GMT
    [ http://issues.apache.org/jira/browse/DERBY-149?page=comments#action_12330500 ] 

Kathey Marsden commented on DERBY-149:

checked in fix to  the trunk.  Thanks Arm for looking at it so carefully.

Date: Mon Sep 26 12:39:26 2005
New Revision: 291721

URL: http://svn.apache.org/viewcvs?rev=291721&view=rev
Fix Server hang when invalid string is bound to datetime columns.
Changes network server to skip only the current DSS and not all chained DSS's 
when parsing parameter data in SQLDTA.

> Server hang when invalid string is bound to datetime columns.
> -------------------------------------------------------------
>          Key: DERBY-149
>          URL: http://issues.apache.org/jira/browse/DERBY-149
>      Project: Derby
>         Type: Bug
>   Components: Network Server
>  Environment: Derby running with Network Server via JDBC universal driver.
>     Reporter: A B
>     Assignee: Kathey Marsden

> When running against Derby Network Server with the JCC driver, attempts to bind an invalid
date/time string to a date/time/timestamp parameter lead to a hang in either the JCC client
or in the Network Server (not sure which).
> The problem does NOT occur if the same thing is run against a DB2 server, which suggests
the bug is in Network Server, not in the JCC driver.  That said, though, the problem also
does NOT happen if one uses an ODBC client to connect to Network Server, instead of a JDBC
client--so perhaps it's a problem with JCC, after all...hard to say one way or the other...
> Here's a simple program to reproduce the problem:
> import java.sql.*;
> public class go {
> 	public static void main (String[] args) throws Exception {
> 		Class.forName("com.ibm.db2.jcc.DB2Driver");
> 		Connection c = DriverManager.getConnection(
> 			"jdbc:derby:net://localhost:1527/ugh;create=true", "bah", "humbug");
> 		Statement s = c.createStatement();
> 		try {
> 			s.execute("drop table dt");
> 		} catch (SQLException se) {}
> 		s.execute("create table dt (d date)");
> 		PreparedStatement pSt = c.prepareStatement("insert into dt values (?)");
> 		try {
> 			pSt.setString(1, "oops"); // invalid date value.
> 			pSt.execute();
> 		} catch (SQLException se) {
> 			System.out.println("Got " + se.getSQLState() + ": " + se.getMessage());
> 		}
> 	}
> }
> Of course, in order for the program to run, one must start the Network Server on port
1527 first.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message