[jira] Commented: (DERBY-1446) Derby can enter infinite loop and consume 100% cpu when loading class when running a stored procedure within Eclipse 3.2

[ http://issues.apache.org/jira/browse/DERBY-1446?page=comments#action_12417582 ] Kathey Marsden commented on DERBY-1446: --- The location of the infinite recursion is in ReflectClassesJava2 in this code right underneath the comments about the other

[jira] Updated: (DERBY-1425) testProtocol hangs with 10.1 client talking to 10.2 server

[ http://issues.apache.org/jira/browse/DERBY-1425?page=all ] Knut Anders Hatlen updated DERBY-1425: -- Attachment: ddmreader_initialize.diff ddmreader_initialize.diff contains the changes to DDMReader which made the hang go away. I have not had time

[jira] Commented: (DERBY-955) Get derbyall on jdk1.6

[ http://issues.apache.org/jira/browse/DERBY-955?page=comments#action_12417592 ] Knut Anders Hatlen commented on DERBY-955: -- The patch looks clean and simple. Ran derbyall on jdk15 with one error (runtimeinfo.java which fails more or less all the

Regression Test Failure! - Derby 416774 - Sun DBTG

[Auto-generated mail] *Derby* 416774/2006-06-23 19:46:08 CEST *derbyall* Failed TestsOK Skip Duration Platform --- *Jvm: 1.6* 15715700 0 106.71% SunOS-5.10_i86pc-i386 Details in

[jira] Updated: (DERBY-1364) Client driver does not roll back the effects of a stored procedure when incorrectly invoked by executeQuery()/executeUpdate()

[ http://issues.apache.org/jira/browse/DERBY-1364?page=all ] Knut Anders Hatlen updated DERBY-1364: -- Attachment: derby-1364-v1.diff derby-1364-v1.stat Attached a patch (derby-1364-v1.diff) which attempts to fix this issue.

[jira] Updated: (DERBY-1364) Client driver does not roll back the effects of a stored procedure when incorrectly invoked by executeQuery()/executeUpdate()

[ http://issues.apache.org/jira/browse/DERBY-1364?page=all ] Knut Anders Hatlen updated DERBY-1364: -- Derby Info: [Patch Available] Client driver does not roll back the effects of a stored procedure when incorrectly invoked by

Re: Question about splitQRYDTA and offbyone error message.

Sunitha Kambhampati wrote: they are hitting an edge case, where the writer.getDSSLength() is equal to blksize and this DSS is the only dss in the send buffer. Hi Sunitha, Yes, I completely agree with your analysis. There is an off-by-one bug in the fix for DERBY-170. Thank you very much for

Re: Question about splitQRYDTA and offbyone error message.

Bryan Pendleton wrote: Sunitha Kambhampati wrote: they are hitting an edge case, where the writer.getDSSLength() is equal to blksize and this DSS is the only dss in the send buffer. Below is a simple repro program that you can run to demonstrate the bug for yourself. Compile it, then start

Re: Question about splitQRYDTA and offbyone error message.

I am fine either ways. If opening a new jira is easy, then we should just do that. Since DERBY-170 is already backported to 10.1, we will need to backport this fix to 10.1 also. If we go with opening a new issue, it might be good to link this new issue with derby-170 using jira links, so

[jira] Created: (DERBY-1454) DRDA Protocol Exception when DSS is exactly 32767 in length

DRDA Protocol Exception when DSS is exactly 32767 in length --- Key: DERBY-1454 URL: http://issues.apache.org/jira/browse/DERBY-1454 Project: Derby Type: Sub-task Components: Network Server Versions:

[jira] Updated: (DERBY-1454) DRDA Protocol Exception when DSS is exactly 32767 in length

[ http://issues.apache.org/jira/browse/DERBY-1454?page=all ] Bryan Pendleton updated DERBY-1454: --- Attachment: newBug.java Attached as 'newBug.java' is a simple repro program that you can run to demonstrate the bug for yourself. Compile it, then start

[jira] Updated: (DERBY-1454) DRDA Protocol Exception when DSS is exactly 32767 in length

[ http://issues.apache.org/jira/browse/DERBY-1454?page=all ] Bryan Pendleton updated DERBY-1454: --- Attachment: derby-1454.diff Attached 'derby-1454.diff' is a proposed patch for this issue. The patch corrects the two splitQRYDTA calls to use rather

[jira] Created: (DERBY-1455) Intermittent failure in derbynet/runtimeinfo.java

Intermittent failure in derbynet/runtimeinfo.java - Key: DERBY-1455 URL: http://issues.apache.org/jira/browse/DERBY-1455 Project: Derby Type: Bug Components: Test Versions: 10.2.0.0 Reporter: Knut

[jira] Updated: (DERBY-1455) Intermittent failure in derbynet/runtimeinfo.java

[ http://issues.apache.org/jira/browse/DERBY-1455?page=all ] Knut Anders Hatlen updated DERBY-1455: -- Attachment: derby-1455.diff derby-1455.stat Attached a patch which seems to fix the problem. I ran the test 421 times with the jar

[jira] Updated: (DERBY-1455) Intermittent failure in derbynet/runtimeinfo.java

[ http://issues.apache.org/jira/browse/DERBY-1455?page=all ] Knut Anders Hatlen updated DERBY-1455: -- Derby Info: [Patch Available] Intermittent failure in derbynet/runtimeinfo.java - Key:

[jira] Commented: (DERBY-1454) DRDA Protocol Exception when DSS is exactly 32767 in length

[ http://issues.apache.org/jira/browse/DERBY-1454?page=comments#action_12417646 ] Bryan Pendleton commented on DERBY-1454: I didn't mark this a regression and I don't think it is. The erroneous = has been in the code for a while, and was not

[jira] Commented: (DERBY-1454) DRDA Protocol Exception when DSS is exactly 32767 in length

[ http://issues.apache.org/jira/browse/DERBY-1454?page=comments#action_12417647 ] Sunitha Kambhampati commented on DERBY-1454: Thanks much Bryan for posting the patch. The changes look good to me. I successfully applied the derby-1454.diff

[jira] Resolved: (DERBY-1454) DRDA Protocol Exception when DSS is exactly 32767 in length

[ http://issues.apache.org/jira/browse/DERBY-1454?page=all ] Bryan Pendleton resolved DERBY-1454: Fix Version: 10.2.0.0 Resolution: Fixed Thank you Sunitha for the quick review. derbyall ran clean for me, so I am committing this fix. SVN

Re: Port fix for DERBY-1454 to 10.1 branch for 10.1.3?

Bryan Pendleton wrote: I know we're way past the 10.1.3 deadline, so if we could get some review of the DERBY-1454 patch, and some opinions from the community about whether the fix is reasonable to port to 10.1 at this late date, that would be much appreciated. The patch looks good to me and I

[jira] Commented: (DERBY-1373) Encrypted databases cannot be booted using the jar subprotocol (and possibly also using http/https/classpath)

[ http://issues.apache.org/jira/browse/DERBY-1373?page=comments#action_12417652 ] Andrew McIntyre commented on DERBY-1373: Mathias, if you can address the issues with the patch mentioned by Sunitha by midday Monday, we can get this into 10.1.3.

Re: Port fix for DERBY-1454 to 10.1 branch for 10.1.3?

On 6/24/06, Kathey Marsden [EMAIL PROTECTED] wrote: Bryan Pendleton wrote: I know we're way past the 10.1.3 deadline, so if we could get some review of the DERBY-1454 patch, and some opinions from the community about whether the fix is reasonable to port to 10.1 at this late date, that

[jira] Created: (DERBY-1456) Network Server agentError calls log only to console and are hard to diagnose

Network Server agentError calls log only to console and are hard to diagnose Key: DERBY-1456 URL: http://issues.apache.org/jira/browse/DERBY-1456 Project: Derby Type: Sub-task