[jira] Resolved: (DERBY-244) with linux, depending on env setting $LANG and console encoding, some i18n tests fail

[ http://issues.apache.org/jira/browse/DERBY-244?page=all ] Knut Anders Hatlen resolved DERBY-244. -- Fix Version/s: 10.2.1.0 Resolution: Fixed Derby Info: (was: [Patch Available]) Committed revision 432645. The problems with

[jira] Resolved: (DERBY-1717) Working With Derby task file twwdactivity4.dita is invalid, results in missing text

[ http://issues.apache.org/jira/browse/DERBY-1717?page=all ] Knut Anders Hatlen resolved DERBY-1717. --- Resolution: Fixed Derby Info: (was: [Patch Available]) Thanks Kim, this looks like an improvement to me. I added yet another client /

[jira] Assigned: (DERBY-1500) PreparedStatement#setObject(int parameterIndex, Object x) throws SQL Exception when binding Short value in embedded mode

[ http://issues.apache.org/jira/browse/DERBY-1500?page=all ] Knut Anders Hatlen reassigned DERBY-1500: - Assignee: Knut Anders Hatlen PreparedStatement#setObject(int parameterIndex, Object x) throws SQL Exception when binding Short value in

[jira] Commented: (DERBY-1500) PreparedStatement#setObject(int parameterIndex, Object x) throws SQL Exception when binding Short value in embedded mode

[ http://issues.apache.org/jira/browse/DERBY-1500?page=comments#action_12429195 ] Knut Anders Hatlen commented on DERBY-1500: --- Derby Network Client and JCC already work correctly. I will fix the embedded driver.

[jira] Created: (DERBY-1730) Manifest file doesn't contain OSGi attributes

Manifest file doesn't contain OSGi attributes - Key: DERBY-1730 URL: http://issues.apache.org/jira/browse/DERBY-1730 Project: Derby Issue Type: Bug Components: Build tools Affects

[jira] Updated: (DERBY-1500) PreparedStatement#setObject(int parameterIndex, Object x) throws SQL Exception when binding Short value in embedded mode

[ http://issues.apache.org/jira/browse/DERBY-1500?page=all ] Knut Anders Hatlen updated DERBY-1500: -- Attachment: derby-1500.diff derby-1500.stat Attached is a fix for the issue. I haven't seen the updated JDBC 4.0 spec myself, but

[jira] Updated: (DERBY-1500) PreparedStatement#setObject(int parameterIndex, Object x) throws SQL Exception when binding Short value in embedded mode

[ http://issues.apache.org/jira/browse/DERBY-1500?page=all ] Knut Anders Hatlen updated DERBY-1500: -- Derby Info: [Patch Available] PreparedStatement#setObject(int parameterIndex, Object x) throws SQL Exception when binding Short value in

[jira] Commented: (DERBY-1610) Updating column typed as CHAR to value passed via setBinaryStream(notNull) is failed because of imcompatiblity of types though it was not taken as error when setBinarySt

[ http://issues.apache.org/jira/browse/DERBY-1610?page=comments#action_12429256 ] Knut Anders Hatlen commented on DERBY-1610: --- Hi Tomohito, The BatchUpdateException indicates that the error happens when executeBatch() is invoked, not

[jira] Updated: (DERBY-1610) Updating column typed as CHAR to value passed via setBinaryStream(notNull) is failed because of imcompatiblity of types though it was not taken as error when setBinaryStre

[ http://issues.apache.org/jira/browse/DERBY-1610?page=all ] Knut Anders Hatlen updated DERBY-1610: -- Derby Info: [Release Note Needed] Adding the Release Note Needed flag to keep it on the release manager's radar. Updating column typed as CHAR to

[jira] Commented: (DERBY-1610) Updating column typed as CHAR to value passed via setBinaryStream(notNull) is failed because of imcompatiblity of types though it was not taken as error when setBinarySt

[ http://issues.apache.org/jira/browse/DERBY-1610?page=comments#action_12429278 ] Knut Anders Hatlen commented on DERBY-1610: --- With the DERBY-1610_2.diff patch, setBinaryStream(null), setBlob(null) and setNull(Types.BLOB) throw

[jira] Commented: (DERBY-1610) Updating column typed as CHAR to value passed via setBinaryStream(notNull) is failed because of imcompatiblity of types though it was not taken as error when setBinarySt

[ http://issues.apache.org/jira/browse/DERBY-1610?page=comments#action_12429368 ] Knut Anders Hatlen commented on DERBY-1610: --- There will be user impact even if only a few of the incompatible combinations are changed to throw

[jira] Commented: (DERBY-1610) Updating column typed as CHAR to value passed via setBinaryStream(notNull) is failed because of imcompatiblity of types though it was not taken as error when setBinarySt

[ http://issues.apache.org/jira/browse/DERBY-1610?page=comments#action_12429424 ] Knut Anders Hatlen commented on DERBY-1610: --- Yes, I think you can decide the correct type on the client side. ParameterMetaData (which can be obtained

[jira] Created: (DERBY-1743) derbynet/testSecMec.java fails with NullPointerException (intermittent failure)

derbynet/testSecMec.java fails with NullPointerException (intermittent failure) --- Key: DERBY-1743 URL: http://issues.apache.org/jira/browse/DERBY-1743 Project: Derby

[jira] Created: (DERBY-1744) ResultSet.rowInserted(), rowUpdated() and rowDeleted() don't throw exception on read-only result sets

ResultSet.rowInserted(), rowUpdated() and rowDeleted() don't throw exception on read-only result sets - Key: DERBY-1744 URL:

[jira] Commented: (DERBY-418) outofmemory error when running large query in autocommit=false mode

[ http://issues.apache.org/jira/browse/DERBY-418?page=comments#action_12429674 ] Knut Anders Hatlen commented on DERBY-418: -- Hi Mayuresh, I'm afraid your fix has some unwanted consequences. First of all, the OutOfMemoryError is still

[jira] Updated: (DERBY-1730) Manifest file doesn't contain OSGi attributes

[ http://issues.apache.org/jira/browse/DERBY-1730?page=all ] Knut Anders Hatlen updated DERBY-1730: -- Description: With osgi.jar in tools/java, 'ant buildjars' does not add the OSGi attributes to derby.jar's manifest. Instead, a file named

[jira] Closed: (DERBY-1730) Manifest file doesn't contain OSGi attributes

[ http://issues.apache.org/jira/browse/DERBY-1730?page=all ] Knut Anders Hatlen closed DERBY-1730. - Resolution: Fixed Patch has been merged into the 10.2 branch. Thanks Andrew! Closing the issue. Manifest file doesn't contain OSGi attributes

[jira] Resolved: (DERBY-23) just booting jdbc driver and shutting down seem to leak memory

[ http://issues.apache.org/jira/browse/DERBY-23?page=all ] Knut Anders Hatlen resolved DERBY-23. - Resolution: Fixed I'm marking this issue as resolved. The reason why I haven't resolved it before, is that I still see OutOfMemoryError on some

[jira] Commented: (DERBY-418) outofmemory error when running large query in autocommit=false mode

[ http://issues.apache.org/jira/browse/DERBY-418?page=comments#action_12429712 ] Knut Anders Hatlen commented on DERBY-418: -- Did you try to declare BaseActivation.inUse as volatile? outofmemory error when running large query in

[jira] Commented: (DERBY-418) outofmemory error when running large query in autocommit=false mode

[ http://issues.apache.org/jira/browse/DERBY-418?page=comments#action_12429725 ] Knut Anders Hatlen commented on DERBY-418: -- Mayuresh, with your latest changes, I don't see the memory leak any more (neither DERBY-418 nor DERBY-1142).

[jira] Updated: (DERBY-1743) derbynet/testSecMec.java fails with NullPointerException (intermittent failure)

[ http://issues.apache.org/jira/browse/DERBY-1743?page=all ] Knut Anders Hatlen updated DERBY-1743: -- Attachment: 1743.diff Thanks Bryan, I agree that has to be it. I noticed that NetworkServerControlImpl already has a method which does the null

[jira] Closed: (DERBY-1743) derbynet/testSecMec.java fails with NullPointerException (intermittent failure)

[ http://issues.apache.org/jira/browse/DERBY-1743?page=all ] Knut Anders Hatlen closed DERBY-1743. - Fix Version/s: 10.3.0.0 Resolution: Fixed Assignee: Knut Anders Hatlen Committed into trunk with revision 434018. I'm closing the

[jira] Commented: (DERBY-1417) Add new, lengthless overloads to the streaming api

[ http://issues.apache.org/jira/browse/DERBY-1417?page=comments#action_12430163 ] Knut Anders Hatlen commented on DERBY-1417: --- Hi Kristian, I tried to run derbyall with the 8a patch and the patch for DERBY-1473. I see this error: ***

[jira] Reopened: (DERBY-1743) derbynet/testSecMec.java fails with NullPointerException (intermittent failure)

[ http://issues.apache.org/jira/browse/DERBY-1743?page=all ] Knut Anders Hatlen reopened DERBY-1743: --- derbynet/testSecMec.java fails with NullPointerException (intermittent failure)

[jira] Closed: (DERBY-1743) derbynet/testSecMec.java fails with NullPointerException (intermittent failure)

[ http://issues.apache.org/jira/browse/DERBY-1743?page=all ] Knut Anders Hatlen closed DERBY-1743. - Fix Version/s: 10.2.1.0 Resolution: Fixed Merged into 10.2 (revision 434308). derbynet/testSecMec.java fails with NullPointerException

[jira] Resolved: (DERBY-1500) PreparedStatement#setObject(int parameterIndex, Object x) throws SQL Exception when binding Short value in embedded mode

[ http://issues.apache.org/jira/browse/DERBY-1500?page=all ] Knut Anders Hatlen resolved DERBY-1500. --- Resolution: Fixed Derby Info: (was: [Patch Available]) Committed into trunk with revision 434309. Committed into 10.2 with revision 434311.

[jira] Commented: (DERBY-1473) Add cut-off and truncation logic to streaming classes in the embedded driver

[ http://issues.apache.org/jira/browse/DERBY-1473?page=comments#action_12430207 ] Knut Anders Hatlen commented on DERBY-1473: --- Thanks Kristian. I tried to commit the patch, but there are conflicts with the ongoing JUnit reorganization

[jira] Assigned: (DERBY-1744) ResultSet.rowInserted(), rowUpdated() and rowDeleted() don't throw exception on read-only result sets

[ http://issues.apache.org/jira/browse/DERBY-1744?page=all ] Knut Anders Hatlen reassigned DERBY-1744: - Assignee: Knut Anders Hatlen ResultSet.rowInserted(), rowUpdated() and rowDeleted() don't throw exception on read-only result sets

[jira] Commented: (DERBY-418) outofmemory error when running large query in autocommit=false mode

[ http://issues.apache.org/jira/browse/DERBY-418?page=comments#action_12430517 ] Knut Anders Hatlen commented on DERBY-418: -- Thank you for addressing my comments, Mayuresh! I think you misunderstood what I meant with the indentation

[jira] Created: (DERBY-1764) Rewrite stress.multi as a JUnit test

Rewrite stress.multi as a JUnit test Key: DERBY-1764 URL: http://issues.apache.org/jira/browse/DERBY-1764 Project: Derby Issue Type: Test Components: Test Reporter: Knut Anders

[jira] Updated: (DERBY-1473) Add cut-off and truncation logic to streaming classes in the embedded driver

[ http://issues.apache.org/jira/browse/DERBY-1473?page=all ] Knut Anders Hatlen updated DERBY-1473: -- Derby Info: (was: [Patch Available]) I have committed 1c and 2c into trunk with revision 437127. The changes merged cleanly into 10.2, and I

[jira] Resolved: (DERBY-1473) Add cut-off and truncation logic to streaming classes in the embedded driver

[ http://issues.apache.org/jira/browse/DERBY-1473?page=all ] Knut Anders Hatlen resolved DERBY-1473. --- Resolution: Fixed Committed into 10.2 with revision 437146. Add cut-off and truncation logic to streaming classes in the embedded driver

[jira] Resolved: (DERBY-705) Re-enable test which was disabled in DERBY-506 commit

[ http://issues.apache.org/jira/browse/DERBY-705?page=all ] Knut Anders Hatlen resolved DERBY-705. -- Fix Version/s: 10.2.1.0 Resolution: Fixed Thanks, Narayanan! Committed into trunk with revision 437168. Committed into 10.2 with revision

[jira] Resolved: (DERBY-694) Statement exceptions cause all the connection's result sets to be closed with the client driver

[ http://issues.apache.org/jira/browse/DERBY-694?page=all ] Knut Anders Hatlen resolved DERBY-694. -- Fix Version/s: 10.2.1.0 Resolution: Fixed Marking the issue as fixed since Narayanan's patch has been committed. Statement exceptions cause

[jira] Created: (DERBY-1767) insertRow(), updateRow() and deleteRow() cannot handle table names and column names containing double quotes

insertRow(), updateRow() and deleteRow() cannot handle table names and column names containing double quotes Key: DERBY-1767 URL:

[jira] Created: (DERBY-1768) Remove JDBC 4.0 RowId classes

Remove JDBC 4.0 RowId classes - Key: DERBY-1768 URL: http://issues.apache.org/jira/browse/DERBY-1768 Project: Derby Issue Type: Improvement Affects Versions: 10.2.1.0 Reporter: Knut Anders Hatlen

[jira] Updated: (DERBY-1768) Remove JDBC 4.0 RowId classes

[ http://issues.apache.org/jira/browse/DERBY-1768?page=all ] Knut Anders Hatlen updated DERBY-1768: -- Attachment: rowid.diff rowid.stat Attached a patch which removes org.apache.derby.impl.jdbc.EmbedRowId and

[jira] Updated: (DERBY-1768) Remove JDBC 4.0 RowId classes

[ http://issues.apache.org/jira/browse/DERBY-1768?page=all ] Knut Anders Hatlen updated DERBY-1768: -- Assignee: Knut Anders Hatlen Derby Info: [Patch Available] Remove JDBC 4.0 RowId classes -

[jira] Commented: (DERBY-1767) insertRow(), updateRow() and deleteRow() cannot handle table names and column names containing double quotes

[ http://issues.apache.org/jira/browse/DERBY-1767?page=comments#action_12430972 ] Knut Anders Hatlen commented on DERBY-1767: --- Also, when this error is observed, subsequent calls to Connection.rollback() will fail with:

[jira] Closed: (DERBY-1744) ResultSet.rowInserted(), rowUpdated() and rowDeleted() don't throw exception on read-only result sets

[ http://issues.apache.org/jira/browse/DERBY-1744?page=all ] Knut Anders Hatlen closed DERBY-1744. - Resolution: Invalid Thanks to Dag and Lance for clearing this up. Closing the issue as invalid. ResultSet.rowInserted(), rowUpdated() and

[jira] Commented: (DERBY-1768) Remove JDBC 4.0 RowId classes

[ http://issues.apache.org/jira/browse/DERBY-1768?page=comments#action_12431023 ] Knut Anders Hatlen commented on DERBY-1768: --- EmbedRowId is in derby.jar because RowIdNotImplementedTest and Driver40 have a direct reference to it. The

[jira] Commented: (DERBY-1417) Add new, lengthless overloads to the streaming api

[ http://issues.apache.org/jira/browse/DERBY-1417?page=comments#action_12431146 ] Knut Anders Hatlen commented on DERBY-1417: --- Thanks Kristian, your latest patch addresses all my concerns. I have verified that inserting a 100MB blob

[jira] Commented: (DERBY-418) outofmemory error when running large query in autocommit=false mode

[ http://issues.apache.org/jira/browse/DERBY-418?page=comments#action_12431148 ] Knut Anders Hatlen commented on DERBY-418: -- Thanks Mayuresh. I think the patch looks good. If there are no more comments, I will run some tests and commit

[jira] Commented: (DERBY-1292) ClassCastException in ClientDriver when using CLOB columns and batch updates

[ http://issues.apache.org/jira/browse/DERBY-1292?page=comments#action_12431150 ] Knut Anders Hatlen commented on DERBY-1292: --- I am running tests on 10.2 and will merge the fix into the 10.2 branch when they have completed

[jira] Commented: (DERBY-1767) insertRow(), updateRow() and deleteRow() cannot handle table names and column names containing double quotes

[ http://issues.apache.org/jira/browse/DERBY-1767?page=comments#action_12431153 ] Knut Anders Hatlen commented on DERBY-1767: --- I believe updateRow() and deleteRow() have the same problem with cursor names that contain double quotes.

[jira] Created: (DERBY-1773) insertRow() and updateRow() fail with syntax error when column has an alias

insertRow() and updateRow() fail with syntax error when column has an alias --- Key: DERBY-1773 URL: http://issues.apache.org/jira/browse/DERBY-1773 Project: Derby

[jira] Commented: (DERBY-418) outofmemory error when running large query in autocommit=false mode

[ http://issues.apache.org/jira/browse/DERBY-418?page=comments#action_12431510 ] Knut Anders Hatlen commented on DERBY-418: -- Derbyall ran cleanly. However, when running the repro for DERBY-1142 (without rs.close()), I noticed that

[jira] Resolved: (DERBY-418) outofmemory error when running large query in autocommit=false mode

[ http://issues.apache.org/jira/browse/DERBY-418?page=all ] Knut Anders Hatlen resolved DERBY-418. -- Resolution: Fixed Thank you, Mayuresh! Committed v6 into trunk (rev 439279) and 10.2 (rev 439281). outofmemory error when running large query in

[jira] Closed: (DERBY-1142) Metadata calls leak memory

[ http://issues.apache.org/jira/browse/DERBY-1142?page=all ] Knut Anders Hatlen closed DERBY-1142. - Fix Version/s: 10.2.1.0 Resolution: Fixed Verified that the fix for DERBY-418 also fixes the remaining problems for this issue. Metadata

[jira] Created: (DERBY-594) Some rawStoreDaemon threads are not stopped

Some rawStoreDaemon threads are not stopped --- Key: DERBY-594 URL: http://issues.apache.org/jira/browse/DERBY-594 Project: Derby Type: Bug Components: Services Versions: 10.1.2.0, 10.2.0.0 Environment: Solaris 10

[jira] Commented: (DERBY-557) Client driver gets OutOfMemoryError when re-executing statement without closing ResultSet

[ http://issues.apache.org/jira/browse/DERBY-557?page=comments#action_12331467 ] Knut Anders Hatlen commented on DERBY-557: -- Kathey, I think you should just go ahead and port the fix to 10.1. Merge command: svn merge -r 289538:289539

[jira] Reopened: (DERBY-23) just booting jdbc driver and shutting down seem to leak memory

[ http://issues.apache.org/jira/browse/DERBY-23?page=all ] Knut Anders Hatlen reopened DERBY-23: - As I have mentioned on derby-dev earlier, there is a problem with the current fix. After the fix was committed, store/encryptDatabase.sql sometimes

[jira] Closed: (DERBY-557) Client driver gets OutOfMemoryError when re-executing statement without closing ResultSet

[ http://issues.apache.org/jira/browse/DERBY-557?page=all ] Knut Anders Hatlen closed DERBY-557: Fix Version: 10.1.1.2 Resolution: Fixed Fixed in trunk (revision 289539) and 10.1 (revision 306950). Client driver gets OutOfMemoryError

[jira] Closed: (DERBY-504) SELECT DISTINCT returns duplicates when selecting from subselects

[ http://issues.apache.org/jira/browse/DERBY-504?page=all ] Knut Anders Hatlen closed DERBY-504: Fix Version: 10.1.1.2 Resolution: Fixed Fixed in trunk (revision 267239) and 10.1 (revision 306964). SELECT DISTINCT returns duplicates when

[jira] Created: (DERBY-642) SELECT MAX doesn't use indices optimally

SELECT MAX doesn't use indices optimally Key: DERBY-642 URL: http://issues.apache.org/jira/browse/DERBY-642 Project: Derby Type: Improvement Components: Store, Performance Versions: 10.2.0.0 Reporter: Knut

[jira] Created: (DERBY-667) Derbyall should test the framework scripts

Derbyall should test the framework scripts -- Key: DERBY-667 URL: http://issues.apache.org/jira/browse/DERBY-667 Project: Derby Type: Test Components: Test, Demos/Scripts Versions: 10.1.3.0, 10.2.0.0 Reporter:

[jira] Closed: (DERBY-110) hsqldb is faster than derby doing inserts

[ http://issues.apache.org/jira/browse/DERBY-110?page=all ] Knut Anders Hatlen closed DERBY-110: Resolution: Won't Fix Closing this issue since no one objected to Olav's proposal. hsqldb is faster than derby doing inserts

[jira] Created: (DERBY-677) ksh scripts should be written in a more portable way

ksh scripts should be written in a more portable way Key: DERBY-677 URL: http://issues.apache.org/jira/browse/DERBY-677 Project: Derby Type: Bug Components: Demos/Scripts Versions: 10.2.0.0, 10.1.2.1

[jira] Updated: (DERBY-677) ksh scripts should be written in a more portable way

[ http://issues.apache.org/jira/browse/DERBY-677?page=all ] Knut Anders Hatlen updated DERBY-677: - Attachment: DERBY-677.diff Attached a patch which fixes the scripts. % svn stat M frameworks/NetworkServer/bin/ij.ksh M

[jira] Created: (DERBY-704) Large page cache kills initial performance

Large page cache kills initial performance -- Key: DERBY-704 URL: http://issues.apache.org/jira/browse/DERBY-704 Project: Derby Type: Bug Components: Services, Performance Versions: 10.1.2.2, 10.1.3.0, 10.2.0.0,

[jira] Updated: (DERBY-704) Large page cache kills initial performance

[ http://issues.apache.org/jira/browse/DERBY-704?page=all ] Knut Anders Hatlen updated DERBY-704: - Attachment: DERBY-704.diff derbyall_report.txt Attached patch and report from running derbyall (no tests failed). The patch modifies

[jira] Updated: (DERBY-704) Large page cache kills initial performance

[ http://issues.apache.org/jira/browse/DERBY-704?page=all ] Knut Anders Hatlen updated DERBY-704: - Attachment: throughput.png cpu-usage.png Attached graphs showing the throughput and CPU usage running with and without the patch. The

[jira] Commented: (DERBY-704) Large page cache kills initial performance

[ http://issues.apache.org/jira/browse/DERBY-704?page=comments#action_12357574 ] Knut Anders Hatlen commented on DERBY-704: -- Sorry, I forgot the output from svn stat. M java/engine/org/apache/derby/impl/services/cache/Clock.java Large page

[jira] Reopened: (DERBY-704) Large page cache kills initial performance

[ http://issues.apache.org/jira/browse/DERBY-704?page=all ] Knut Anders Hatlen reopened DERBY-704: -- Issue is reopened in order to add more comments to the code. Large page cache kills initial performance

[jira] Updated: (DERBY-704) Large page cache kills initial performance

[ http://issues.apache.org/jira/browse/DERBY-704?page=all ] Knut Anders Hatlen updated DERBY-704: - Attachment: DERBY-704-extra-comments.diff Patch DERBY-704-extra-comments.diff adds the following comments to the code: // 1) find out how many

[jira] Closed: (DERBY-704) Large page cache kills initial performance

[ http://issues.apache.org/jira/browse/DERBY-704?page=all ] Knut Anders Hatlen closed DERBY-704: Fixed in revision 344270. Extra comments put into the code in revision 345215. Large page cache kills initial performance

[jira] Created: (DERBY-733) Starvation in RAFContainer.readPage()

Starvation in RAFContainer.readPage() - Key: DERBY-733 URL: http://issues.apache.org/jira/browse/DERBY-733 Project: Derby Type: Bug Components: Performance, Store Versions: 10.2.0.0, 10.1.2.1, 10.1.3.0, 10.1.2.2

[jira] Commented: (DERBY-733) Starvation in RAFContainer.readPage()

[ http://issues.apache.org/jira/browse/DERBY-733?page=comments#action_12358925 ] Knut Anders Hatlen commented on DERBY-733: -- I have tried to put calls to the lock() and unlock() methods in the Java 1.5 ReentrantLock class around the synchronized

[jira] Updated: (DERBY-733) Starvation in RAFContainer.readPage()

[ http://issues.apache.org/jira/browse/DERBY-733?page=all ] Knut Anders Hatlen updated DERBY-733: - Attachment: DERBY-733.diff Mike, I agree that a pool of open file descriptors is a good idea, but you will run into the same problem with highly

[jira] Updated: (DERBY-733) Starvation in RAFContainer.readPage()

[ http://issues.apache.org/jira/browse/DERBY-733?page=all ] Knut Anders Hatlen updated DERBY-733: - Attachment: Insert.java Select.java I have attached a test case that makes it possible to reproduce the reported issue. There are two

[jira] Updated: (DERBY-733) Starvation in RAFContainer.readPage()

[ http://issues.apache.org/jira/browse/DERBY-733?page=all ] Knut Anders Hatlen updated DERBY-733: - Attachment: DERBY-733-more-exception-handling.diff Attached patch (DERBY-733-more-exception-handling.diff) that addresses Mike's concerns for

[jira] Closed: (DERBY-733) Starvation in RAFContainer.readPage()

[ http://issues.apache.org/jira/browse/DERBY-733?page=all ] Knut Anders Hatlen closed DERBY-733: Fix Version: 10.2.0.0 Resolution: Fixed Fixed in revision 357275. Thanks for taking the time to review and commit, Mike. Starvation in

[jira] Commented: (DERBY-333) Malformed if statement in org.apache.derby.impl.drda.Database.getDRDAStatement()

[ http://issues.apache.org/jira/browse/DERBY-333?page=comments#action_12361027 ] Knut Anders Hatlen commented on DERBY-333: -- Bryan's proposed rewrite of getDRDAStatement() is a lot clearer than the original code, and as far as I can tell, it does

[jira] Updated: (DERBY-212) Optimize some specific methods in Network Server to improve performance

[ http://issues.apache.org/jira/browse/DERBY-212?page=all ] Knut Anders Hatlen updated DERBY-212: - Attachment: (was: DERBY-212-parsePKGNAMCSN.diff) Optimize some specific methods in Network Server to improve performance

[jira] Updated: (DERBY-212) Optimize some specific methods in Network Server to improve performance

[ http://issues.apache.org/jira/browse/DERBY-212?page=all ] Knut Anders Hatlen updated DERBY-212: - Attachment: DERBY-212-parsePKGNAMCSN-2.diff I have uploaded a new patch (DERBY-212-parsePKGNAMCSN-2.diff) where I have tried to address Bryan's review

[jira] Reopened: (DERBY-212) Optimize some specific methods in Network Server to improve performance

[ http://issues.apache.org/jira/browse/DERBY-212?page=all ] Knut Anders Hatlen reopened DERBY-212: -- Assign To: Dyre Tjeldvoll (was: Knut Anders Hatlen) Reopening the issue since my patch didn't address everything mentioned in the

[jira] Created: (DERBY-814) Prevent unneeded object creation and excessive decoding in parsePKGNAMCSN()

Prevent unneeded object creation and excessive decoding in parsePKGNAMCSN() --- Key: DERBY-814 URL: http://issues.apache.org/jira/browse/DERBY-814 Project: Derby Type: Sub-task Components:

[jira] Created: (DERBY-815) Prevent unneeded object creation and excessive decoding in parseSQLDTA_work()

Prevent unneeded object creation and excessive decoding in parseSQLDTA_work() -- Key: DERBY-815 URL: http://issues.apache.org/jira/browse/DERBY-815 Project: Derby Type: Sub-task

[jira] Updated: (DERBY-815) Prevent unneeded object creation and excessive decoding in parseSQLDTA_work()

[ http://issues.apache.org/jira/browse/DERBY-815?page=all ] Knut Anders Hatlen updated DERBY-815: - Component: Network Server Performance Fix Version: 10.2.0.0 Description: Reported by Kathey Marsden in DERBY-212: In

[jira] Created: (DERBY-816) In DDMWriter and DDMReader, use system routines in java.util.Arrays and System.arrayCopy

In DDMWriter and DDMReader, use system routines in java.util.Arrays and System.arrayCopy Key: DERBY-816 URL: http://issues.apache.org/jira/browse/DERBY-816 Project: Derby Type:

[jira] Closed: (DERBY-814) Prevent unneeded object creation and excessive decoding in parsePKGNAMCSN()

[ http://issues.apache.org/jira/browse/DERBY-814?page=all ] Knut Anders Hatlen closed DERBY-814: Resolution: Fixed Fixed in revision 368333. Prevent unneeded object creation and excessive decoding in parsePKGNAMCSN()

[jira] Updated: (DERBY-816) In DDMWriter and DDMReader, use system routines in java.util.Arrays and System.arrayCopy

[ http://issues.apache.org/jira/browse/DERBY-816?page=all ] Knut Anders Hatlen updated DERBY-816: - Component: Network Server Newcomer Performance Priority: Trivial (was: Minor) It seems like System.arraycopy is

[jira] Created: (DERBY-821) Client driver: Implicitly close exhausted result sets on the server

Client driver: Implicitly close exhausted result sets on the server - Key: DERBY-821 URL: http://issues.apache.org/jira/browse/DERBY-821 Project: Derby Type: Improvement Components: Network

[jira] Created: (DERBY-822) Client driver: Pre-fetch data on executeQuery()

Client driver: Pre-fetch data on executeQuery() --- Key: DERBY-822 URL: http://issues.apache.org/jira/browse/DERBY-822 Project: Derby Type: Improvement Components: Network Client, Network Server, Performance

[jira] Commented: (DERBY-821) Client driver: Implicitly close exhausted result sets on the server

[ http://issues.apache.org/jira/browse/DERBY-821?page=comments#action_12363677 ] Knut Anders Hatlen commented on DERBY-821: -- In the network server code, DRDAResultSet.isRSCloseImplicit() has this comment: * Method to decide weather the ResultSet

[jira] Commented: (DERBY-821) Client driver: Implicitly close exhausted result sets on the server

[ http://issues.apache.org/jira/browse/DERBY-821?page=comments#action_12363714 ] Knut Anders Hatlen commented on DERBY-821: -- I have a partly working implementation which sends qryclsimp to the server and implicitly closes exhausted forward-only

[jira] Commented: (DERBY-821) Client driver: Implicitly close exhausted result sets on the server

[ http://issues.apache.org/jira/browse/DERBY-821?page=comments#action_12363723 ] Knut Anders Hatlen commented on DERBY-821: -- Thanks for your comments, Bryan. Because of the prefetching (default fetch size is 64) next is called four times on the

[jira] Commented: (DERBY-821) Client driver: Implicitly close exhausted result sets on the server

[ http://issues.apache.org/jira/browse/DERBY-821?page=comments#action_12363814 ] Knut Anders Hatlen commented on DERBY-821: -- Answer to my own question about why QRYCLSIMP is disabled when LMTBLKPRC is used: The DB2 driver seems to send QRYCLSIMP=1

[jira] Commented: (DERBY-816) In DDMWriter and DDMReader, use system routines in java.util.Arrays and System.arrayCopy

[ http://issues.apache.org/jira/browse/DERBY-816?page=comments#action_12363818 ] Knut Anders Hatlen commented on DERBY-816: -- I agree with Dyre and Bryan that there's little value in these changes. I guess DDMReader and DDMWriter have been cleaned

[jira] Commented: (DERBY-864) Network Client should not assume length of Layer B segment is 32K

[ http://issues.apache.org/jira/browse/DERBY-864?page=comments#action_12363878 ] Knut Anders Hatlen commented on DERBY-864: -- David's question: Do we have version detection at that level of granularity in the protocol? The client driver has a

[jira] Commented: (DERBY-213) ResultSet.next() after last row of FORWARD_ONLY cursor throws an SQL Exception with Network Server

[ http://issues.apache.org/jira/browse/DERBY-213?page=comments#action_12363960 ] Knut Anders Hatlen commented on DERBY-213: -- The comments (and resolution=fixed) indicate that we should close this issue. Any objections? ResultSet.next() after

[jira] Updated: (DERBY-821) Client driver: Implicitly close exhausted result sets on the server

[ http://issues.apache.org/jira/browse/DERBY-821?page=all ] Knut Anders Hatlen updated DERBY-821: - Attachment: DERBY-821.diff DERBY-821.stat changes.html I have attached a patch (DERBY-821.diff) which lets the client

[jira] Commented: (DERBY-821) Client driver: Implicitly close exhausted result sets on the server

[ http://issues.apache.org/jira/browse/DERBY-821?page=comments#action_12364799 ] Knut Anders Hatlen commented on DERBY-821: -- Thanks for commenting on this issue, Philip. From my reading of DERBY-213 and DERBY-545, it seems like the term implicit

[jira] Commented: (DERBY-922) getSQLException() method in client.am.SqlException does not correctly chain exceptions

[ http://issues.apache.org/jira/browse/DERBY-922?page=comments#action_12365124 ] Knut Anders Hatlen commented on DERBY-922: -- There is a similar problem in SqlWarning.getSQLWarning(). getSQLException() method in client.am.SqlException does not

[jira] Closed: (DERBY-333) Malformed if statement in org.apache.derby.impl.drda.Database.getDRDAStatement()

[ http://issues.apache.org/jira/browse/DERBY-333?page=all ] Knut Anders Hatlen closed DERBY-333: Fix Version: 10.2.0.0 Resolution: Fixed Assign To: Knut Anders Hatlen Fixed in revision 368333. Malformed if statement in

[jira] Updated: (DERBY-821) Client driver: Implicitly close exhausted result sets on the server

[ http://issues.apache.org/jira/browse/DERBY-821?page=all ] Knut Anders Hatlen updated DERBY-821: - Attachment: (was: changes.html) Client driver: Implicitly close exhausted result sets on the server

[jira] Updated: (DERBY-821) Client driver: Implicitly close exhausted result sets on the server

[ http://issues.apache.org/jira/browse/DERBY-821?page=all ] Knut Anders Hatlen updated DERBY-821: - Attachment: (was: changes-no-object-tags.html) Client driver: Implicitly close exhausted result sets on the server

[jira] Updated: (DERBY-821) Client driver: Implicitly close exhausted result sets on the server

[ http://issues.apache.org/jira/browse/DERBY-821?page=all ] Knut Anders Hatlen updated DERBY-821: - Attachment: DERBY-821-v2.diff DERBY-821-v2.stat changes.html New patch (DERBY-821-v2.diff) which addresses issues

[jira] Commented: (DERBY-822) Client driver: Pre-fetch data on executeQuery()

[ http://issues.apache.org/jira/browse/DERBY-822?page=comments#action_12365915 ] Knut Anders Hatlen commented on DERBY-822: -- Brief status update... This seems easier than I first thought. In theory, at least... When the server receives an OPNQRY

[jira] Reopened: (DERBY-557) Client driver gets OutOfMemoryError when re-executing statement without closing ResultSet

[ http://issues.apache.org/jira/browse/DERBY-557?page=all ] Knut Anders Hatlen reopened DERBY-557: -- Reopening to add regression test. Client driver gets OutOfMemoryError when re-executing statement without closing ResultSet

<    1   2   3   4   5   6   7   8   9   10   >