All,
As per the gpc-dev call today, please see Jira CORE issue 149: JDBC calls to
interrupted threads throw
sqlexceptions<https://community.i2b2.org/jira/browse/CORE-149?jql=text%20~%20%22Interrupted%20attempting%20lock%22>
for work on long-running i2b2 queries that get stuck in a "processing" state
and never return. Note that you have to log in to the Jira system in order to
see the ticket information - otherwise Jira reports "No issues were found to
match your search".
Michael Horvath said in the description:
> As a temporary fix, we've commented out the t.interrupt() call without any
> ill effects.
Specifically, here's the text from the patch we applied at KUMC:
---
./i2b2_1704_orig/edu.harvard.i2b2.crc/src/server/edu/harvard/i2b2/crc/ejb/QueryManagerBeanUtil.java
2014-11-06 15:48:08.000000000 -0600
+++
./i2b2_1704/edu.harvard.i2b2.crc/src/server/edu/harvard/i2b2/crc/ejb/QueryManagerBeanUtil.java
2015-02-10 08:35:26.000000000 -0600
@@ -231,7 +231,7 @@
throw new I2B2Exception("Thread error while
running CRC job "
, e);
} finally {
- t.interrupt();
+ //t.interrupt();
//exec = null;
t = null;
}
_______________________________________________
Gpc-dev mailing list
[email protected]
http://listserv.kumc.edu/mailman/listinfo/gpc-dev
