HTTP Status 500 - Exception occurred while rendering template 'templates/jira/appconsistency/jiralocked.vm'.

Our IT admins changed the domain and hostnames of our JIRA instance, so I changed the hostname of the JIRA computer accordingly. For an unknown reason this did not work out and it was decided to revert to the initial hostnames and so. Hence I put back the original domain and hostnames on the computer. Now JIRA does not start anymore with the error mentioned below when trying to access it via http://localhost:8080/jira:

HTTP Status 500 - Exception occurred while rendering template 'templates/jira/appconsistency/jiralocked.vm'.


type Exception report

message Exception occurred while rendering template 'templates/jira/appconsistency/jiralocked.vm'.

description The server encountered an internal error that prevented it from fulfilling this request.

exception

javax.servlet.ServletException: Exception occurred while rendering template 'templates/jira/appconsistency/jiralocked.vm'.
	com.atlassian.jira.startup.JiraStartupChecklistFilter.doFilter(JiraStartupChecklistFilter.java:102)
	com.atlassian.jira.web.filters.MultipartBoundaryCheckFilter.doFilter(MultipartBoundaryCheckFilter.java:41)
	com.atlassian.jira.web.filters.steps.ChainedFilterStepRunner.doFilter(ChainedFilterStepRunner.java:87)
	com.atlassian.jira.web.filters.JiraFirstFilter.doFilter(JiraFirstFilter.java:61)

root cause

java.lang.NullPointerException
	org.apache.velocity.util.introspection.UberspectImpl.getMethod(UberspectImpl.java:183)
	com.atlassian.velocity.htmlsafe.introspection.AnnotationBoxingUberspect.getMethod(AnnotationBoxingUberspect.java:108)
	org.apache.velocity.runtime.parser.node.ASTMethod.execute(ASTMethod.java:192)
	org.apache.velocity.runtime.parser.node.ASTReference.execute(ASTReference.java:262)
	org.apache.velocity.runtime.parser.node.ASTReference.render(ASTReference.java:342)
	org.apache.velocity.runtime.parser.node.ASTBlock.render(ASTBlock.java:72)
	org.apache.velocity.runtime.parser.node.ASTIfStatement.render(ASTIfStatement.java:87)
	org.apache.velocity.runtime.parser.node.SimpleNode.render(SimpleNode.java:336)
	org.apache.velocity.Template.merge(Template.java:328)
	org.apache.velocity.Template.merge(Template.java:235)
	org.apache.velocity.app.VelocityEngine.mergeTemplate(VelocityEngine.java:381)
	com.atlassian.jira.startup.JiraStartupChecklistFilter.doFilter(JiraStartupChecklistFilter.java:98)
	com.atlassian.jira.web.filters.MultipartBoundaryCheckFilter.doFilter(MultipartBoundaryCheckFilter.java:41)
	com.atlassian.jira.web.filters.steps.ChainedFilterStepRunner.doFilter(ChainedFilterStepRunner.java:87)
	com.atlassian.jira.web.filters.JiraFirstFilter.doFilter(JiraFirstFilter.java:61)

note The full stack trace of the root cause is available in the Apache Tomcat/7.0.55 logs.


Apache Tomcat/7.0.55

Do you have any idea what I did wrong?

Thanks!

Yvan

2 answers

1 accepted

0 vote

That error suggests that Tomcat is running, but you've relocated JIRA in such a way that it can't find the installation.

I think you need to go into the exact detail of what was changed when your admins changed the hostname, and what you did in JIRA to adapt to it.

Thank you for a swift reply. I think the only thing what could be still wrong is the base URL location of the JIRA instance - which is accessed through the admin panel. Is there another way to change the base URL- so that it at least looks at localhost port 8080

An incorrect base url will just warn you that it is incorrect in the browser. It is not the cause of this problem I'm afraid - you've changed a lot more than that, and it looks like your installation is completely broken.

Yvan : Were you able to fix it? I face the same issue.

The lack of response suggests that they fixed whatever they'd broken in Tomcat without our help.

Try rebooting the server and restarting the application again. Run a ipconfig /dnsflush command on the client.

If all changes have been rolled back the reboot and restart should work.

For future my recommendation would be to test such critical changes first on a test instance.

Pilar

Thank you for this feedback. Unfortunatelly it did not solve my problem, but I will for sure take your recommendations into account.

Suggest an answer

Log in or Join to answer
Community showcase
Sarah Schuster
Posted Jan 29, 2018 in Jira

What are common themes you've seen across successful & failed Jira Software implementations?

Hey everyone! My name is Sarah Schuster, and I'm a Customer Success Manager in Atlassian specializing in Jira Software Cloud. Over the next few weeks I will be posting discussion topics (8 total) to ...

3,334 views 14 20
Join discussion

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