[jbossts-issues] [JBoss JIRA] (JBTM-2234) out of memory when logging more messages than heap size (surefire issue)

Amos Feng (JIRA) issues at jboss.org
Thu Aug 20 01:52:26 EDT 2015

    [ https://issues.jboss.org/browse/JBTM-2234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13100036#comment-13100036 ] 

Amos Feng commented on JBTM-2234:

Thanks Mike,

I create the jacorb.properties in the ArjunaJTS/jts/src/test/resource and add "jacorb.log.default.verbosity=2". But it looks like there are still INFO messages in the surefire-report/com.hp.mwtests.ts.jts.orbspecific.local.performance.Performance2-output.txt 

> out of memory when logging more messages than heap size (surefire issue)
> ------------------------------------------------------------------------
>                 Key: JBTM-2234
>                 URL: https://issues.jboss.org/browse/JBTM-2234
>             Project: JBoss Transaction Manager
>          Issue Type: Bug
>          Components: Performance Testing
>    Affects Versions: 5.0.2
>         Environment: JTS testing 
>            Reporter: Michael Musgrove
>            Assignee: Amos Feng
>            Priority: Optional
>             Fix For: 5.next
> Running com.hp.mwtests.ts.jts.orbspecific.local.performance.Performance2 on JacORB with about 500000 transactions results in an OOM error because surefire keeps in logs in memory until the test has finished.
> In this particular test jacorb logs  messages at INFO level for each transaction resulting in excessive memory requirements. We can't make the heap too large because the default JVM is 32 bit. However, we could fix it by reducing the jacorb log level to WARN.

This message was sent by Atlassian JIRA

More information about the jbossts-issues mailing list