[jira] [Commented] (DERBY-5237) interrupting thread performing create table doesn't cause SQLException with sql state 08000

[ https://issues.apache.org/jira/browse/DERBY-5237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13041784#comment-13041784 ] Jim Newsham commented on DERBY-5237: I tested a build from the 10.8 branch and it

[jira] [Commented] (DERBY-5237) interrupting thread performing create table doesn't cause SQLException with sql state 08000

[ https://issues.apache.org/jira/browse/DERBY-5237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13035665#comment-13035665 ] Jim Newsham commented on DERBY-5237: Thanks for the comments Dag. Unfortunately JIRA

[jira] [Created] (DERBY-5237) interrupting thread performing create table doesn't cause SQLException with sql state 08000

interrupting thread performing create table doesn't cause SQLException with sql state 08000 --- Key: DERBY-5237 URL: https://issues.apache.org/jira/browse/DERBY-5237

[jira] [Updated] (DERBY-5237) interrupting thread performing create table doesn't cause SQLException with sql state 08000

[ https://issues.apache.org/jira/browse/DERBY-5237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jim Newsham updated DERBY-5237: --- Attachment: DerbyInterruptTest.java interrupting thread performing create table doesn't cause

[jira] [Commented] (DERBY-5237) interrupting thread performing create table doesn't cause SQLException with sql state 08000

[ https://issues.apache.org/jira/browse/DERBY-5237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13035036#comment-13035036 ] Jim Newsham commented on DERBY-5237: I have attached a junit test suite named

[jira] [Commented] (DERBY-5237) interrupting thread performing create table doesn't cause SQLException with sql state 08000

[ https://issues.apache.org/jira/browse/DERBY-5237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13035040#comment-13035040 ] Jim Newsham commented on DERBY-5237: One more comment. Instead of just looking at the

[jira] Commented: (DERBY-3939) IllegalMonitorStateException in PreparedStatement.executeUpdate()

[ https://issues.apache.org/jira/browse/DERBY-3939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12706724#action_12706724 ] Jim Newsham commented on DERBY-3939: As suggested, we are now using a debug build of

[jira] Created: (DERBY-3939) IllegalMonitorStateException in PreparedStatement.executeUpdate()

IllegalMonitorStateException in PreparedStatement.executeUpdate() - Key: DERBY-3939 URL: https://issues.apache.org/jira/browse/DERBY-3939 Project: Derby Issue Type: Bug

[jira] Created: (DERBY-3093) intermittent transaction failure caused by internal duplicate savepoint name, for tirgger

intermittent transaction failure caused by internal duplicate savepoint name, for tirgger - Key: DERBY-3093 URL: https://issues.apache.org/jira/browse/DERBY-3093

[jira] Commented: (DERBY-2689) Deadlock with GenericPreparedStatement

[ https://issues.apache.org/jira/browse/DERBY-2689?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12501707 ] Jim Newsham commented on DERBY-2689: We are experiencing deadlock at the same location. This is with Derby

[jira] Updated: (DERBY-2689) Deadlock with GenericPreparedStatement

[ https://issues.apache.org/jira/browse/DERBY-2689?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jim Newsham updated DERBY-2689: --- Attachment: TestDerbyPreparedStatements.java The attached test case deadlocks pretty quickly for me.

[jira] Created: (DERBY-2364) improve documentation to explain logged/unlogged operations

improve documentation to explain logged/unlogged operations --- Key: DERBY-2364 URL: https://issues.apache.org/jira/browse/DERBY-2364 Project: Derby Issue Type: Improvement