For the purposes of completeness, a follow-up.
I have overcome the problem. It seems the MAVEN_OPTS environment variable
set within Windows is not read, or mine is incorrect set.
If I Configure the project, and click "Advanced" under Build I can add
"-XX:MaxPermSize=256m" to MAVEN_OPTS. This resolved the issue for me.
On 19 May 2014 16:05, James Green <james.mk.gr...@gmail.com> wrote:
> Right - server is now 1.563 and I restarted the Jenkins service. I still
> get PermGen errors.
>
> Time to file a bug..?
>
> Build output includes:
>
> Parsing POMs
> Modules changed, recalculating dependency graph
> maven31-agent.jar already up to date
> maven31-interceptor.jar already up to date
> maven3-interceptor-commons.jar already up to date
> [portal-selenium] $ "C:\Program Files\Java\jdk1.7.0_55/bin/java"
> -Dmaven.test.failure.ignore=false -cp
> "c:\Jenkins\maven31-agent.jar;C:\Program
> Files\apache-maven\boot\plexus-classworlds-2.5.1.jar;C:\Program
> Files\apache-maven/conf/logging" jenkins.maven3.agent.Maven31Main "C:\Program
> Files\apache-maven" C:\Jenkins\slave.jar c:\Jenkins\maven31-interceptor.jar
> c:\Jenkins\maven3-interceptor-commons.jar 54261
> <===[JENKINS REMOTING CAPACITY]===>channel started
> Executing Maven: -B -f c:\Jenkins\workspace\portal-selenium\pom.xml clean
> install
> [INFO] Scanning for projects...
> [INFO]
> [INFO] Using the builder
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder
> with a thread count of 1
>
> ...
>
> [INFO] Initializing ProtocolHandler ["http-bio-8080"]
> [INFO] Starting service Tomcat
> [INFO] Starting Servlet Engine: Apache Tomcat/7.0.47
> [INFO] No Spring WebApplicationInitializer types detected on classpath
> [INFO] Initializing Spring root WebApplicationContext
>
> ...
>
> [INFO] WSSERVLET14: JAX-WS servlet initializing
> [INFO] No Spring WebApplicationInitializer types detected on classpath
> [INFO] Initializing Spring root WebApplicationContext
> 15:45:27,036 WARN
> org.springframework.core.io.support.PropertiesLoaderSupport:181
> loadProperties() - Could not load properties from URL
> [file:${portal.properties.file}]: ${portal.properties.file} (The system
> cannot find the file specified)
> Have now configured log4j using log4j.properties
>
> ...
>
> Exception in thread
> "org.springframework.scheduling.quartz.SchedulerFactoryBean#0_Worker-4"
> Exception in thread
> "org.springframework.scheduling.quartz.SchedulerFactoryBean#0_Worker-3"
> 15:46:42,942 INFO quartz.ReadNotificationScheduler:39 executeInternal() -
> Executing schedule
> Exception in thread
> "org.springframework.scheduling.quartz.SchedulerFactoryBean#0_Worker-2"
> Exception in thread
> "org.springframework.scheduling.quartz.SchedulerFactoryBean#0_Worker-8"
> Exception in thread
> "org.springframework.scheduling.quartz.SchedulerFactoryBean#0_Worker-10"
> [ERROR] Unexpected error in channel channel
> java.lang.OutOfMemoryError: PermGen space[ERROR] A child container failed
> during startjava.lang.InterruptedException
> at java.util.concurrent.FutureTask.awaitDone(FutureTask.java:400)
> at java.util.concurrent.FutureTask.get(FutureTask.java:187)
> at
> org.apache.catalina.core.ContainerBase.startInternal(ContainerBase.java:1123)
> at
> org.apache.catalina.core.StandardEngine.startInternal(StandardEngine.java:302)
> at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
> at
> org.apache.catalina.core.StandardService.startInternal(StandardService.java:443)
> at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
> at
> org.apache.catalina.core.StandardServer.startInternal(StandardServer.java:732)
> at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
> at org.apache.catalina.startup.Tomcat.start(Tomcat.java:341)
> at
> org.apache.tomcat.maven.plugin.tomcat7.run.AbstractRunMojo.startContainer(AbstractRunMojo.java:1238)
> at
> org.apache.tomcat.maven.plugin.tomcat7.run.AbstractRunMojo.execute(AbstractRunMojo.java:592)
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:133)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:108)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:76)
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:116)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:361)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:155)
> at
> org.jvnet.hudson.maven3.launcher.Maven31Launcher.main(Maven31Launcher.java:132)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launchStandard(Launcher.java:330)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:238)
> at jenkins.maven3.agent.Maven31Main.launch(Maven31Main.java:181)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at hudson.maven.Maven3Builder.call(Maven3Builder.java:134)
> at hudson.maven.Maven3Builder.call(Maven3Builder.java:69)
> at hudson.remoting.UserRequest.perform(UserRequest.java:118)
> at hudson.remoting.UserRequest.perform(UserRequest.java:48)
> at hudson.remoting.Request$2.run(Request.java:328)
> at
> hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
> at java.util.concurrent.FutureTask.run(FutureTask.java:262)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:745)
> channel stopped
>
> Exception: java.lang.OutOfMemoryError thrown from the
> UncaughtExceptionHandler in thread
> "org.springframework.scheduling.quartz.SchedulerFactoryBean#0_Worker-9"
>
>
> None of which occurs when I log in to that machine and run the same
> commands myself. Some help on this would be appreciated.
>
> Thanks,
>
> James
>
>
>
> On 8 May 2014 13:43, <matthew.web...@diamond.ac.uk> wrote:
>
>> There are memory issues in 1.560/1.561/1.562 – see
>> https://issues.jenkins-ci.org/browse/JENKINS-22734
>>
>>
>>
>> *From:* James Green [mailto:james.mk.gr...@gmail.com]
>> *Sent:* 08 May 2014 12:13
>> *To:* jenkinsci-users@googlegroups.com
>> *Subject:* OOM: Permgen issues only when run as a Windows Service
>>
>>
>>
>> I've got a Windows 8 Pro machine connected to our Jenkins 1.562 instance
>> as a slave. The slave runs as a windows service.
>>
>>
>>
>> I have set MAVEN_OPTS as a system property variable. If I open an
>> administrative cmd prompt and type 'set' included is the following:
>>
>>
>>
>> MAVEN_OPTS=-Xms1024m -Xmx1024m -XX:NewSize=256m -XX:MaxNewSize=356m
>> -XX:PermSize
>>
>> =1024m -XX:MaxPermSize=2048m
>>
>>
>>
>> If I check out a maven 3 project and clean/install it myself it works.
>> But the Jenkins service fails it, with OOM: Permgen Space.
>>
>>
>>
>> Any ideas?
>>
>>
>>
>> Thanks,
>>
>>
>>
>> James
>>
>>
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Jenkins Users" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to jenkinsci-users+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Jenkins Users" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to jenkinsci-users+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
