Jenkins fails to save configuration due to NPE

Article ID:360055099332
1 minute readKnowledge base

Issue

  • Jenkins fails to save Configure System due to Null Pointer Exception (NPE)

Saving the Manage Jenkins -> Configure System fails the following stack trace:

22020-12-31 11:43:02.580+0000 [id=20] WARNING o.e.j.s.h.ContextHandler$Context#log: Error while serving https://jenkins.example.com:8080/configSubmit
net.sf.json.JSONException: null object
    at net.sf.json.JSONObject.verifyIsNull(JSONObject.java:2688)
    at net.sf.json.JSONObject.get(JSONObject.java:1905)
    at com.thed.zephyr.jenkins.reporter.ZfjDescriptor.configure(ZfjDescriptor.java:72)
    at jenkins.model.Jenkins.configureDescriptor(Jenkins.java:3846)
    at jenkins.model.Jenkins.doConfigSubmit(Jenkins.java:3810)
    at java.lang.invoke.MethodHandle.invokeWithArguments(MethodHandle.java:627)
    at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:396)
    at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:408)
    at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:212)
    at org.kohsuke.stapler.SelectionInterceptedFunction$Adapter.invoke(SelectionInterceptedFunction.java:36)
    at org.kohsuke.stapler.verb.HttpVerbInterceptor.invoke(HttpVerbInterceptor.java:48)
    at org.kohsuke.stapler.SelectionInterceptedFunction.bindAndInvoke(SelectionInterceptedFunction.java:26)
    at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:145)
    at org.kohsuke.stapler.MetaClass$11.doDispatch(MetaClass.java:536)
    at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58)
    at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:766)
    at org.kohsuke.stapler.Stapler.invoke(Stapler.java:898)
    at org.kohsuke.stapler.Stapler.invoke(Stapler.java:694)
    at org.kohsuke.stapler.Stapler.service(Stapler.java:240)

Resolution

Disable or Uninstall Zephyr for Jira Test Management Plugin

This article is part of our Knowledge Base and is provided for guidance-based purposes only. The solutions or workarounds described here are not officially supported by CloudBees and may not be applicable in all environments. Use at your own discretion, and test changes in a safe environment before applying them to production systems.