I don't think it is correct to simply close this bug. When not using JDBC-level streams, the problem still occurs.