Limitiations on Sybase ResultSet implementation causes unit tets failures ------------------------------------------------------------------------- Key: HHH-3675 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3675 Project: Hibernate Core Issue Type: Bug Components: core Reporter: Gail Badner Assignee: Gail Badner Fix For: 3.2.x, 3.3.x, 3.4 CMTTest.testCurrentSessionWithScroll() fails using Sybase because it calls ResultSet.isLast() and the Sybase implentation throws com.sybase.jdbc2.utils.UnimplementedOperationException. The exception message is, "The method com.sybase.jdbc2.jdbc.SybResultSet.isLast() has not been completed and should not be called.". AggressiveReleaseTest,testSerializationFailsOnAfterStatementAggressiveReleaseWithOpenResources() throws NullPointerException when a ResultSet is closed before reading any rows. The exception is: java.lang.NullPointerException at com.sybase.jdbc2.tds.TdsResultSet.next(TdsResultSet.java:313) at com.sybase.jdbc2.tds.TdsResultSet.close(TdsResultSet.java:452) at com.sybase.jdbc2.jdbc.SybResultSet.markDead(SybResultSet.java:1540) at com.sybase.jdbc2.jdbc.SybResultSet.close(SybResultSet.java:1608) at com.sybase.jdbc2.jdbc.SybResultSet.close(SybResultSet.java:193) at org.hibernate.jdbc.AbstractBatcher.closeQueryStatement(AbstractBatcher.java:207) at org.hibernate.impl.AbstractScrollableResults.close(AbstractScrollableResults.java:99) at org.hibernate.test.connections.AggressiveReleaseTest.testSerializationFailsOnAfterStatementAggressiveReleaseWithOpenResources(AggressiveReleaseTest.java:112) at org.hibernate.junit.functional.FunctionalTestCase.runTest(FunctionalTestCase.java:102) at org.hibernate.junit.UnitTestCase.runBare(UnitTestCase.java:34) at org.hibernate.junit.functional.FunctionalTestClassTestSuite.runTest(FunctionalTestClassTestSuite.java:100) at org.hibernate.junit.functional.FunctionalTestClassTestSuite.run(FunctionalTestClassTestSuite.java:69) CurrentSessionConnectionTest extends AggressiveReleaseTest, so NullPointerException is thrown for the same reason. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira