[
https://issues.jboss.org/browse/JBTM-2234?page=com.atlassian.jira.plugin....
]
Tom Jenkinson commented on JBTM-2234:
-------------------------------------
Hi Mike,
Good find! For performance tests I think you are right and we should set all logging to
WARN for those type of tests to ensure log writing isn't factoring into the
benchmark.
Thanks,
Tom
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
Security Level: Public(Everyone can see)
Components: Performance Testing
Affects Versions: 5.0.2
Environment: JTS testing
Reporter: Michael Musgrove
Assignee: Michael Musgrove
Priority: Optional
Fix For: 5.0.4
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.2.6#6264)