Error 500 : TOMCAT restarted during REINDEX

Question

Dear all

In the middle of an INDEX REBUILD an IT sysadmin restarted the Atlassian JIRA service.

This is a Server version - JIRA 7.4.2

Windows Server 2012.

SQL Server 2016

What do you suggest ? We are not able to locate the SUPPORT ENTITLEMENT NUMBER.

Please see the log from the server :-

Technical details

Log's referral number: 82c1d94e-7446-4130-aed2-1e1e3580201a

Cause

Referer URL: Unknown
java.lang.RuntimeException: javax.servlet.ServletException: Servlet execution threw an exception

at com.atlassian.jira.web.dispatcher.JiraWebworkActionDispatcher.prepareDispatcher(JiraWebworkActionDispatcher.java:196) [classes/:?]
at com.atlassian.jira.web.dispatcher.JiraWebworkActionDispatcher.service(JiraWebworkActionDispatcher.java:133) [classes/:?]
at javax.servlet.http.HttpServlet.service(HttpServlet.java:729) [servlet-api.jar:?]
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:230) [catalina.jar:8.5.6]
... 390 more

Keshav Tadimeti · Answer

Someone from the admin team, cleared the caches, then restarted the service.

I was able to login and restarted Indexing.

Issue solved.

THanks

Danyal Iqbal · Answer

This should not cause a problem.

* Restart tomcat(if separately installed)
* Restart Jira

Sloan N_ B_ · Answer

Hi @Keshav Tadimeti

What is your issue? Is Jira now unable to start?
This log fragment doesn't give me an insight.

If you can't access your Jira, you can look for your SEN on my.atlassian.com aswell or find it on any invoices by atlassian.

Have you tried doing a full reindex (also often called reindex from scratch)? See here under resolution: Unable to rebuild JIRA application indexes

Regards
Niklas