[
https://issues.apache.org/jira/browse/DERBY-3574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12588315#action_12588315
]
Tiago R. Espinha commented on DERBY-3574:
-----------------------------------------
Ok I have a problem.
I ran the command that Kathey posted (without the -D switch and with -Xmx1024M
since it gave out of memory with just 512MiB) and I got a stackload of error
lines after a few hours of running. Here's what it said in the end:
FAILURES!!!
Tests run: 8010, Failures: 1, Errors: 8
Somehow I get the feeling that this is still a memory issue. I'm running the
tests in a Virtual Machine running Ubuntu 7.10 with just 1GiB of RAM, and after
a while, java is using all the RAM and has entered the swap file. Should I
discard the VM and run it all natively on XP where I have 2GiB of RAM?
> With client, attempting to get the lob length after commit or connection
> close if there was a call to length() before commit does not throw an
> exception
> ----------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-3574
> URL: https://issues.apache.org/jira/browse/DERBY-3574
> Project: Derby
> Issue Type: Bug
> Components: JDBC, Network Client, Newcomer
> Affects Versions: 10.5.0.0
> Reporter: Kathey Marsden
> Assignee: Tiago R. Espinha
> Priority: Trivial
> Attachments: derby3574-wtest.patch, derby3574.patch,
> TestLobLength.java
>
>
> Attempting to get call Blob/Clob.length() after commit or connection close
> does not fail if there was a previous call to length(). If no previous call
> was made an exception is thrown as expected.
> See attached program TestLobLength for repro with commit. If you comment out
> the two lines to get the length before the commit we get the expected
> exception.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
