[jira] Commented: (DERBY-2083) Shutting down a database loaded from a jar leaves an open file reference to the jar file containing the database.

[ http://issues.apache.org/jira/browse/DERBY-2083?page=comments#action_12456730 ] Øystein Grøvlen commented on DERBY-2083: The tinderbox test indicates that something has been broken by this fix. Several tests now fail with: ERROR

[jira] Updated: (DERBY-1856) Multiple communication failures when starting server with derby.drda.timeSlice

[ http://issues.apache.org/jira/browse/DERBY-1856?page=all ] Bernt M. Johnsen updated DERBY-1856: Attachment: DERBY-1856-r126392-regressionfix.diff The exception thrown is caused by a regression introduced in r126392 (2005-01-25) and is easily fixed

[jira] Updated: (DERBY-1165) A test checking the transaction ids returned by xa_recover is needed

[ http://issues.apache.org/jira/browse/DERBY-1165?page=all ] Knut Anders Hatlen updated DERBY-1165: -- Affects Version/s: 10.2.1.6 A test checking the transaction ids returned by xa_recover is needed

[jira] Updated: (DERBY-1856) Multiple communication failures when starting server with derby.drda.timeSlice

[ http://issues.apache.org/jira/browse/DERBY-1856?page=all ] Bernt M. Johnsen updated DERBY-1856: Derby Info: [Patch Available] Multiple communication failures when starting server with derby.drda.timeSlice

[jira] Updated: (DERBY-1856) Multiple communication failures when starting server with derby.drda.timeSlice

[ http://issues.apache.org/jira/browse/DERBY-1856?page=all ] Bernt M. Johnsen updated DERBY-1856: Affects Version/s: 10.2.1.6 Multiple communication failures when starting server with derby.drda.timeSlice

[jira] Commented: (DERBY-1165) A test checking the transaction ids returned by xa_recover is needed

[ http://issues.apache.org/jira/browse/DERBY-1165?page=comments#action_12456740 ] Knut Anders Hatlen commented on DERBY-1165: --- Since this is already tested in jdk1.3, and jdk 1.3 will not be supported in 10.3, I suggest that we close

[jira] Commented: (DERBY-1434) Client can send incorrect database name to server after having made multiple connections to different databases.

[ http://issues.apache.org/jira/browse/DERBY-1434?page=comments#action_12456741 ] Julius Stroffek commented on DERBY-1434: Could we just remove the static modifier from the fields noHoldPKGNAMCBytes and holdPKGNAMCBytes of the

[jira] Updated: (DERBY-1856) Multiple communication failures when starting server with derby.drda.timeSlice

[ http://issues.apache.org/jira/browse/DERBY-1856?page=all ] Bernt M. Johnsen updated DERBY-1856: Fix Version/s: 10.1.3.2 10.2.2.0 10.3.0.0 Derby Info: [Patch Available, Regression] (was: [Patch

Re: Releasing latches when waiting for locks. When and why?

While I'm not an expert on the subject matter, I can't help myself but chime in and share my thoughts on this... =) During the course of our project on analyzing Derby's SMP scalability properties, we've investigated Derby's locking and latching pretty thoroughly. We've followed this thread with

[jira] Created: (DERBY-2165) Implement testing of derby.drda.timeSlice property

Implement testing of derby.drda.timeSlice property -- Key: DERBY-2165 URL: http://issues.apache.org/jira/browse/DERBY-2165 Project: Derby Issue Type: Test Components: Test

[jira] Created: (DERBY-2166) Implement proper handling of SoecketTimeoutException in DRDAConnThread

Implement proper handling of SoecketTimeoutException in DRDAConnThread -- Key: DERBY-2166 URL: http://issues.apache.org/jira/browse/DERBY-2166 Project: Derby Issue Type:

[jira] Commented: (DERBY-2166) Implement proper handling of SoecketTimeoutException in DRDAConnThread

[ http://issues.apache.org/jira/browse/DERBY-2166?page=comments#action_12456755 ] Bernt M. Johnsen commented on DERBY-2166: - SocketTimeoutException was introduced in JDK 1.4 Implement proper handling of SoecketTimeoutException in

[jira] Updated: (DERBY-2166) Implement proper handling of SocketTimeoutException in DRDAConnThread

[ http://issues.apache.org/jira/browse/DERBY-2166?page=all ] Bernt M. Johnsen updated DERBY-2166: Summary: Implement proper handling of SocketTimeoutException in DRDAConnThread (was: Implement proper handling of SoecketTimeoutException in

[jira] Commented: (DERBY-2107) Move page latching out of the lock manager

[ http://issues.apache.org/jira/browse/DERBY-2107?page=comments#action_12456770 ] Knut Anders Hatlen commented on DERBY-2107: --- The first may have been an existing issue: 1) The field nestedLatch is used under synchronization when

Re: Should be a statement with error allowed to do a rollback of the active transaction

In this case, user may have troubles - for example when executing an sql script through ij with autocommit off - the part of the transaction code would be rollbacked and part of the code will be committed by the following commit. When an error is produced by the transaction transaction may

[jira] Updated: (DERBY-1856) Multiple communication failures when starting server with derby.drda.timeSlice

[ http://issues.apache.org/jira/browse/DERBY-1856?page=all ] Bernt M. Johnsen updated DERBY-1856: Attachment: DERBY-1856-r126392-regressionfix-v2.diff Added a comment Multiple communication failures when starting server with derby.drda.timeSlice

Re: Should be a statement with error allowed to do a rollback of the active transaction

Could we unify the behavior of the embedded configuration and a derby net ? Julo Knut Anders Hatlen wrote: Bryan Pendleton [EMAIL PROTECTED] writes: The key question is whether the statement with error should (or could) rollback the active transaction? Does this same situation

[jira] Commented: (DERBY-1856) Multiple communication failures when starting server with derby.drda.timeSlice

[ http://issues.apache.org/jira/browse/DERBY-1856?page=comments#action_12456829 ] Øystein Grøvlen commented on DERBY-1856: The fix looks good. +1 to commit. It would be great if you would make a test for timeSlice, too. Multiple

[jira] Commented: (DERBY-1856) Multiple communication failures when starting server with derby.drda.timeSlice

[ http://issues.apache.org/jira/browse/DERBY-1856?page=comments#action_12456837 ] Bernt M. Johnsen commented on DERBY-1856: - I have created DERBY-2165 for the test. Multiple communication failures when starting server with

[jira] Commented: (DERBY-1856) Multiple communication failures when starting server with derby.drda.timeSlice

[ http://issues.apache.org/jira/browse/DERBY-1856?page=comments#action_12456839 ] Bernt M. Johnsen commented on DERBY-1856: - Committed revision 484615 on trunk Multiple communication failures when starting server with

[jira] Resolved: (DERBY-1856) Multiple communication failures when starting server with derby.drda.timeSlice

[ http://issues.apache.org/jira/browse/DERBY-1856?page=all ] Bernt M. Johnsen resolved DERBY-1856. - Resolution: Fixed Derby Info: [Regression] (was: [Patch Available, Regression]) Committed revision 484616 on 10.2 Multiple communication

[jira] Reopened: (DERBY-2083) Shutting down a database loaded from a jar leaves an open file reference to the jar file containing the database.

[ http://issues.apache.org/jira/browse/DERBY-2083?page=all ] Daniel John Debrunner reopened DERBY-2083: -- Shutting down a database loaded from a jar leaves an open file reference to the jar file containing the database.

10.2.2 delayed one day

I'm expecting Java SE 6 to go GA on Monday so I'm hoping to build the 10.2.2 release candidate then rather than today. Thanks to everyone for all the hard work so far! Regards, -Rick

Re: [jira] Commented: (DERBY-2107) Move page latching out of the lock manager

Mike Matrigali wrote: I assume changes to remove latching out of lock manage will break existing in progress work to do in memory store - but I don't know for sure. I would not think so since AFAIK that work is just replacing the current io system with memory. Hence, it should still operate

[jira] Commented: (DERBY-1709) Deprecate scripts in frameworks directory

[ http://issues.apache.org/jira/browse/DERBY-1709?page=comments#action_12456877 ] Bryan Pendleton commented on DERBY-1709: I have to say that derbyrun.jar is just so darn cool, that nowadays I never seem to use the scripts at all. I

Re: 10.2.2 delayed one day

Rick Hillegas wrote: I'm expecting Java SE 6 to go GA on Monday so I'm hoping to build the 10.2.2 release candidate then rather than today. Thanks to everyone for all the hard work so far! thanks for the update, Rick, -jean

[jira] Subscription: Derby: JIRA issues with patch available

Issue Subscription Filter: Derby: JIRA issues with patch available (12 issues) Subscriber: derby-dev Key Summary DERBY-2107 Move page latching out of the lock manager http://issues.apache.org/jira/browse/DERBY-2107 DERBY-606 SYSCS_UTIL.SYSCS_INPLACE_COMPRESS_TABLE fails on

[jira] Commented: (DERBY-408) Fix formatting of manuals in PDF output

[ http://issues.apache.org/jira/browse/DERBY-408?page=comments#action_12456889 ] Kim Haase commented on DERBY-408: - Thanks a million, Andrew. nbsp; works. Fix formatting of manuals in PDF output ---

[jira] Commented: (DERBY-2107) Move page latching out of the lock manager

[ http://issues.apache.org/jira/browse/DERBY-2107?page=comments#action_12456903 ] Daniel John Debrunner commented on DERBY-2107: -- Sorry, I was wrong on issue 2), got confused mentally walking through the code. Though the patch does

Re: Should be a statement with error allowed to do a rollback of the active transaction

Julius Stroffek wrote: In this case, user may have troubles - for example when executing an sql script through ij with autocommit off - the part of the transaction code would be rollbacked and part of the code will be committed by the following commit. ij is not intended as an application

Regression Test Report - Daily 483545 - Sun DBTG

[Auto-generated mail] *Daily* 483545/2006-12-07 18:00:09 MET Failed TestsOK Skip Duration Suite --- *Jvm: 1.6* lin 0517517 096.91% derbyall 064756475 0 149.55%

10.2.2 JDBC4 disclaimer and Eclipse UI plugin

It looks like we're very close to being able to build 10.2.2 with a production Java SE 6 (on Monday). I think we can polish off the last bits of 10.2.2 now. Hi Jean, You kindly volunteered to remove the JDBC4 disclaimers from the 10.2 docs. I think it's ok to do this now. Hi Raj, You

Regression Test Report - tinderbox_trunk15 484616 - Sun DBTG

[Auto-generated mail] *tinderbox_trunk15* 484616/2006-12-08 15:22:19 CET Failed TestsOK Skip Duration Suite --- *Jvm: 1.5* SunOS-5.10_i86pc-i386 10509499 2 120.07% derbyall 022312231 0

[jira] Commented: (DERBY-2129) Tasks related to releasing 10.2.2

[ http://issues.apache.org/jira/browse/DERBY-2129?page=comments#action_12456923 ] Jean T. Anderson commented on DERBY-2129: - Removed JDBC 4 disclaimer from docs in the 10.2 branch, revision 484667. Originally I had hoped that simply

[jira] Commented: (DERBY-2143) Updated localized messages for Derby 10.2

[ http://issues.apache.org/jira/browse/DERBY-2143?page=comments#action_12456927 ] Myrna van Lunteren commented on DERBY-2143: --- I committed changes from patch DERBY_2143_2110_trunk.diff2 with revision 484671 and from patch

Re: 10.2.2 JDBC4 disclaimer and Eclipse UI plugin

Rick Hillegas wrote: It looks like we're very close to being able to build 10.2.2 with a production Java SE 6 (on Monday). I think we can polish off the last bits of 10.2.2 now. Hi Jean, You kindly volunteered to remove the JDBC4 disclaimers from the 10.2 docs. I think it's ok to do this

[jira] Updated: (DERBY-2125) Getting Started with Derby - Installing Derby

[ http://issues.apache.org/jira/browse/DERBY-2125?page=all ] Andrew McIntyre updated DERBY-2125: --- Fix Version/s: 10.2.2.0 (was: 10.0.2.2) correcting fix version Getting Started with Derby - Installing Derby

Re: 10.2.2 JDBC4 disclaimer and Eclipse UI plugin

Thanks! Rajesh Kartha wrote: Rick Hillegas wrote: It looks like we're very close to being able to build 10.2.2 with a production Java SE 6 (on Monday). I think we can polish off the last bits of 10.2.2 now. Hi Jean, You kindly volunteered to remove the JDBC4 disclaimers from the 10.2

[jira] Updated: (DERBY-1871) testSecMec failing with what looks like just a error message change diff

[ http://issues.apache.org/jira/browse/DERBY-1871?page=all ] Andrew McIntyre updated DERBY-1871: --- Fix Version/s: 10.1.4.0 (was: 10.1.3.2) Priority: Minor (was: Major) Marking minor, difference in exception text between

Issue with Derby Views

Hi All, The following problem essentially has to do with accessing a view made up of more than 300 tables. We found out that by reducing the number of tables in the view, we managed to eliminate the problem. But when we exceed approximately 300 tables per view, the issue started to surface.