> On Jan 27, 2020, at 10:52 PM, Allen Wittenauer 
> <a...@effectivemachines.com.INVALID> wrote:
> 
> 
> 
>> On Jan 27, 2020, at 6:37 PM, Andriy Redko <drr...@gmail.com> wrote:
>> 
>> Thanks a lot for looking into it. From the CXF perspective, I have seen that 
>> many CXF builds have been aborted
>> because of the connection with master is lost (don't have exact builds to 
>> point since we keep only last 3),
>> that could probably explain the hanging builds. 
> 
> 
>       This is almost always because whatever is running on the two executors 
> have suffocated the system resources. This ends up starving the Jenkins 
> slave.jar, thus causing the disconnect.  (It's extremely important to 
> understand that Jenkins' implementation here is sort of brain dead: the 
> slave.jar runs as the SAME USER as the jobs being executed.  This is an 
> idiotic implementation, but it is what it is.)

this is correct re: starving the slave.jar. It’s entirely likely the CXF jobs 
are the ones causing the disconnect based on available information. 

Allen, can you elaborate on what a “proper” implementation is?  As far as I 
know, this is baked into jenkins. We could raise process limits for the jenkins 
user, but these situations only tend to arise when a build has gone off the 
rails.


-Chris

Reply via email to