db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Knut Anders Hatlen (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DERBY-6215) derby.log grows enormously during StressMultiTest
Date Fri, 10 May 2013 09:25:17 GMT

    [ https://issues.apache.org/jira/browse/DERBY-6215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13653665#comment-13653665
] 

Knut Anders Hatlen commented on DERBY-6215:
-------------------------------------------

Committed revision 1480947.

I'm planning to backport this fix to 10.8, as the nightly tests have sometimes run out of
disk space lately, and I think this issue might be the root cause.
                
> derby.log grows enormously during StressMultiTest
> -------------------------------------------------
>
>                 Key: DERBY-6215
>                 URL: https://issues.apache.org/jira/browse/DERBY-6215
>             Project: Derby
>          Issue Type: Bug
>          Components: Test
>    Affects Versions: 10.11.0.0
>            Reporter: Knut Anders Hatlen
>            Assignee: Knut Anders Hatlen
>         Attachments: derby-6215-01-a.diff
>
>
> When running suites.All with sane jars, I've seen derby.log grow very big (over 4GB)
during StressMultiTest. I don't see this when StressMultiTest is run separately, only when
it runs as part of suites.All.
> What takes the most space in derby.log is debug output like this
> DEBUG DaemonTrace OUTPUT: Next urgent assignment : org.apache.derby.impl.services.daemon.ServiceRecord@d1294d
> DEBUG DaemonTrace OUTPUT: servicing org.apache.derby.impl.services.daemon.ServiceRecord@d1294d
> DEBUG DaemonTrace OUTPUT: done org.apache.derby.impl.services.daemon.ServiceRecord@d1294d
> DEBUG DaemonTrace OUTPUT: come back from yield
> repeated over and over.
> I suspect there's a test that sets the DaemonTrace debug flag, and that the flag for
some reason doesn't get reset. I've only found one test that sets it: ClobReclamationTest.
It uses a SystemPropertyTestSetup ensure the derby.debug.true property is reset and the engine
rebooted, but I'm not sure rebooting the engine will reset the state of the SanityManager.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message