[jira] [Updated] (DERBY-5554) NullPointerException in generated VTI code

2011-12-23 Thread Knut Anders Hatlen (Updated) (JIRA)
[ https://issues.apache.org/jira/browse/DERBY-5554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Knut Anders Hatlen updated DERBY-5554: -- Affects Version/s: 10.3.1.4 10.4.1.3

[jira] [Created] (DERBY-5555) Execution Time with a Statement 1 ms with a PreparedStatement 3 minutes

2011-12-23 Thread Steffen Kuche (Created) (JIRA)
Execution Time with a Statement 1 ms with a PreparedStatement 3 minutes --- Key: DERBY- URL: https://issues.apache.org/jira/browse/DERBY- Project: Derby Issue Type:

[jira] [Updated] (DERBY-5555) Execution Time with a Statement 1 ms with a PreparedStatement 3 minutes

2011-12-23 Thread Steffen Kuche (Updated) (JIRA)
[ https://issues.apache.org/jira/browse/DERBY-?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steffen Kuche updated DERBY-: - Description: Sounds incrediable? Test it by yourself with the attached program. The issued

[jira] [Updated] (DERBY-5555) Execution Time with a Statement 1 ms and with a PreparedStatement about 4 minutes

2011-12-23 Thread Steffen Kuche (Updated) (JIRA)
[ https://issues.apache.org/jira/browse/DERBY-?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steffen Kuche updated DERBY-: - Summary: Execution Time with a Statement 1 ms and with a PreparedStatement about 4 minutes

[jira] [Updated] (DERBY-5555) Execution Time with a Statement 1 ms with a PreparedStatement 3 minutes

2011-12-23 Thread Steffen Kuche (Updated) (JIRA)
[ https://issues.apache.org/jira/browse/DERBY-?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steffen Kuche updated DERBY-: - Description: Sounds incrediable? Test it by yourself with the attached program. The issued

[jira] [Updated] (DERBY-5555) Execution Time with a Statement 1 ms and with a PreparedStatement about 4 minutes

2011-12-23 Thread Steffen Kuche (Updated) (JIRA)
[ https://issues.apache.org/jira/browse/DERBY-?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steffen Kuche updated DERBY-: - Attachment: test.zip Execution Time with a Statement 1 ms and with a PreparedStatement

[jira] [Updated] (DERBY-5555) Execution Time with a Statement 1 ms and with a PreparedStatement about 4 minutes

2011-12-23 Thread Steffen Kuche (Updated) (JIRA)
[ https://issues.apache.org/jira/browse/DERBY-?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steffen Kuche updated DERBY-: - Description: Sounds incrediable? Test it by yourself with the attached program. The issued

[jira] [Updated] (DERBY-5555) Execution Time with a Statement 1 ms and with a PreparedStatement about 4 minutes

2011-12-23 Thread Steffen Kuche (Updated) (JIRA)
[ https://issues.apache.org/jira/browse/DERBY-?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steffen Kuche updated DERBY-: - Affects Version/s: 10.8.1.2 10.8.2.2 Execution Time with a Statement

RE: [jira] [Commented] (DERBY-5552) Derby threads hanging when using ClientXADataSource and a deadlock or lock timeout occurs

2011-12-23 Thread Bergquist, Brett
Well, I see that at the start of the execution, even on the next retry, the isValid is true for the statement. Something comes along and changes the state of isValid. I am having trouble finding out what with the debugger because there are quite a few threads running (statistics daemon for

RE: [jira] [Commented] (DERBY-5552) Derby threads hanging when using ClientXADataSource and a deadlock or lock timeout occurs

2011-12-23 Thread Bergquist, Brett
It is the IndexStatisticsDaemonImpl that is invalidating the statement. To verify this, I got my test case where it was in this loop. With my printouts I was seeing that the isValid was being set by the thread that was stuck right after the timeout occurred and then I immediately saw

Regression Test Report - Daily 1222350 - Sun DBTG

2011-12-23 Thread Ole . Solberg
[Auto-generated mail] *Daily* 1222350/2011-12-22 18:00:08 MET Failed TestsOK Skip Duration Suite --- *Jvm: 1.7* lin 01471014710 0 .% suitesAll 01515 0 .% jdbcapiAutoLoad 014

[jira] [Updated] (DERBY-866) Derby User Management Enhancements

2011-12-23 Thread Rick Hillegas (Updated) (JIRA)
[ https://issues.apache.org/jira/browse/DERBY-866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rick Hillegas updated DERBY-866: Attachment: derby-866-08-aa-passwordHasher.diff Attaching derby-866-08-aa-passwordHasher.diff.

[jira] [Updated] (DERBY-866) Derby User Management Enhancements

2011-12-23 Thread Rick Hillegas (Updated) (JIRA)
[ https://issues.apache.org/jira/browse/DERBY-866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rick Hillegas updated DERBY-866: Attachment: derby-866-08-ab-passwordHasher.diff Attaching derby-866-08-ab-passwordHasher.diff. The

[jira] [Created] (DERBY-5556) NULLIF and CASE return different result

2011-12-23 Thread hleem (Created) (JIRA)
NULLIF and CASE return different result --- Key: DERBY-5556 URL: https://issues.apache.org/jira/browse/DERBY-5556 Project: Derby Issue Type: Bug Components: SQL Affects Versions: 10.8.1.2

[jira] [Commented] (DERBY-866) Derby User Management Enhancements

2011-12-23 Thread Rick Hillegas (Commented) (JIRA)
[ https://issues.apache.org/jira/browse/DERBY-866?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13175582#comment-13175582 ] Rick Hillegas commented on DERBY-866: - Tests passed cleanly except for an error in the

Re: [jira] [Commented] (DERBY-5552) Derby threads hanging when using ClientXADataSource and a deadlock or lock timeout occurs

2011-12-23 Thread Kristian Waagan
On 23.12.2011 17:49, Bergquist, Brett wrote: It is the IndexStatisticsDaemonImpl that is invalidating the statement. To verify this, I got my test case where it was in this loop. With my printouts I was seeing that the isValid was being set by the thread that was stuck right after the

RE: [jira] [Commented] (DERBY-5552) Derby threads hanging when using ClientXADataSource and a deadlock or lock timeout occurs

2011-12-23 Thread Bergquist, Brett
If I disable the istat daemon, I still the the timeout but now the error is reported as it should and the transaction is aborted and my code continues. With the itstat deamon enabled, then the lock timeout is discovered and signaled by exception being thrown but between the time it gets caught

[jira] [Commented] (DERBY-5549) Questionable behaviour of PooledConnection after receiving an interrupt

2011-12-23 Thread Dag H. Wanvik (Commented) (JIRA)
[ https://issues.apache.org/jira/browse/DERBY-5549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13175665#comment-13175665 ] Dag H. Wanvik commented on DERBY-5549: -- Yes, I am seeing this. Looks wrong.

[jira] [Commented] (DERBY-5546) ResultSet#updateBigDecimal on a REAL column does not do underflow checking

2011-12-23 Thread Dag H. Wanvik (Commented) (JIRA)
[ https://issues.apache.org/jira/browse/DERBY-5546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13175668#comment-13175668 ] Dag H. Wanvik commented on DERBY-5546: -- Yes, I would agree that the converting -0.1