It turns out that there was already a surefire plugin config on the test module which was setting some memory settings, but if i removed them it all started working fine. I've committed that change and kicked off a Hudson build to see if that still works, but if these settings break it for anyone else just say and we can try to find if there are settings which work for all of us.
...ant On Mon, May 9, 2011 at 6:26 PM, ant elder <ant.el...@gmail.com> wrote: > Thats a good point, i shall go play around with surefire config in the > tuscany-compliance-test-java-caa to see if that helps. > > ...ant > > On Mon, May 9, 2011 at 4:45 PM, Raymond Feng <enjoyj...@gmail.com> wrote: >> The maven option won't help as surefire plugin forks the jvm. Try to >> configure the surefire plugin. >> >> Raymond Feng >> Sent from my iPhone >> >> On May 9, 2011, at 4:41 AM, ant elder <antel...@apache.org> wrote: >> >>> On Mon, May 9, 2011 at 11:51 AM, Simon Laws <simonsl...@googlemail.com> >>> wrote: >>>> On Mon, May 9, 2011 at 11:47 AM, ant elder <ant.el...@gmail.com> wrote: >>>>> Another issue i have getting the build running on a new machine is >>>>> that the Java CAA compliance test suite always fails with an >>>>> OutOfMemoryError. It doesn't matter how I run that, in a full build >>>>> the suite on its own, or what memory setting i use it always ends up >>>>> getting the following exception in most of the tests: >>>>> >>>>> java.lang.OutOfMemoryError: unable to create new native thread >>>>> at java.lang.Thread.start0(Native Method) >>>>> at java.lang.Thread.start(Thread.java:640) >>>>> at java.util.Timer.<init>(Timer.java:154) >>>>> at java.util.Timer.<init>(Timer.java:122) >>>>> at >>>>> org.mortbay.jetty.servlet.HashSessionManager.doStart(HashSessionManager.java:71) >>>>> at >>>>> org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50) >>>>> at >>>>> org.mortbay.jetty.servlet.SessionHandler.doStart(SessionHandler.java:115) >>>>> at >>>>> org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50) >>>>> at >>>>> org.mortbay.jetty.handler.HandlerWrapper.doStart(HandlerWrapper.java:130) >>>>> at >>>>> org.mortbay.jetty.handler.ContextHandler.startContext(ContextHandler.java:537) >>>>> at >>>>> org.mortbay.jetty.handler.ContextHandler.doStart(ContextHandler.java:517) >>>>> at >>>>> org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50) >>>>> at >>>>> org.mortbay.jetty.handler.HandlerWrapper.doStart(HandlerWrapper.java:130) >>>>> at org.mortbay.jetty.Server.doStart(Server.java:224) >>>>> at >>>>> org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50) >>>>> at >>>>> org.apache.tuscany.sca.http.jetty.JettyServer.addServletMapping(JettyServer.java:297) >>>>> at >>>>> org.apache.tuscany.sca.http.jetty.JettyServer.addServletMapping(JettyServer.java:225) >>>>> at >>>>> org.apache.tuscany.sca.host.http.DefaultServletHostExtensionPoint$LazyServletHost.addServletMapping(DefaultServletHostExte >>>>> nsionPoint.java:124) >>>>> at >>>>> org.apache.tuscany.sca.binding.ws.axis2.provider.Axis2ServiceBindingProvider.start(Axis2ServiceBindingProvider.java:191) >>>>> at >>>>> org.apache.tuscany.sca.core.assembly.impl.CompositeActivatorImpl$2.run(CompositeActivatorImpl.java:552) >>>>> at java.security.AccessController.doPrivileged(Native Method) >>>>> at >>>>> org.apache.tuscany.sca.core.assembly.impl.CompositeActivatorImpl.startEndpoint(CompositeActivatorImpl.java:550) >>>>> at >>>>> org.apache.tuscany.sca.core.assembly.impl.CompositeActivatorImpl.start(CompositeActivatorImpl.java:422) >>>>> at >>>>> org.apache.tuscany.sca.core.assembly.impl.CompositeActivatorImpl.start(CompositeActivatorImpl.java:345) >>>>> at >>>>> org.apache.tuscany.sca.node.impl.NodeImpl.start(NodeImpl.java:162) >>>>> at >>>>> org.apache.tuscany.sca.otest.TuscanyRuntimeBridge.startContribution(TuscanyRuntimeBridge.java:80) >>>>> at >>>>> client.BaseJAXWSTestRunner.startContribution(BaseJAXWSTestRunner.java:235) >>>>> at client.BaseJAXWSTestRunner.setUp(BaseJAXWSTestRunner.java:144) >>>>> at sun.reflect.GeneratedMethodAccessor19.invoke(Unknown Source) >>>>> at >>>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) >>>>> at java.lang.reflect.Method.invoke(Method.java:597) >>>>> at >>>>> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44) >>>>> at >>>>> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15) >>>>> at >>>>> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41) >>>>> at >>>>> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:27) >>>>> at >>>>> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:31) >>>>> at >>>>> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:73) >>>>> at >>>>> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:46) >>>>> at >>>>> org.junit.runners.ParentRunner.runChildren(ParentRunner.java:180) >>>>> >>>>> Does anyone have any ideas on how to fix that? >>>>> >>>>> I have this in MAVEN_OPTs: -Xmx1024m -Xms1024m -XX:MaxPermSize=512m >>>>> >>>>> For now I've stopped trying to run in and taken the test suite out of >>>>> my local build >>>>> >>>>> ...ant >>>>> >>>>> >>>>> ...ant >>>>> >>>> >>>> Any differences between the new and old machine that might affect this? >>>> >>> >>> Yes lots - 64 bit vs 32 bit, newer OS, newer Maven, newer Java, etc, >>> etc - so its hard to know where to start. >>> >>> ...ant >> >
