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

Michael Musgrove (JIRA) issues at jboss.org
Tue Aug 18 10:06:28 EDT 2015

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

Michael Musgrove commented on JBTM-2234:

./build.sh -f ArjunaJTS/jts/pom.xml -Dtest=com.hp.mwtests.ts.jts.orbspecific.local.performance.Performance2

but you don't need to duplicate it since the issue is that the logger stores the messages in memory and only dumps them to a file at the end of the test. So you just need to reduce the JacORB logging level from INFO to just WARN and to verify the fix check that the log file does not contain any INFO messages.

> 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