Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
badges earned

Your Points Tracker
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

java.lang.RuntimeException: javax.servlet.ServletException: java.lang.NullPointerException Edited


I've installed JIRA 8.14.0 (same error on 8.13.0) on Ubuntu 16.04 Docker container with SQL server (mssql/server:2019-latest).

And on the last step when configuring E-mail at /secure/SetupMailNotifications!default.jspa (by choosing Later), JIRA crashes with the following error:


Sorry, we had some technical problems during your last operation.

Log's referral number: b3b1076c-3369-47db-8aa0-09d724bb2400

Referer URL: http://localhost:8080/secure/SetupMailNotifications!default.jspa

java.lang.RuntimeException: javax.servlet.ServletException: java.lang.NullPointerException
java.lang.RuntimeException: javax.servlet.ServletException: java.lang.NullPointerException
	at com.atlassian.web.servlet.plugin.DynamicAuthorizationServletForwarder.forward( [?:?]
	at com.atlassian.web.servlet.plugin.DynamicAuthorizationServletForwarder.forwardSafely( [?:?]
	at com.atlassian.web.servlet.plugin.SanitizingServletForwarder.forwardSafely( [?:?]
	at com.atlassian.web.servlet.plugin.RememberingServletForwarder.forwardSafely( [?:?]
	at com.atlassian.web.servlet.plugin.ResolvingServletForwarder.forwardSafely( [?:?]
	at com.atlassian.web.servlet.plugin.request.RedirectInterceptingResponse.lambda$null$0( [?:?]
	at [?:1.8.0_202]
	at com.atlassian.web.servlet.plugin.request.RedirectInterceptingResponse.lambda$forward$1( [?:?]
	at java.util.Optional.flatMap( [?:1.8.0_202]
	at com.atlassian.web.servlet.plugin.request.RedirectInterceptingResponse.forward( [?:?]
	at com.atlassian.web.servlet.plugin.request.RedirectInterceptingResponse.sendRedirect( [?:?]
	at javax.servlet.http.HttpServletResponseWrapper.sendRedirect( [servlet-api.jar:?]
	at com.atlassian.core.filters.HeaderSanitisingResponseWrapper.sendRedirect( [atlassian-core-7.0.2.jar:?]
	at com.atlassian.jira.web.action.JiraWebActionSupport.forceRedirect( [jira-api-8.13.0.jar:?]
	at com.atlassian.jira.web.action.JiraWebActionSupport.getRedirect( [jira-api-8.13.0.jar:?]
	at com.atlassian.jira.web.action.JiraWebActionSupport.getRedirect( [jira-api-8.13.0.jar:?]
	at com.atlassian.jira.web.action.setup.SetupComplete.doExecute( [classes/:?]
	at webwork.action.ActionSupport.execute( [webwork-1.4-atlassian-30.jar:?]
	at com.atlassian.jira.action.JiraActionSupport.execute( [jira-api-8.13.0.jar:?]
	at webwork.interceptor.DefaultInterceptorChain.proceed( [webwork-1.4-atlassian-30.jar:?]
	at webwork.interceptor.NestedInterceptorChain.proceed( [webwork-1.4-atlassian-30.jar:?]
	at webwork.interceptor.ChainedInterceptor.intercept( [webwork-1.4-atlassian-30.jar:?]
	at webwork.interceptor.DefaultInterceptorChain.proceed( [webwork-1.4-atlassian-30.jar:?]
	at webwork.dispatcher.GenericDispatcher.executeAction( [webwork-1.4-atlassian-30.jar:?]
	at webwork.dispatcher.GenericDispatcher.executeAction( [webwork-1.4-atlassian-30.jar:?]
	at com.atlassian.jira.web.dispatcher.JiraWebworkActionDispatcher.service( [classes/:?]
	at javax.servlet.http.HttpServlet.service( [servlet-api.jar:?]
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter( [catalina.jar:8.5.57]
	at org.apache.catalina.core.ApplicationFilterChain.doFilter( [catalina.jar:8.5.57]
	at org.apache.tomcat.websocket.server.WsFilter.doFilter( [tomcat-websocket.jar:8.5.57]
	at ...


Log file: /var/atlassian/application-data/jira/log/atlassian-jira.log

80-exec-23 WARN [c.a.j.w.action.setup.SetupComplete] Unable to automatically login after setup complete: sessionStorage is nul
80-exec-23 ERROR [o.a.c.c.C.[.[localhost].[/].[action]] Servlet.service() for servlet [action] threw exception


Any ideas?


Screenshot 2021-01-14 at 19.28.34.png

1 answer

1 accepted

0 votes
Answer accepted

The error happened, because the database was not correctly configured which happened by skipping some of the steps.

To do that, you need to hit the home page for the first time before hitting any configuration pages. Basically the homepage redirects to /secure/SetupMode!default.jspa and /secure/SetupDatabase!default.jspa pages which are configuring the database for the first time.

If you hit the following error at /secure/SetupAdminAccount!default.jspa:

Cannot add user, all the user directories are read-only.

It's basically the same cause. You need to hit the home page first.

To summarize, to configure JIRA via wizard, here are the steps from the scripting perspective:

  1. Hit homepage via GET request (e.g. http://localhost:8080) and follow the redirects (such as /secure/SetupMode!default.jspa and /secure/SetupDatabase!default.jspa).
  2. Set up application properties via POST at /secure/SetupApplicationProperties.jspa (regular page: /secure/SetupApplicationProperties!default.jspa).
  3. (Optionally) Validate license via POST at /secure/SetupLicense!validateLicense.jspa
  4. Setup license via POST at /secure/SetupLicense.jspa (regular page: /secure/SetupLicense!default.jspa).
  5. Setup account via POST at /secure/SetupAdminAccount.jspa (regular page: /secure/SetupAdminAccount!default.jspa).
  6. Setup mail notification at /secure/SetupMailNotifications.jspa (regular page: /secure/SetupMailNotifications!default.jspa)
  7. To confirm, hit /rest/api/2/dashboard (response code 200 - JIRA configured, 500 - not configured, 503 - starting up or not configured).

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Jira Service Management

JSM June Challenge #2: Share how your business teams became ITSM rockstars

For JSM June Challenge #2, share how your non-technical teams like HR, legal, marketing, finance, and beyond started using Jira Service Management! Tell us: Did they ask to start using it or...

226 views 7 7
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you