Ok the tag below of course solves it ... or maybe just postpones it (I haven't
investigated whether there is a real memory leak in our tests or our application or in
seam):
| <testng ...
| <jvmarg value="-Xmx256m"/>
| </testng>
|
Cheers,
Tobias
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4099401#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...