[ http://issues.apache.org/jira/browse/DERBY-1395?page=comments#action_12417318 ]
Deepa Remesh commented on DERBY-1395: ------------------------------------- I had seen the first scenario (both connection and statement closed) in jdbcapi/checkDataSource.java.This is in the checkConnection method. The scenario Knut mentions is covered in ClosedObjectTest.java. > Change the client SQLState to match that of embedded for the exception thrown > on a closed statement whose connection is also closed > ----------------------------------------------------------------------------------------------------------------------------------- > > Key: DERBY-1395 > URL: http://issues.apache.org/jira/browse/DERBY-1395 > Project: Derby > Type: Improvement > Components: Network Client > Versions: 10.2.0.0, 10.1.3.0 > Reporter: Deepa Remesh > Assignee: David Van Couvering > Priority: Trivial > > Scenario: Both connection and statement are closed and an operation is > performed on a closed statement. SQLStates are as follows: > Embedded: SQLSTATE: XJ012, Message: Statement Closed > Client before DERBY-843 fix: SQLSTATE = null, message = Statement closed > Client after DERBY-843 fix: SQLSTATE: 08003, Message: connection closed > This issue is related to the effort started in DERBY-254. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
