[ http://issues.apache.org/jira/browse/DERBY-151?page=comments#action_12329329 ]
Suresh Thalamati commented on DERBY-151: ---------------------------------------- derby.log occasional has more information than the above stack mentioned. In most cases , some sort of IO exception has to happen for the above error to occur, all the exception are nested inside the SQL Exception. If the derby.log file is still around , please attach it to the jira. > Thread termination -> XSDG after operation is 'complete' > -------------------------------------------------------- > > Key: DERBY-151 > URL: http://issues.apache.org/jira/browse/DERBY-151 > Project: Derby > Type: Bug > Components: Store > Versions: 10.0.2.1 > Environment: Linux kernel 2.4.21-243-athlon (SuSE 9.0) > Reporter: Barnet Wagman > > I've encountered what appears to be a bug related to threading. After an > INSERT operation, if the invoking thread terminates too quickly, Derby throws > an XSDG. > The bug is a bit difficult to isolate but it occurs consistently in the > following situation (with a particular database and an operation of a > particular size): > Derby is running in embedded mode with autocommit on. > The application performs an INPUT operation from a thread that is not the > main thread. The INPUT is issued using a PreparedStatement. The INPUT adds > ~ 256 records of six fields each. (Note that INSERTs of this size seem to > work fine in other contexts.) > > The preparedStatement.executeUpdate() seems to excute successfully; at least > it returns without throwing an exception. > The thread that invoked the INPUT operation then terminates (but NOT the > application). The next INPUT operation then results in an > "ERROR XSDG1: Page Page(7,Container(0, 1344)) could not be written to disk, > please check if disk is full." > The disk is definitely not full. > HOWEVER, if I put the calling thread to sleep for a second before it exits, > the problem does not occur. > I'm not quite sure what to make of this. I was under the impression that > most of Derby's activity occurs in the application's threads. Could Derby be > creating a child thread from in the application thread, which dies when the > parent thread terminates? > Thanks -- 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
