Hi Harald,
thanx for clearification.
So to set the PermGen space I'll need to add it as a maven opts
parameter then?
Regards, Achim
Am 11.11.2011 22:29, schrieb Harald Wellmann:
Hi Achim,
if you use the Pax Runner Container, vmOptions() will be propagated to
the spawned VM.
With the Native Container, vmOptions() has no effect, since the
container is running in the same VM, and you can't change the heap
limits at runtime.
No idea why your test is hanging...
Hope that helps,
Harald
Am 11.11.2011 22:21, schrieb Achim Nierbeck:
Hi All
it's me again, bugging with itests of Pax Web again :)
Certain tests seem to fail due to the following Error:
ERROR: Bundle org.ops4j.pax.exam.extender.service [3] EventDispatcher:
Error during dispatch. (java.lang.OutOfMemoryError: PermGen space)
I found the following option
vmOptions("-Xmx1G", "-XX:MaxPermSize=128M")
but now it's starting to be funny cause after adding this option
the itests stalls at the second test method and just holds without any
reactions.
Now the question, is it the right way of setting the max perm size for
PaxExam 2
and if so, why does the integration test just hang there without doing
anything.
Thanx and regards, Achim
_______________________________________________
general mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/general
--
--
*Achim Nierbeck*
Apache Karaf<http://karaf.apache.org/> Committer& PMC
OPS4J Pax Web<http://wiki.ops4j.org/display/paxweb/Pax+Web/> Committer&
Project Lead
blog<http://notizblog.nierbeck.de/>
_______________________________________________
general mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/general
