[jira] Updated: (DERBY-2339) org.apache.derbyTesting.functionTests.suites.All is extremely CPU intensive since ~svn 507489

[ https://issues.apache.org/jira/browse/DERBY-2339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ole Solberg updated DERBY-2339: --- Description: Run org.apache.derbyTesting.functionTests.suites.All. http://www.nabble.com/org.apache.

[jira] Created: (DERBY-2339) org.apache.derbyTesting.functionTests.suites.All is extremely CPU intensive since ~svn 507489

org.apache.derbyTesting.functionTests.suites.All is extremely CPU intensive since ~svn 507489 - Key: DERBY-2339 URL: https://issues.apache.org/jira/browse/DERBY-2339

[jira] Commented: (DERBY-2249) Place holder to attach the long running test which will test Derby's improved optimizer

[ https://issues.apache.org/jira/browse/DERBY-2249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12473299 ] Bryan Pendleton commented on DERBY-2249: I'm a bit confused about the goal of this test. Is the idea: - run

Re: org.apache.derbyTesting.functionTests.suites.All is extremely CPU intensive!

On 2/14/07, Ole Solberg <[EMAIL PROTECTED]> wrote: Do anyone else see this? Yes, I am experiencing a similar situation with my Windows XP box today, I kicked off the JUnit tests using trunk svn 507732 about 2 hours ago and it is still running. It used to complete in an hour or so. CPU utiliz

Re: Increased disk space allocation when populating database with multiple connections

I think you are seeing the effect of two problems with derby space management (maybe one or both). I've logged DERBY-2337 and DERBY-2338 to start a discussion on these. I am just guessing what is going on.: 1) hot single point of contention, with limited attention to multi-cpu optimization.

[jira] Created: (DERBY-2338) improve page allocation when there are many threaded inserts to same table .

improve page allocation when there are many threaded inserts to same table . Key: DERBY-2338 URL: https://issues.apache.org/jira/browse/DERBY-2338 Project: Derby Is

[jira] Commented: (DERBY-2337) allow latches to be transferred directly from nested internal transactions to calling user transaction to improve page allocation performance/complexity

[ https://issues.apache.org/jira/browse/DERBY-2337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12473247 ] Mike Matrigali commented on DERBY-2337: --- Here's the comment from the applicable code in FileContainer.java:

[jira] Created: (DERBY-2337) allow latches to be transferred directly from nested internal transactions to calling user transaction to improve page allocation performance/complexity

allow latches to be transferred directly from nested internal transactions to calling user transaction to improve page allocation performance/complexity -

2 trivial doc warnings on trunk.

[javadoc] C:\nightlies\main\src\opensource\java\engine\org\apache\derby\impl\jdbc\LOBStreamControl.java:303: warning - @param argument "b" is not a parameter name. [javadoc] C:\nightlies\main\src\opensource\java\engine\org\apache\derby\impl\jdbc\LOBStreamControl.java:372: warning - @par

[jira] Updated: (DERBY-2249) Place holder to attach the long running test which will test Derby's improved optimizer

[ https://issues.apache.org/jira/browse/DERBY-2249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manjula Kutty updated DERBY-2249: - Attachment: build.xml DERBY-2249_diff.txt Army, thanks for the review. I would ap

[jira] Commented: (DERBY-681) Eliminate the parser's rewriting of the abstract syntax tree for queries with GROUP BY and/or HAVING clauses

[ https://issues.apache.org/jira/browse/DERBY-681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12473232 ] A B commented on DERBY-681: --- > I would argue that with Manish's patch committed DERBY-681 and DERBY-1624 > should be closed

Re: Derby Creme Help

Piotr Zaremba wrote: Dear Support, I am running a Creme JVM (ver 4.10 and 4.11) on a Windows CE 5.0 OS, everytime I run the app I get the following error can you please help me. NSIcom Ltd., CrEme(tm) Evaluation Version CrE-ME J2ME(tm) CrE-ME V4.11 B102.020706 02-Jul-2006 MemoryLimit=8535Kb

[jira] Commented: (DERBY-681) Eliminate the parser's rewriting of the abstract syntax tree for queries with GROUP BY and/or HAVING clauses

[ https://issues.apache.org/jira/browse/DERBY-681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12473226 ] Andrew McIntyre commented on DERBY-681: --- I checked Manish's patch and it does fix the original query reported no

org.apache.derbyTesting.functionTests.suites.All is extremely CPU intensive!

Do anyone else see this? I see this in all(?) test runs since the tinderbox test run on svn 507489. ( http://dbtg.thresher.com/derby/test/tinderbox_trunk16/jvm1.6/testing/Limited/testSummary-507489.html ) That specific test run I aborted after ~6 hours. (Test started ~11:29:52.655 GMT, killed

[jira] Commented: (DERBY-681) Eliminate the parser's rewriting of the abstract syntax tree for queries with GROUP BY and/or HAVING clauses

[ https://issues.apache.org/jira/browse/DERBY-681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12473218 ] Manish Khettry commented on DERBY-681: -- Just a quick note to address two issues raised by Army. DERBY-1624: It w

[jira] Commented: (DERBY-2249) Place holder to attach the long running test which will test Derby's improved optimizer

[ https://issues.apache.org/jira/browse/DERBY-2249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12473214 ] A B commented on DERBY-2249: I unzipped the zip file into my svn codeline and ran "ant all", but the new files did not b

[jira] Commented: (DERBY-2317) Difference in the cursor.getcursorName behaviour between n/w server and embedded mode, where embedded retuns null and n/w server returns the cursor name

[ https://issues.apache.org/jira/browse/DERBY-2317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12473210 ] Manjula Kutty commented on DERBY-2317: -- once this issue gets fixed, please make the CurrentOfTest.java runnable

Derby Creme Help

Dear Support, I am running a Creme JVM (ver 4.10 and 4.11) on a Windows CE 5.0 OS, everytime I run the app I get the following error can you please help me. NSIcom Ltd., CrEme(tm) Evaluation Version CrE-ME J2ME(tm) CrE-ME V4.11 B102.020706 02-Jul-2006 MemoryLimit=8535Kb EBCI(TM) Interpreter V

[jira] Updated: (DERBY-2315) compatibility/testScript.xml should include 10.2.2 in the server/client combinations

[ https://issues.apache.org/jira/browse/DERBY-2315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ole Solberg updated DERBY-2315: --- Attachment: derby-2315_v2_status.txt derby-2315_v2_diff.txt derby-2315_v2 combines de

Regression Test Report - tinderbox_trunk16 507489 - Sun DBTG

[Auto-generated mail] *tinderbox_trunk16* 507489/2007-02-14 12:22:22 CET Failed TestsOK Skip Duration Suite --- *Jvm: 1.6* SunOS-5.10_i86pc-i386 0456456 0 115.02% derbyall UNKNOWNUNKNOWNUNKNOWN

[jira] Created: (DERBY-2336) Enable collation based ordering for CHAR data type.

Enable collation based ordering for CHAR data type. --- Key: DERBY-2336 URL: https://issues.apache.org/jira/browse/DERBY-2336 Project: Derby Issue Type: Sub-task Components: SQL A

[jira] Created: (DERBY-2335) Compare character datatypes with different collation ordering.

Compare character datatypes with different collation ordering. -- Key: DERBY-2335 URL: https://issues.apache.org/jira/browse/DERBY-2335 Project: Derby Issue Type: Sub-task

[jira] Commented: (DERBY-681) Eliminate the parser's rewriting of the abstract syntax tree for queries with GROUP BY and/or HAVING clauses

[ https://issues.apache.org/jira/browse/DERBY-681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12473169 ] A B commented on DERBY-681: --- I spent some time manually trying out different test cases with the patch for this issue and t

[jira] Updated: (DERBY-2329) Compatibility test fails in all combinations with 'serverTrunk', i.e. current trunk revision. (since tinderbox on svn 506771)

[ https://issues.apache.org/jira/browse/DERBY-2329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ole Solberg updated DERBY-2329: --- Derby Info: [Patch Available] > Compatibility test fails in all combinations with 'serverTrunk', i.e.

[jira] Updated: (DERBY-2329) Compatibility test fails in all combinations with 'serverTrunk', i.e. current trunk revision. (since tinderbox on svn 506771)

[ https://issues.apache.org/jira/browse/DERBY-2329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ole Solberg updated DERBY-2329: --- Attachment: derby-2329_v1_status.txt derby-2329_v1_diff.txt Added extra parameter to

[jira] Updated: (DERBY-2334) Accept the new collation attribute and store it in services.properties file. Will be used for language based collation ordering.

[ https://issues.apache.org/jira/browse/DERBY-2334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mamta A. Satoor updated DERBY-2334: --- Attachment: DERBY2334_AcceptCollationAttribute_diff_V01.txt DERBY2334_AcceptCo

[jira] Created: (DERBY-2334) Accept the new collation attribute and store it in services.properties file. Will be used for language based collation ordering.

Accept the new collation attribute and store it in services.properties file. Will be used for language based collation ordering. Key: DERBY-2334

Re: [jira] Commented: (DERBY-2220) Uncommitted transactions executed throught XAResource will held locks after the application terminates (or crashes during the transaction).

Julius Stroffek commented on DERBY-2220: Dan: Thank you for explanation. It seems that I was reading a wrong book. ;-) No, just not enough books. :-) XA is a bit of a pain because once has to read the official distributed transaction spec from X/Open

Regression Test Report - Daily 507098 - Sun DBTG

[Auto-generated mail] *Daily* 507098/2007-02-13 18:00:26 CET Failed TestsOK Skip Duration Suite --- *Jvm: 1.6* lin 0479479 096.13% derbyall 067446744 0 216.40% suitesAll sles 1

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

Issue Subscription Filter: Derby: JIRA issues with patch available (14 issues) Subscriber: derby-dev Key Summary DERBY-1842 Accessibility of figures in Derby Docs https://issues.apache.org/jira/browse/DERBY-1842 DERBY-2315 compatibility/testScript.xml should include 10.2.2 i

[jira] Assigned: (DERBY-264) This enhancement to allow expressions in ORDER BY clause will require documentation changes.

[ https://issues.apache.org/jira/browse/DERBY-264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Laura Stewart reassigned DERBY-264: --- Assignee: Laura Stewart > This enhancement to allow expressions in ORDER BY clause will requir

[jira] Commented: (DERBY-2220) Uncommitted transactions executed throught XAResource will held locks after the application terminates (or crashes during the transaction).

[ https://issues.apache.org/jira/browse/DERBY-2220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12473075 ] Julius Stroffek commented on DERBY-2220: Dan: Thank you for explanation. It seems that I was reading a wrong

[jira] Updated: (DERBY-2328) Reduce monitor contention in SinglePool

[ https://issues.apache.org/jira/browse/DERBY-2328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Knut Anders Hatlen updated DERBY-2328: -- Attachment: unused.diff LanguageConnectionContext has a method called getLockSpace(int)

[jira] Commented: (DERBY-2328) Reduce monitor contention in SinglePool

[ https://issues.apache.org/jira/browse/DERBY-2328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12473059 ] Knut Anders Hatlen commented on DERBY-2328: --- getLockSpace(int) in the previous comment should have been get

[jira] Updated: (DERBY-2108) Implement SSL/TLS communication between client and server

[ https://issues.apache.org/jira/browse/DERBY-2108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bernt M. Johnsen updated DERBY-2108: Derby Info: [Release Note Needed] (was: [Release Note Needed, Patch Available]) > Impleme

[jira] Resolved: (DERBY-2108) Implement SSL/TLS communication between client and server

[ https://issues.apache.org/jira/browse/DERBY-2108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bernt M. Johnsen resolved DERBY-2108. - Resolution: Fixed Derby Info: [Patch Available, Release Note Needed] (was: [Patch Ava