[jira] Updated: (DERBY-1696) transaction may sometimes keep lock on a row after moving off the resultset in scrollable updatable resultset

[ http://issues.apache.org/jira/browse/DERBY-1696?page=all ] Andreas Korneliussen updated DERBY-1696: Assignee: (was: Andreas Korneliussen) > transaction may sometimes keep lock on a row after moving off the resultset > in scrollable updatab

[jira] Updated: (DERBY-1862) Simple hash improves performance

[ http://issues.apache.org/jira/browse/DERBY-1862?page=all ] Andreas Korneliussen updated DERBY-1862: Attachment: DERBY-1862v3.diff Attaching a modified patch where I have taken in the advice of not creating the map object in the constructor, an

[jira] Commented: (DERBY-1846) Create a script that allows users to easily update their Derby jars with the JDBC4 classes.

[ http://issues.apache.org/jira/browse/DERBY-1846?page=comments#action_12436798 ] Andreas Korneliussen commented on DERBY-1846: - I have successfully used this script now on solarisx86. My previous test was from the 10.2 branch. To te

[jira] Commented: (DERBY-1846) Create a script that allows users to easily update their Derby jars with the JDBC4 classes.

[ http://issues.apache.org/jira/browse/DERBY-1846?page=comments#action_12436565 ] Andreas Korneliussen commented on DERBY-1846: - I think the script update-with-jdbc4 as it is now in SVN has a dangling-else problem if JAVA_HOME is set

[jira] Closed: (DERBY-1564) wisconsin.java test failed in DerbyNet or DerbyNetClient frameworks, VM for network server got OutOfMemoryError

[ http://issues.apache.org/jira/browse/DERBY-1564?page=all ] Andreas Korneliussen closed DERBY-1564. --- Thanks for resolving this issue, I agree it can be closed. > wisconsin.java test failed in DerbyNet or DerbyNetClient frameworks, VM for > network

[jira] Updated: (DERBY-1862) Simple hash improves performance

[ http://issues.apache.org/jira/browse/DERBY-1862?page=all ] Andreas Korneliussen updated DERBY-1862: Attachment: DERBY-1862v2.diff Attached incorrect patch (DERBY-1696v2.diff). The correct patch is DERBY-1862v2.diff. > Simple hash improves pe

[jira] Updated: (DERBY-1862) Simple hash improves performance

[ http://issues.apache.org/jira/browse/DERBY-1862?page=all ] Andreas Korneliussen updated DERBY-1862: Attachment: DERBY-1696v2.diff The attached patch makes a map of column names to column number. The map is populated when the first call to find

[jira] Commented: (DERBY-1177) updateObject with null as argument causes network driver to fail with NullPointerException

[ http://issues.apache.org/jira/browse/DERBY-1177?page=comments#action_12435486 ] Andreas Korneliussen commented on DERBY-1177: - REL NOTE: Problem 1: The derby client driver throws an exception when calling ResultSet.updateObject()

[jira] Updated: (DERBY-1862) Simple hash improves performance

[ http://issues.apache.org/jira/browse/DERBY-1862?page=all ] Andreas Korneliussen updated DERBY-1862: Attachment: DERBY-1862.diff Attached is a patch which uses another approach to improve the SQLEqualsIgnoreCase method. The patch check the iden

[jira] Commented: (DERBY-1696) transaction may sometimes keep lock on a row after moving off the resultset in scrollable updatable resultset

[ http://issues.apache.org/jira/browse/DERBY-1696?page=comments#action_12435207 ] Andreas Korneliussen commented on DERBY-1696: - I will update the patch for this issue once the DERBY-1799 is reviewed and committed, since these patche

[jira] Commented: (DERBY-1659) Document describe and show tables functionality

[ http://issues.apache.org/jira/browse/DERBY-1659?page=comments#action_12434702 ] Andreas Korneliussen commented on DERBY-1659: - I have just a minor comment on the doc: I have been testing this feature, and found that descrbie also c

[jira] Resolved: (DERBY-1691) jdbcapi/blobclob4BLOB.java fails under DerbyNet framework with JCC 2.6

[ http://issues.apache.org/jira/browse/DERBY-1691?page=all ] Andreas Korneliussen resolved DERBY-1691. - Resolution: Fixed Committed revision 442199. > jdbcapi/blobclob4BLOB.java fails under DerbyNet framework with JCC 2.6 >

[jira] Commented: (DERBY-1691) jdbcapi/blobclob4BLOB.java fails under DerbyNet framework with JCC 2.6

[ http://issues.apache.org/jira/browse/DERBY-1691?page=comments#action_12433805 ] Andreas Korneliussen commented on DERBY-1691: - Patch looks good. Got one conflict in DerbyNet.exclude, which I resolved. I will run some tests and comm

[jira] Resolved: (DERBY-1800) testSetBinaryStreamLengthLessOnBlobTooLong fails with 'Unexpected SQL state. expected:<22001> but was:<58009>'

[ http://issues.apache.org/jira/browse/DERBY-1800?page=all ] Andreas Korneliussen resolved DERBY-1800. - Fix Version/s: 10.3.0.0 Resolution: Fixed Committed revision 440062. > testSetBinaryStreamLengthLessOnBlobTooLong fails with 'Unexpec

[jira] Updated: (DERBY-1800) testSetBinaryStreamLengthLessOnBlobTooLong fails with 'Unexpected SQL state. expected:<22001> but was:<58009>'

[ http://issues.apache.org/jira/browse/DERBY-1800?page=all ] Andreas Korneliussen updated DERBY-1800: Component/s: Network Server > testSetBinaryStreamLengthLessOnBlobTooLong fails with 'Unexpected SQL state. > expected:<22001> but was:<58009>'

[jira] Commented: (DERBY-1800) testSetBinaryStreamLengthLessOnBlobTooLong fails with 'Unexpected SQL state. expected:<22001> but was:<58009>'

[ http://issues.apache.org/jira/browse/DERBY-1800?page=comments#action_12432508 ] Andreas Korneliussen commented on DERBY-1800: - Tests shows that the failure has been fixed. Derbyall passes. Running the jdbc40 suite, fails with more

[jira] Updated: (DERBY-1696) transaction may sometimes keep lock on a row after moving off the resultset in scrollable updatable resultset

[ http://issues.apache.org/jira/browse/DERBY-1696?page=all ] Andreas Korneliussen updated DERBY-1696: Derby Info: (was: [Patch Available]) Removing patch available flag, since the second patch makes SURQueryMixTest fail. > transaction may som

[jira] Updated: (DERBY-1696) transaction may sometimes keep lock on a row after moving off the resultset in scrollable updatable resultset

[ http://issues.apache.org/jira/browse/DERBY-1696?page=all ] Andreas Korneliussen updated DERBY-1696: Attachment: DERBY-1696v2.diff The attached patch also releases the lock on indexed scans. Additionally extended tests. > transaction may someti

[jira] Closed: (DERBY-1559) when receiving a single EXTDTA object representing a BLOB, the server do not need to read it into memory before inserting it into the DB

[ http://issues.apache.org/jira/browse/DERBY-1559?page=all ] Andreas Korneliussen closed DERBY-1559. --- > when receiving a single EXTDTA object representing a BLOB, the server do not > need to read it into memory before inserting it into the DB > --

[jira] Resolved: (DERBY-1559) when receiving a single EXTDTA object representing a BLOB, the server do not need to read it into memory before inserting it into the DB

[ http://issues.apache.org/jira/browse/DERBY-1559?page=all ] Andreas Korneliussen resolved DERBY-1559. - Fix Version/s: 10.2.2.0 Resolution: Fixed > when receiving a single EXTDTA object representing a BLOB, the server do not > need to rea

[jira] Updated: (DERBY-1800) testSetBinaryStreamLengthLessOnBlobTooLong fails with 'Unexpected SQL state. expected:<22001> but was:<58009>'

[ http://issues.apache.org/jira/browse/DERBY-1800?page=all ] Andreas Korneliussen updated DERBY-1800: Attachment: DERBY-1800.diff The problem is caused by not flushing the blob data after an exception occurs. Attached patch makes the test pass. I

[jira] Commented: (DERBY-1800) testSetBinaryStreamLengthLessOnBlobTooLong fails with 'Unexpected SQL state. expected:<22001> but was:<58009>'

[ http://issues.apache.org/jira/browse/DERBY-1800?page=comments#action_12432140 ] Andreas Korneliussen commented on DERBY-1800: - I will check if this is caused by DERBY-1559, and if that is the case, fix the issue. > testSetBinarySt

[jira] Assigned: (DERBY-1800) testSetBinaryStreamLengthLessOnBlobTooLong fails with 'Unexpected SQL state. expected:<22001> but was:<58009>'

[ http://issues.apache.org/jira/browse/DERBY-1800?page=all ] Andreas Korneliussen reassigned DERBY-1800: --- Assignee: Andreas Korneliussen > testSetBinaryStreamLengthLessOnBlobTooLong fails with 'Unexpected SQL state. > expected:<22001> but was:

[jira] Commented: (DERBY-1696) transaction may sometimes keep lock on a row after moving off the resultset in scrollable updatable resultset

[ http://issues.apache.org/jira/browse/DERBY-1696?page=comments#action_12432096 ] Andreas Korneliussen commented on DERBY-1696: - Thanks. Testing better with indexes also uncovered another locking issue w.r.t SUR : DERBY-1799. I will

[jira] Created: (DERBY-1799) SUR: current row not locked when renavigating to it, in queries with indexes

SUR: current row not locked when renavigating to it, in queries with indexes Key: DERBY-1799 URL: http://issues.apache.org/jira/browse/DERBY-1799 Project: Derby Iss

[jira] Updated: (DERBY-1740) Change error message to indicate encryptionkey length to be atleast 16 characters instead of 8 characters

[ http://issues.apache.org/jira/browse/DERBY-1740?page=all ] Andreas Korneliussen updated DERBY-1740: Urgency: (was: Urgent) Unsetting the urgency flag. I think the urgency should be set to normal, as it is a matter of incorrect error message,

[jira] Updated: (DERBY-1696) transaction may sometimes keep lock on a row after moving off the resultset in scrollable updatable resultset

[ http://issues.apache.org/jira/browse/DERBY-1696?page=all ] Andreas Korneliussen updated DERBY-1696: Derby Info: [Patch Available] > transaction may sometimes keep lock on a row after moving off the resultset > in scrollable updatable resultset

[jira] Updated: (DERBY-1559) when receiving a single EXTDTA object representing a BLOB, the server do not need to read it into memory before inserting it into the DB

[ http://issues.apache.org/jira/browse/DERBY-1559?page=all ] Andreas Korneliussen updated DERBY-1559: Fix Version/s: 10.3.0.0 Derby Info: (was: [Patch Available]) Committed revision 438478 at trunk. > when receiving a single EXTDTA obj

[jira] Updated: (DERBY-1696) transaction may sometimes keep lock on a row after moving off the resultset in scrollable updatable resultset

[ http://issues.apache.org/jira/browse/DERBY-1696?page=all ] Andreas Korneliussen updated DERBY-1696: Attachment: DERBY-1696.diff DERBY-1696.stat The attached patch addresses this bug by having the SQL-execution layer use ScanCon

[jira] Updated: (DERBY-1559) when receiving a single EXTDTA object representing a BLOB, the server do not need to read it into memory before inserting it into the DB

[ http://issues.apache.org/jira/browse/DERBY-1559?page=all ] Andreas Korneliussen updated DERBY-1559: Attachment: DERBY-1559v6.diff Found a bug while testing the patch DERBY-1559v5.diff: In case of an DRDAProtoclException while doing the streami

[jira] Commented: (DERBY-1559) when receiving a single EXTDTA object representing a BLOB, the server do not need to read it into memory before inserting it into the DB

[ http://issues.apache.org/jira/browse/DERBY-1559?page=comments#action_12431227 ] Andreas Korneliussen commented on DERBY-1559: - Thanks for the review. I will run some tests, and then commit the patch on the trunk. > when receiving a

[jira] Updated: (DERBY-1559) when receiving a single EXTDTA object representing a BLOB, the server do not need to read it into memory before inserting it into the DB

[ http://issues.apache.org/jira/browse/DERBY-1559?page=all ] Andreas Korneliussen updated DERBY-1559: Attachment: DERBY-1559v5.diff Attached patch makes DDMReader handle the DRDAProtocolException, and throws IOException from it, instead of doing

[jira] Commented: (DERBY-1559) when receiving a single EXTDTA object representing a BLOB, the server do not need to read it into memory before inserting it into the DB

[ http://issues.apache.org/jira/browse/DERBY-1559?page=comments#action_12430519 ] Andreas Korneliussen commented on DERBY-1559: - > One last thought, then: does it make any sense to have > DDMReader.readLobContinuationString > throw a

[jira] Updated: (DERBY-1696) transaction may sometimes keep lock on a row after moving off the resultset in scrollable updatable resultset

[ http://issues.apache.org/jira/browse/DERBY-1696?page=all ] Andreas Korneliussen updated DERBY-1696: Component/s: Store To fix this issue, I need a mechanism to notify the store (scancontroller) to move off the row (i.e to afterLast() or before

[jira] Assigned: (DERBY-1696) transaction may sometimes keep lock on a row after moving off the resultset in scrollable updatable resultset

[ http://issues.apache.org/jira/browse/DERBY-1696?page=all ] Andreas Korneliussen reassigned DERBY-1696: --- Assignee: Andreas Korneliussen > transaction may sometimes keep lock on a row after moving off the resultset > in scrollable updatable re

[jira] Commented: (DERBY-1559) when receiving a single EXTDTA object representing a BLOB, the server do not need to read it into memory before inserting it into the DB

[ http://issues.apache.org/jira/browse/DERBY-1559?page=comments#action_12430431 ] Andreas Korneliussen commented on DERBY-1559: - Hi, I thought I had addressed the comment by capturing the stack trace in DDMReader.readLobContiniationS

[jira] Updated: (DERBY-1559) when receiving a single EXTDTA object representing a BLOB, the server do not need to read it into memory before inserting it into the DB

[ http://issues.apache.org/jira/browse/DERBY-1559?page=all ] Andreas Korneliussen updated DERBY-1559: Attachment: DERBY-1559v4.diff Thanks for reviewing the patch. Attached is a patch where I try to address the issue w.r.t preserving the informa

[jira] Updated: (DERBY-1559) when receiving a single EXTDTA object representing a BLOB, the server do not need to read it into memory before inserting it into the DB

[ http://issues.apache.org/jira/browse/DERBY-1559?page=all ] Andreas Korneliussen updated DERBY-1559: Attachment: DERBY-1559v3.diff Attached is an updated patch were the conflicts from DERBY-1610 has been resolved. Additionally, to avoid the fa

[jira] Closed: (DERBY-1558) enable more testcases in ConcurrencyTest

[ http://issues.apache.org/jira/browse/DERBY-1558?page=all ] Andreas Korneliussen closed DERBY-1558. --- > enable more testcases in ConcurrencyTest > > > Key: DERBY-1558 > URL: http:

[jira] Resolved: (DERBY-1558) enable more testcases in ConcurrencyTest

[ http://issues.apache.org/jira/browse/DERBY-1558?page=all ] Andreas Korneliussen resolved DERBY-1558. - Resolution: Fixed > enable more testcases in ConcurrencyTest > > > Key: DERBY-1558 >

[jira] Commented: (DERBY-1558) enable more testcases in ConcurrencyTest

[ http://issues.apache.org/jira/browse/DERBY-1558?page=comments#action_12429682 ] Andreas Korneliussen commented on DERBY-1558: - Committed revision 433607. > enable more testcases in ConcurrencyTest > ---

[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_12429473 ] Andreas Korneliussen commented on DERBY-418: Assuming the Derby embedded JDBC driver is thread-safe, it should be safe for a result set to call its own

[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_12429438 ] Andreas Korneliussen commented on DERBY-418: I am not sure what you mean. Could you give an example ? I agree that it is possible to get a deadlock in

[jira] Commented: (DERBY-1387) Add JMX extensions to Derby

[ http://issues.apache.org/jira/browse/DERBY-1387?page=comments#action_12429432 ] Andreas Korneliussen commented on DERBY-1387: - Hi, thanks for providing this patch. I have tried compiling it, and I do have the following comments: 1

[jira] Commented: (DERBY-1559) when receiving a single EXTDTA object representing a BLOB, the server do not need to read it into memory before inserting it into the DB

[ http://issues.apache.org/jira/browse/DERBY-1559?page=comments#action_12429406 ] Andreas Korneliussen commented on DERBY-1559: - I will wait for DERBY-1610 being fixed, to avoid the risk. > when receiving a single EXTDTA object repr

[jira] Commented: (DERBY-1559) when receiving a single EXTDTA object representing a BLOB, the server do not need to read it into memory before inserting it into the DB

[ http://issues.apache.org/jira/browse/DERBY-1559?page=comments#action_12429394 ] Andreas Korneliussen commented on DERBY-1559: - DERBY-1535 caused conflicts with this patch during development. Now, DERBY-1610 will cause conflicts wit

[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_12429386 ] Andreas Korneliussen commented on DERBY-418: The finalizer thread is as pr javadoc guaranteed to not hold any user-visible synchronization locks when fi

[jira] Updated: (DERBY-1558) enable more testcases in ConcurrencyTest

[ http://issues.apache.org/jira/browse/DERBY-1558?page=all ] Andreas Korneliussen updated DERBY-1558: Attachment: DERBY-1558.diff DERBY-1558.stat Attaching patch which enables more testcases in ConcurrencyTest. The patch makes use

[jira] Closed: (DERBY-1712) Add a JUnit test decorator that starts the NetworkServer at setUp and stops it at tearDown.

[ http://issues.apache.org/jira/browse/DERBY-1712?page=all ] Andreas Korneliussen closed DERBY-1712. --- > Add a JUnit test decorator that starts the NetworkServer at setUp and stops > it at tearDown. > ---

[jira] Resolved: (DERBY-1712) Add a JUnit test decorator that starts the NetworkServer at setUp and stops it at tearDown.

[ http://issues.apache.org/jira/browse/DERBY-1712?page=all ] Andreas Korneliussen resolved DERBY-1712. - Resolution: Fixed > Add a JUnit test decorator that starts the NetworkServer at setUp and stops > it at tearDown. > -

[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_12429361 ] Andreas Korneliussen commented on DERBY-418: I think that the lack of synchronization when calling singleUseActivation.markUnused() may cause that other

[jira] Updated: (DERBY-1559) when receiving a single EXTDTA object representing a BLOB, the server do not need to read it into memory before inserting it into the DB

[ http://issues.apache.org/jira/browse/DERBY-1559?page=all ] Andreas Korneliussen updated DERBY-1559: Urgency: Normal Affects Version/s: 10.2.2.0 10.3.0.0 Derby Info: [Patch Available] I will consid

[jira] Updated: (DERBY-1712) Add a JUnit test decorator that starts the NetworkServer at setUp and stops it at tearDown.

[ http://issues.apache.org/jira/browse/DERBY-1712?page=all ] Andreas Korneliussen updated DERBY-1712: Attachment: DERBY-1712.diff DERBY-1712.stat The patch (DERBY-1712.diff) has a new class NetworkServerTestSetup. This class is p

[jira] Created: (DERBY-1712) Add a JUnit test decorator that starts the NetworkServer at setUp and stops it at tearDown.

Add a JUnit test decorator that starts the NetworkServer at setUp and stops it at tearDown. --- Key: DERBY-1712 URL: http://issues.apache.org/jira/browse/DERBY-1712

[jira] Updated: (DERBY-1558) enable more testcases in ConcurrencyTest

[ http://issues.apache.org/jira/browse/DERBY-1558?page=all ] Andreas Korneliussen updated DERBY-1558: Summary: enable more testcases in ConcurrencyTest (was: include ConcurrencyTest into a suite) Description: A number of testcases, whi

[jira] Created: (DERBY-1696) transaction may sometimes keep lock on a row after moving off the resultset in scrollable updatable resultset

transaction may sometimes keep lock on a row after moving off the resultset in scrollable updatable resultset - Key: DERBY-1696 URL: http://issues.apache.o

[jira] Updated: (DERBY-1559) when receiving a single EXTDTA object representing a BLOB, the server do not need to read it into memory before inserting it into the DB

[ http://issues.apache.org/jira/browse/DERBY-1559?page=all ] Andreas Korneliussen updated DERBY-1559: Attachment: DERBY-1559v2.diff Attached is an updated patch which preserves the changes in DERBY-1535 when receiving multiple EXTDTA objects. >

[jira] Commented: (DERBY-1600) JUnit test SURQueryMixTest does not follow the typical pattern for JUnit tests.

[ http://issues.apache.org/jira/browse/DERBY-1600?page=comments#action_12423905 ] Andreas Korneliussen commented on DERBY-1600: - See: http://junit.sourceforge.net/doc/cookstour/cookstour.htm run() is a template method, it will call:

[jira] Commented: (DERBY-1559) when receiving a single EXTDTA object representing a BLOB, the server do not need to read it into memory before inserting it into the DB

[ http://issues.apache.org/jira/browse/DERBY-1559?page=comments#action_12423868 ] Andreas Korneliussen commented on DERBY-1559: - Thanks I will update the patch to follow the approach suggested in DERBY-1535 when receiving multiple EX

[jira] Commented: (DERBY-1564) wisconsin.sql test failed in DerbyNet framework, VM for network server got OutOfMemoryError

[ http://issues.apache.org/jira/browse/DERBY-1564?page=comments#action_12423858 ] Andreas Korneliussen commented on DERBY-1564: - I think experimenting with different heap-sizes is slightly off-track, since all it may prove is that de

[jira] Updated: (DERBY-1559) when receiving a single EXTDTA object representing a BLOB, the server do not need to read it into memory before inserting it into the DB

[ http://issues.apache.org/jira/browse/DERBY-1559?page=all ] Andreas Korneliussen updated DERBY-1559: Attachment: DERBY-1559.diff DERBY-1559.stat Attached is a patch which does the following: EXTDTAReaderInputStream: this is a ne

[jira] Commented: (DERBY-1545) derbynet/testProtocol.java fails with security manager enabled

[ http://issues.apache.org/jira/browse/DERBY-1545?page=comments#action_12423828 ] Andreas Korneliussen commented on DERBY-1545: - Improved the original patch by also granting permission to "${derbyTesting.serverhost}". This should mak

[jira] Commented: (DERBY-1241) logmirror.ctrl is getting accessed outside the privileged block when the checkpoint instant is invalid on log factory boot method.

[ http://issues.apache.org/jira/browse/DERBY-1241?page=comments#action_12423822 ] Andreas Korneliussen commented on DERBY-1241: - The following scenario reproduced this problem: 1. Start Network server with security manager enabled 2.

[jira] Closed: (DERBY-1598) unable to boot exisiting database from network server when running with security manager

[ http://issues.apache.org/jira/browse/DERBY-1598?page=all ] Andreas Korneliussen closed DERBY-1598. --- Resolution: Duplicate Duplicate: http://issues.apache.org/jira/browse/DERBY-1241 > unable to boot exisiting database from network server when run

[jira] Updated: (DERBY-1598) unable to boot exisiting database from network server when running with security manager

[ http://issues.apache.org/jira/browse/DERBY-1598?page=all ] Andreas Korneliussen updated DERBY-1598: Description: Myrna van Lunteren reported the following: Quote I ran into the following interesting situation with permissions gr

[jira] Created: (DERBY-1598) unable to boot exisiting database from network server when running with security manager

unable to boot exisiting database from network server when running with security manager Key: DERBY-1598 URL: http://issues.apache.org/jira/browse/DERBY-1598 Pro

[jira] Created: (DERBY-1595) Network server fails with DRDAProtocolException if a BLOB with size 2147483647 is streamed from client

Network server fails with DRDAProtocolException if a BLOB with size 2147483647 is streamed from client -- Key: DERBY-1595 URL: http://issues.apache.org/jira/browse

[jira] Closed: (DERBY-1545) derbynet/testProtocol.java fails with security manager enabled

[ http://issues.apache.org/jira/browse/DERBY-1545?page=all ] Andreas Korneliussen closed DERBY-1545. --- > derbynet/testProtocol.java fails with security manager enabled > -- > >

[jira] Resolved: (DERBY-1545) derbynet/testProtocol.java fails with security manager enabled

[ http://issues.apache.org/jira/browse/DERBY-1545?page=all ] Andreas Korneliussen resolved DERBY-1545. - Fix Version/s: 10.2.0.0 Resolution: Fixed Committed revision 425732. > derbynet/testProtocol.java fails with security manager enabled

[jira] Resolved: (DERBY-1587) INTEGER function cannot be abbreviated

[ http://issues.apache.org/jira/browse/DERBY-1587?page=all ] Andreas Korneliussen resolved DERBY-1587. - Fix Version/s: 10.2.0.0 Resolution: Fixed Derby Info: (was: [Patch Available]) Thanks for contributing. Committed revision 42

[jira] Updated: (DERBY-1545) derbynet/testProtocol.java fails with security manager enabled

[ http://issues.apache.org/jira/browse/DERBY-1545?page=all ] Andreas Korneliussen updated DERBY-1545: Attachment: DERBY-1545.diff DERBY-1545.stat Attached is a patch (DERBY-1545.diff + stat) which gives socket permission to derby

[jira] Assigned: (DERBY-1545) derbynet/testProtocol.java fails with security manager enabled

[ http://issues.apache.org/jira/browse/DERBY-1545?page=all ] Andreas Korneliussen reassigned DERBY-1545: --- Assignee: Andreas Korneliussen > derbynet/testProtocol.java fails with security manager enabled >

[jira] Commented: (DERBY-1545) derbynet/testProtocol.java fails with security manager enabled

[ http://issues.apache.org/jira/browse/DERBY-1545?page=comments#action_12423599 ] Andreas Korneliussen commented on DERBY-1545: - The test code (TestProto is packed into derbyTesting.jar), does new Socket(hostName, 1527). derbyTesting

[jira] Commented: (DERBY-1587) INTEGER function cannot be abbreviated

[ http://issues.apache.org/jira/browse/DERBY-1587?page=comments#action_12423578 ] Andreas Korneliussen commented on DERBY-1587: - I think the patch looks good and can be committed. > INTEGER function cannot be abbreviated > -

[jira] Commented: (DERBY-1535) Trial 2 for DERBY-550, improve use of Engine from NetworkServer and reduce memory usage

[ http://issues.apache.org/jira/browse/DERBY-1535?page=comments#action_12423375 ] Andreas Korneliussen commented on DERBY-1535: - I think there could be a problem here: DRDAConnThread: - p

[jira] Resolved: (DERBY-1296) Setting property derby.system.bootAll causes an Exception

[ http://issues.apache.org/jira/browse/DERBY-1296?page=all ] Andreas Korneliussen resolved DERBY-1296. - Resolution: Fixed Derby Info: (was: [Patch Available]) Thanks for resolving the conflict. Committed revision 425388. > Setting propert

[jira] Commented: (DERBY-1296) Setting property derby.system.bootAll causes an Exception

[ http://issues.apache.org/jira/browse/DERBY-1296?page=comments#action_12423000 ] Andreas Korneliussen commented on DERBY-1296: - Thanks for making the patch for this critical issue. It seems there is a conflict when applying it, due

[jira] Commented: (DERBY-1564) wisconsin.sql test failed in DerbyNet framework, VM for network server got OutOfMemoryError

[ http://issues.apache.org/jira/browse/DERBY-1564?page=comments#action_12422684 ] Andreas Korneliussen commented on DERBY-1564: - Do note that that there was not output in the outfile, and the diff file is therefore the entire master

[jira] Updated: (DERBY-1564) wisconsin.sql test failed in DerbyNet framework, VM for network server got OutOfMemoryError

[ http://issues.apache.org/jira/browse/DERBY-1564?page=all ] Andreas Korneliussen updated DERBY-1564: Attachment: wisconsin.tar.gz Attaching log from test (wisconsin.tar.gz) > wisconsin.sql test failed in DerbyNet framework, VM for network serve

[jira] Created: (DERBY-1564) wisconsin.sql test failed in DerbyNet framework, VM for network server got OutOfMemoryError

wisconsin.sql test failed in DerbyNet framework, VM for network server got OutOfMemoryError --- Key: DERBY-1564 URL: http://issues.apache.org/jira/browse/DERBY-1564

[jira] Created: (DERBY-1559) when receiving a single EXTDTA object representing a BLOB, the server do not need to read it into memory before inserting it into the DB

when receiving a single EXTDTA object representing a BLOB, the server do not need to read it into memory before inserting it into the DB Key: D

[jira] Created: (DERBY-1558) include ConcurrencyTest into a suite

include ConcurrencyTest into a suite Key: DERBY-1558 URL: http://issues.apache.org/jira/browse/DERBY-1558 Project: Derby Issue Type: Test Components: Test Affects Versions: 10.2.0.0

[jira] Updated: (DERBY-1351) lang/forupdate.sql fails with derbyclient in the 10.1 branch

[ http://issues.apache.org/jira/browse/DERBY-1351?page=all ] Andreas Korneliussen updated DERBY-1351: Derby Info: (was: [Patch Available]) svn merge -r420534:420535 https://svn.apache.org/repos/asf/db/derby/code/trunk A java/testing/org/apa

[jira] Commented: (DERBY-1511) SELECT clause without a WHERE, causes an Exception when extracting a Blob from a database

[ http://issues.apache.org/jira/browse/DERBY-1511?page=comments#action_12422368 ] Andreas Korneliussen commented on DERBY-1511: - Yes. If you modify the code, and replace readTable1(..) with con.commit(), you will see this issue with

[jira] Commented: (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=comments#action_12421848 ] Andreas Korneliussen commented on DERBY-694: I think a test was disabled in DERBY-506. According to DERBY-705, it can be enabled once this issue has bee

[jira] Resolved: (DERBY-802) OutofMemory Error when reading large blob when statement type is ResultSet.TYPE_SCROLL_INSENSITIVE

[ http://issues.apache.org/jira/browse/DERBY-802?page=all ] Andreas Korneliussen resolved DERBY-802. Fix Version/s: 10.2.0.0 Resolution: Fixed Derby Info: (was: [Patch Available]) Thanks for reviewing. Committed revision 423034.

[jira] Updated: (DERBY-802) OutofMemory Error when reading large blob when statement type is ResultSet.TYPE_SCROLL_INSENSITIVE

[ http://issues.apache.org/jira/browse/DERBY-802?page=all ] Andreas Korneliussen updated DERBY-802: --- Attachment: derby-802v3.diff derby-802v3.stat Attached is a patch (derby-802v3.diff and derby-802v3.stat) which uses projectmappin

[jira] Commented: (DERBY-802) OutofMemory Error when reading large blob when statement type is ResultSet.TYPE_SCROLL_INSENSITIVE

[ http://issues.apache.org/jira/browse/DERBY-802?page=comments#action_12421136 ] Andreas Korneliussen commented on DERBY-802: Thank you very much for the review comments. I agree that the undo-projection code can be improved, (someth

[jira] Closed: (DERBY-1497) assert failure in MessageUtil, because exception thrown with too many parameters when handling OutOfMemoryError

[ http://issues.apache.org/jira/browse/DERBY-1497?page=all ] Andreas Korneliussen closed DERBY-1497: --- > assert failure in MessageUtil, because exception thrown with too many > parameters when handling OutOfMemoryError > --

[jira] Resolved: (DERBY-1497) assert failure in MessageUtil, because exception thrown with too many parameters when handling OutOfMemoryError

[ http://issues.apache.org/jira/browse/DERBY-1497?page=all ] Andreas Korneliussen resolved DERBY-1497: - Resolution: Fixed Committed revision 421566. > assert failure in MessageUtil, because exception thrown with too many > parameters when

[jira] Updated: (DERBY-1497) assert failure in MessageUtil, because exception thrown with too many parameters when handling OutOfMemoryError

[ http://issues.apache.org/jira/browse/DERBY-1497?page=all ] Andreas Korneliussen updated DERBY-1497: Attachment: DERBY-1497v2.diff New patch which preserves the stack trace of OutOfMemoryError, as cause. > assert failure in MessageUtil, becaus

[jira] Reopened: (DERBY-1497) assert failure in MessageUtil, because exception thrown with too many parameters when handling OutOfMemoryError

[ http://issues.apache.org/jira/browse/DERBY-1497?page=all ] Andreas Korneliussen reopened DERBY-1497: - Will update the fix so that a constructor of DisconnectException which takes Throwable is used. After applying the new fix, the stack trace

[jira] Commented: (DERBY-802) OutofMemory Error when reading large blob when statement type is ResultSet.TYPE_SCROLL_INSENSITIVE

[ http://issues.apache.org/jira/browse/DERBY-802?page=comments#action_12420819 ] Andreas Korneliussen commented on DERBY-802: Withdrawing derby-802v2.diff, since it makes SURQueryMixTest.junit fail. The first patch has been run with no failures i

[jira] Updated: (DERBY-802) OutofMemory Error when reading large blob when statement type is ResultSet.TYPE_SCROLL_INSENSITIVE

[ http://issues.apache.org/jira/browse/DERBY-802?page=all ] Andreas Korneliussen updated DERBY-802: --- Attachment: derby-802v2.diff The attached diff (derby-802v2.diff) has one change compared to the first diff: * The logic for undoing the projection

[jira] Commented: (DERBY-1486) ERROR 40XD0 - When exracting Blob from a database

[ http://issues.apache.org/jira/browse/DERBY-1486?page=comments#action_12420618 ] Andreas Korneliussen commented on DERBY-1486: - To clarify: this applies only in autocommit: > Executing a new statement, will cause a commit on the current transact

[jira] Commented: (DERBY-1486) ERROR 40XD0 - When exracting Blob from a database

[ http://issues.apache.org/jira/browse/DERBY-1486?page=comments#action_12420614 ] Andreas Korneliussen commented on DERBY-1486: - Executing a new statement, will cause a commit on the current transaction, which is in line with the standard. The r

[jira] Commented: (DERBY-550) BLOB : java.lang.OutOfMemoryError with network JDBC driver (org.apache.derby.jdbc.ClientDriver)

[ http://issues.apache.org/jira/browse/DERBY-550?page=comments#action_12420591 ] Andreas Korneliussen commented on DERBY-550: Unless the streaming could be fixed for 10.2 so that we avoid OutOfMemoryError on the receiver side, I would propose th

[jira] Commented: (DERBY-1486) ERROR 40XD0 - When exracting Blob from a database

[ http://issues.apache.org/jira/browse/DERBY-1486?page=comments#action_12420571 ] Andreas Korneliussen commented on DERBY-1486: - When executing a statement in autocommit mode, the transaction will be committed. You are using forward-only, hold

[jira] Closed: (DERBY-1361) positioned updates and deletes allowed after a commit without repositioning the cursor - if the table is indexed on the columns selected

[ http://issues.apache.org/jira/browse/DERBY-1361?page=all ] Andreas Korneliussen closed DERBY-1361: --- > positioned updates and deletes allowed after a commit without repositioning > the cursor - if the table is indexed on the columns selected > -

[jira] Closed: (DERBY-717) update doc on updatable cursors

[ http://issues.apache.org/jira/browse/DERBY-717?page=all ] Andreas Korneliussen closed DERBY-717: -- > update doc on updatable cursors > --- > > Key: DERBY-717 > URL: http://issues.apache.org/jira/browse

  1   2   3   4   >