Am 11.11.2011 23:48, schrieb Achim Nierbeck:
OK, this is starting to be real strange right now.
Maybe it's more because there are quite some tests available.
But around 5 of them are still failing because of MaxPerm size (set to
512M)
either the configuration through the argline param
doesn't work or it's just consuming to much.
Do you know if each of the test is forked in a process of its own, or do
all
tests share the same instance. If so this could be a possible reason
though I wouldn't know how to change that :(
Maven Surefire has a forkMode option with default value "once". I.e.
Maven forks one VM before running the entire test suite in it.
You can use
<forkMode>always</forkMode>
to fork per test class.
See
http://maven.apache.org/plugins/maven-surefire-plugin/test-mojo.html#forkMode
With this setting, you should be able to run your tests.
But I suspect we are not currently addressing the real problem. PermGen
issues in web containers are usually a symptom of classloader leaks
where the container fails to release a reference to the classloader of
an application that has been undeployed.
With Pax Web as a dual web + OSGi container, the leak might also be
caused by the OSGi framework failing to release classloaders of
uninstalled bundles.
Sounds like a case for a heap dump analysis - I'd recommend Eclipse
Memory Analyzer.
Best regards,
Harald
_______________________________________________
general mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/general
