[JENKINS-56843] Active Directory Health Status non-functional, NPE in logs

Fresh Jenkins install, default Active Directory configuration.  The Active Directory plugin is basically functional: it does successfully authenticate users against their domain credentials.

However, the Health Status page at /ad-health/ does not list a server, Submit Query does nothing, and no information is available in either table.  The following exception is seen in jenkins.err.log:

Apr 01, 2019 4:10:32 PM jenkins.util.ProgressiveRendering$1 run

WARNING: failed to compute /ad-health/

java.lang.NullPointerException

	at hudson.plugins.active_directory.ActiveDirectoryStatus$1.compute(ActiveDirectoryStatus.java:101)

	at jenkins.util.ProgressiveRendering$1.run(ProgressiveRendering.java:122)

	at jenkins.security.ImpersonatingScheduledExecutorService$1.run(ImpersonatingScheduledExecutorService.java:58)

	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)

	at java.util.concurrent.FutureTask.run(FutureTask.java:266)

	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)

	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)

	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)

	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)

	at java.lang.Thread.run(Thread.java:748)

 

---
Originally reported by sumdumgai, imported from: Active Directory Health Status non-functional, NPE in logs

• assignee: fbelzunc
  
• status: Open
  
• priority: Major
  
• component(s): active-directory-plugin
  
• resolution: Unresolved
  
• votes: 1
  
• watchers: 3
  
• imported: 2025-12-07
  

Raw content of original issue

Fresh Jenkins install, default Active Directory configuration.  The Active Directory plugin is basically functional: it does successfully authenticate users against their domain credentials.


However, the Health Status page at /ad-health/ does not list a server, Submit Query does nothing, and no information is available in either table.  The following exception is seen in jenkins.err.log:



Apr 01, 2019 4:10:32 PM jenkins.util.ProgressiveRendering$1 run

WARNING: failed to compute /ad-health/

java.lang.NullPointerException

	at hudson.plugins.active_directory.ActiveDirectoryStatus$1.compute(ActiveDirectoryStatus.java:101)

	at jenkins.util.ProgressiveRendering$1.run(ProgressiveRendering.java:122)

	at jenkins.security.ImpersonatingScheduledExecutorService$1.run(ImpersonatingScheduledExecutorService.java:58)

	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)

	at java.util.concurrent.FutureTask.run(FutureTask.java:266)

	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)

	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)

	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)

	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)

	at java.lang.Thread.run(Thread.java:748)





 

environment

```
Jenkins 2.164.1

Active Directory plugin 2.13

Windows Server 2016 x64

Server JRE 1.8u202 x64
```

Inspect hudson.plugins.active_directory.ActiveDirectoryStatus, especially the compute method at ActiveDirectoryStatus.java:101, and reproduce the /ad-health/ failure with the default Active Directory configuration described here. Done means the health page lists the server, Submit Query produces information in both tables, and the NullPointerException no longer appears in the logs.

Written by the indexing model from the issue text.