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

[Tom Jenkinson (JIRA)]

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

Tom Jenkinson commented on JBTM-2234:
-------------------------------------

I had a look at this too and can't seem to influence the JacORB logger. Is it possible its not reading those settings because the logger is not set? I tried to add:
jacorb.log.loggerFactory=org.jboss.util.Log4jLoggerFactory

But that didn't seem to make a difference - maybe we don't have log4j in the classpath so some default not controllable logger is being used?

> 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
(v6.3.15#6346)