[ http://issues.apache.org/jira/browse/DERBY-1453?page=comments#action_12420757 ]
Rajesh Kartha commented on DERBY-1453: -------------------------------------- I did some investigation on this. So there are two separate issues: A) Lock while updating an int col Scenario: 1) Open connection (conn1), set autocommit false 2) select int, clob from table 3) create another connection (conn2) , set autocommit false 4) attempt to update the clob column - pass 5) attempt to update the int col - fails with lock time out Since locks are not obtained on clobs step 4 works fine, whereas the update on the int (step 5) awaits the for the lock (step 2) to be released. I verified this behaviour on different cominations: 10.2 Embedded 10.2 Server and 10.2 Derby Client 10.1 Embedded 10.2 Server and 10.1 Derby Client 10.1 Server and 10.1 Derby Client - update does happen ! Only with the v10.1 Network Server (10.1.3.2 - (420033)), the update of the int col (step 5) goes thru fine. which I think is not a correct behavior and hence 10.1 NW Server seems to be issue. B) The error messages are different This would require a master update on the 10.1 branch to fix teh output expected in case of testing against a 10.2 server Both of the above issues are targetted for the 10.1 branch, hence I plan to: - change fix version to be 10.1.3.2 - lower the Priority from 'Critical' unless I hear otherwise. > jdbcapi/blobclob4BLOB.java fails with 10.1 client and 10.2 server > ----------------------------------------------------------------- > > Key: DERBY-1453 > URL: http://issues.apache.org/jira/browse/DERBY-1453 > Project: Derby > Type: Test > Components: Network Server, Network Client > Versions: 10.2.0.0, 10.1.3.0 > Environment: derbyclient.jar and derbyTesting.jar from 10.1 > all other jars from 10.2 > Reporter: Deepa Remesh > Priority: Critical > Fix For: 10.2.0.0 > > Diff is: > *** Start: blobclob4BLOB jdk1.5.0_02 DerbyNetClient derbynetmats:jdbcapi > 2006-06-23 02:09:39 *** > 510a511,513 > > FAIL -- unexpected exception **************** > > SQLSTATE(40XL1): A lock could not be obtained within the time requested > > START: clobTest93 > 512,513d514 > < START: clobTest93 > < clobTest92 finished > 766 del > < EXPECTED SQLSTATE(XCL30): An IOException was thrown when reading a > 'java.sql.String' from an InputStream. SQLSTATE: XJ001: Java exception: > 'ERROR 40XD0: Container has been closed: java.io.IOException'. > 766a767 > > EXPECTED SQLSTATE(XJ073): The data in this BLOB or CLOB is no longer > > available. The BLOB or CLOBs transaction may be committed, or its > > connection is closed. > 769 del > < EXPECTED SQLSTATE(XCL30): An IOException was thrown when reading a 'BLOB' > from an InputStream. SQLSTATE: XJ001: Java exception: 'ERROR 40XD0: Container > has been closed: java.io.IOException'. > 769a770 > > EXPECTED SQLSTATE(XJ073): The data in this BLOB or CLOB is no longer > > available. The BLOB or CLOBs transaction may be committed, or its > > connection is closed. > Test Failed. > *** End: blobclob4BLOB jdk1.5.0_02 DerbyNetClient derbynetmats:jdbcapi > 2006-06-23 02:10:20 *** -- 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
