Trying to login to jira, getting null pointer exception

Our JIRA-Software runs with postgresql DB, version 9.4. The Databse-Server runs in a virtual Debian-machine (Hyper-V) which is installed on our domain contoller (Windows Server 2012 R2). Also JIRA is installed on the DC.  Everything worked well, but after our DC received new windows updates the JIRA Login fails. The VM and postgresql are running. If someone tries to Login then an error message appers in the browser-window:

JIRA — Internal Server Error

Error reference: 44a95f7d-79b9-437a-acb9-260d73e85eed

Unable to render full error details at this time. Please consult the error logs for more information.

 

The JIRA-log:

2017-08-14 11:35:46,016 http-nio-8080-exec-17 ERROR      [o.a.c.c.C.[.[.[.[jsp.secure.errors_jsp]] Servlet.service() for servlet [jsp.secure.errors_jsp] in context with path [] threw exception
java.lang.NullPointerException
    at com.atlassian.jira.security.JiraSecurityFilter.doFilter(JiraSecurityFilter.java:72)
    at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:192)
    at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:165)
    at com.atlassian.security.auth.trustedapps.filter.TrustedApplicationsFilter.doFilter(TrustedApplicationsFilter.java:103)
    at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:192)
    ... 23 filtered
    at com.atlassian.jira.servermetrics.CorrelationIdPopulatorFilter.doFilter(CorrelationIdPopulatorFilter.java:30)
    ... 26 filtered
    at com.atlassian.jira.servermetrics.MetricsCollectorFilter.doFilter(MetricsCollectorFilter.java:25)
    ... 28 filtered
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
    at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
    at java.lang.Thread.run(Thread.java:745)

 

How can I resolve this problem?

1 answer

0 vote

Is there more of your log?

My guess is that your server update broke either a path or added some security checking that breaks it, but it's impossible to tell from that snippet of log.

It's already solved. The issue was caused by the reboot of our server. As the server was up JIRA is started but the virtual Debian system with the JIRA-db started some time later. I guess JIRA needs some data from the db to start up properly but there was no chance to connect because the db was not running at this time. The solution was a restart of JIRA. Thank You and sorry for eventually inconvenience.

Suggest an answer

Log in or Join to answer
Community showcase
Emilee Spencer
Published yesterday in Marketplace Apps

Marketplace Spotlight: DeepAffects

Hello Atlassian Community! My name is Emilee, and I’m a Product Marketing Manager for the Marketplace team. Starting with this post, I'm kicking off a monthly series of Spotlights to highlight Ma...

34 views 0 3
Read article

Atlassian User Groups

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

Find a group

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

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot