If you ever upgrade from Red Hat Enterprise Linux version 5 to 6, this is one 
of the things to watch out for: the max number of child processes per user is a 
lot lower by default. 

Sent from my iPhone

> On 2016/06/13, at 6:59, Matt Sicker <boa...@gmail.com> wrote:
> 
> I don't think I've ever come across weird out of memory errors like that 
> before, so that's some rather useful advice. :)
> 
>> On 12 June 2016 at 16:24, Ralph Goers <ralph.go...@dslextreme.com> wrote:
>> It had just started. Notice that this isn’t an out of heap space.  In my 
>> experience  "Unable to create native thread” usually means the server has 
>> exceeded the max number of processes.
>> 
>> Ralph
>> 
>>> On Jun 12, 2016, at 1:13 PM, Matt Sicker <boa...@gmail.com> wrote:
>>> 
>>> Huh, that's a new one. Out of memory!
>>> 
>>> I built this locally and it worked fine.
>>> 
>>>> On 12 June 2016 at 13:46, Apache Jenkins Server 
>>>> <jenk...@builds.apache.org> wrote:
>>>> See <https://builds.apache.org/job/Log4j%202.x/2026/changes>
>>>> 
>>>> Changes:
>>>> 
>>>> [boards] Suppress pointless warning messages
>>>> 
>>>> ------------------------------------------
>>>> Started by an SCM change
>>>> [EnvInject] - Loading node environment variables.
>>>> Building remotely on ubuntu-1 (docker Ubuntu ubuntu yahoo-not-h2 ubuntu1) 
>>>> in workspace <https://builds.apache.org/job/Log4j%202.x/ws/>
>>>>  > git rev-parse --is-inside-work-tree # timeout=10
>>>> Fetching changes from the remote Git repository
>>>>  > git config remote.origin.url 
>>>> https://git-wip-us.apache.org/repos/asf/logging-log4j2.git # timeout=10
>>>> Fetching upstream changes from 
>>>> https://git-wip-us.apache.org/repos/asf/logging-log4j2.git
>>>>  > git --version # timeout=10
>>>>  > git -c core.askpass=true fetch --tags --progress 
>>>> https://git-wip-us.apache.org/repos/asf/logging-log4j2.git 
>>>> +refs/heads/*:refs/remotes/origin/*
>>>>  > git rev-parse refs/remotes/origin/master^{commit} # timeout=10
>>>>  > git rev-parse refs/remotes/origin/origin/master^{commit} # timeout=10
>>>> Checking out Revision 021da77c9b1615b63f9b3d2b89ab7f78e705a9df 
>>>> (refs/remotes/origin/master)
>>>>  > git config core.sparsecheckout # timeout=10
>>>>  > git checkout -f 021da77c9b1615b63f9b3d2b89ab7f78e705a9df
>>>>  > git rev-list 33162b9c292f119a944e8ca42f6698996c3b670b # timeout=10
>>>> [EnvInject] - Executing scripts and injecting environment variables after 
>>>> the SCM step.
>>>> [EnvInject] - Injecting as environment variables the properties content
>>>> LANG=en_US.UTF-8
>>>> 
>>>> [EnvInject] - Variables injected successfully.
>>>> Parsing POMs
>>>> Modules changed, recalculating dependency graph
>>>> Established TCP socket on 49503
>>>> maven32-agent.jar already up to date
>>>> maven32-interceptor.jar already up to date
>>>> maven3-interceptor-commons.jar already up to date
>>>> [Log4j 2.x] $ 
>>>> /home/jenkins/jenkins-slave/tools/hudson.model.JDK/jdk-1.7u51/bin/java 
>>>> -Xmx2g -Xms256m -XX:MaxPermSize=512m -cp 
>>>> /home/jenkins/jenkins-slave/maven32-agent.jar:/home/jenkins/jenkins-slave/tools/hudson.tasks.Maven_MavenInstallation/maven-3.2.1/boot/plexus-classworlds-2.5.1.jar:/home/jenkins/jenkins-slave/tools/hudson.tasks.Maven_MavenInstallation/maven-3.2.1/conf/logging
>>>>  jenkins.maven3.agent.Maven32Main 
>>>> /home/jenkins/jenkins-slave/tools/hudson.tasks.Maven_MavenInstallation/maven-3.2.1
>>>>  /home/jenkins/jenkins-slave/slave.jar 
>>>> /home/jenkins/jenkins-slave/maven32-interceptor.jar 
>>>> /home/jenkins/jenkins-slave/maven3-interceptor-commons.jar 49503
>>>> ERROR: Failed to parse POMs
>>>> java.io.IOException: Remote call on ubuntu-1 failed
>>>>         at hudson.remoting.Channel.call(Channel.java:789)
>>>>         at hudson.Launcher$RemoteLauncher.launch(Launcher.java:928)
>>>>         at hudson.Launcher$ProcStarter.start(Launcher.java:381)
>>>>         at 
>>>> hudson.maven.AbstractMavenProcessFactory.newProcess(AbstractMavenProcessFactory.java:281)
>>>>         at hudson.maven.ProcessCache.get(ProcessCache.java:236)
>>>>         at 
>>>> hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:778)
>>>>         at 
>>>> hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:534)
>>>>         at hudson.model.Run.execute(Run.java:1738)
>>>>         at 
>>>> hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:531)
>>>>         at 
>>>> hudson.model.ResourceController.execute(ResourceController.java:98)
>>>>         at hudson.model.Executor.run(Executor.java:410)
>>>> Caused by: java.lang.OutOfMemoryError: unable to create new native thread
>>>>         at java.lang.Thread.start0(Native Method)
>>>>         at java.lang.Thread.start(Thread.java:714)
>>>>         at hudson.Proc$LocalProc.<init>(Proc.java:252)
>>>>         at hudson.Proc$LocalProc.<init>(Proc.java:216)
>>>>         at hudson.Launcher$LocalLauncher.launch(Launcher.java:815)
>>>>         at hudson.Launcher$ProcStarter.start(Launcher.java:381)
>>>>         at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:1148)
>>>>         at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:1113)
>>>>         at hudson.remoting.UserRequest.perform(UserRequest.java:120)
>>>>         at hudson.remoting.UserRequest.perform(UserRequest.java:48)
>>>>         at hudson.remoting.Request$2.run(Request.java:326)
>>>>         at 
>>>> hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68)
>>>>         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)
>>>>         at ......remote call to ubuntu-1(Native Method)
>>>>         at 
>>>> hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1416)
>>>>         at hudson.remoting.UserResponse.retrieve(UserRequest.java:220)
>>>>         at hudson.remoting.Channel.call(Channel.java:781)
>>>>         ... 10 more
>>>> 
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
>>>> For additional commands, e-mail: log4j-dev-h...@logging.apache.org
>>> 
>>> 
>>> 
>>> -- 
>>> Matt Sicker <boa...@gmail.com>
> 
> 
> 
> -- 
> Matt Sicker <boa...@gmail.com>

Reply via email to