[JIRA] (JENKINS-61343) EC2 alive slaves monitor thread died unexpectedly

[raihaan.shouh...@autodesk.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Raihaan Shouhell closed an issue as Duplicate  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-61343  
 
 
  EC2 alive slaves monitor thread died unexpectedly   
 

  
 
 
 
 

 
Change By: 
 Raihaan Shouhell  
 
 
Status: 
 Open Closed  
 
 
Resolution: 
 Duplicate  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204935.1583407223000.18044.1587953700468%40Atlassian.JIRA.

[JIRA] (JENKINS-61343) EC2 alive slaves monitor thread died unexpectedly

[bochenski.kuba+jenk...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jakub Bochenski created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-61343  
 
 
  EC2 alive slaves monitor thread died unexpectedly   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 FABRIZIO MANFREDI  
 
 
Components: 
 ec2-plugin  
 
 
Created: 
 2020-03-05 11:20  
 
 
Environment: 
 Jenkins ver. 2.204.2  ec2 plugin 1.49.1  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Jakub Bochenski  
 

  
 
 
 
 

 
 I'm seeing this in the logs every 10 minutes.  The monitor thread starts and then dies. 10 minutes later it repeats. 

 
Mar 05, 2020 10:54:35 AM INFO hudson.model.AsyncPeriodicWork lambda$doRun$0

Started EC2 alive slaves monitor

Mar 05, 2020 10:54:35 AM SEVERE hudson.init.impl.InstallUncaughtExceptionHandler$DefaultUncaughtExceptionHandler uncaughtException

A thread (EC2 alive slaves monitor thread/10354) died unexpectedly due to an uncaught exception, this may leave your Jenkins in a bad way and is usually indicative of a bug in the code.
java.lang.NullPointerException
	at hudson.plugins.ec2.util.MinimumInstanceChecker.lambda$countQueueItemsForAgentTemplate$8(MinimumInstanceChecker.java:67)
	at java.util.stream.ReferencePipeline$2$1.accept(ReferencePipeline.java:174)
	at java.util.stream.ReferencePipeline$3$1.accept(ReferencePipeline.java:193)
	at java.util.ArrayList$ArrayListSpliterator.forEachRemaining(ArrayList.java:1382)
	at java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:482)
	at java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:472)
	at java.util.stream.ReduceOps$ReduceOp.evaluateSequential(ReduceOps.java:708)
	at java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234)
	at java.util.stream.LongPipeline.reduce(LongPipe