[ 
https://issues.apache.org/jira/browse/DERBY-6533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Rick Hillegas updated DERBY-6533:
---------------------------------

    Attachment: derby-6533-04-outOfMemory.diff

Attaching derby-6533-04-outOfMemory.diff. This patch adds some additional 
defenses against OutOfMemoryErrors in NsTest:

1) Now the test records the last measurements taken by the memory checker 
thread. The last memory measurements are reported when the test prints out its 
statistics at the end.

2) When recording an exception, the test now checks whether the exception was 
(or was caused by) an OutOfMemoryError. If so, the statistics are printed and 
the program ends.

Knut thinks that the OutOfMemoryError I saw in the last run was caused by a bug 
in JVM 8: https://bugs.openjdk.java.net/browse/JDK-8034852 . The workaround is 
to run the test with this setting:

  -XX:MaxMetaspaceFreeRatio=100


Touches the following files:

M       java/testing/org/apache/derbyTesting/system/nstest/utils/MemCheck.java
M       java/testing/org/apache/derbyTesting/system/nstest/NsTest.java


> Add a quiet mode to NsTest
> --------------------------
>
>                 Key: DERBY-6533
>                 URL: https://issues.apache.org/jira/browse/DERBY-6533
>             Project: Derby
>          Issue Type: Improvement
>          Components: Test
>    Affects Versions: 10.11.0.0
>            Reporter: Rick Hillegas
>            Assignee: Rick Hillegas
>         Attachments: derby-6533-01-aa-quietMode.diff, 
> derby-6533-02-aa-sequencesAndMoreStats.diff, 
> derby-6533-02-aa-sequencesAndMoreStats.out, derby-6533-03-timerThread.diff, 
> derby-6533-04-outOfMemory.diff
>
>
> Right now NsTest produces an enormous log file. This may be useful for 
> tracking down some errors. However, this can also make it hard to find the 
> signal in the noise. It would be good to turn off the chatty diagnostics 
> which report the result of every insert, update, delete, and select. A 
> summary at the end may be good enough, including a summary of the number of 
> times each kind of error (SQLState) was seen. While I'm in there, I plan to 
> make other smallish changes.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to