An exception occured while rendering the web panel

[Alexander Richter]

JIRA is not able to load the dates-, people-, description- and detailsmodule. it occures just in one project. following errors are thrown in the logs:

2016-10-04 10:25:56,166 http-nio-8080-exec-19 ERROR arichter 625x116x1 17osmyp 10.176.51.138 /browse/SDBA-5438 [c.a.j.web.component.ModuleWebComponentImpl] An exception occured while rendering the web panel: com.atlassian.jira.jira-view-issue-plugin:datesmodule (null)

2016-10-04 10:25:56,154 http-nio-8080-exec-19 ERROR arichter 625x116x1 17osmyp 10.176.51.138 /browse/SDBA-5438 [c.a.j.web.component.ModuleWebComponentImpl] An exception occured while rendering the web panel: com.atlassian.jira.jira-view-issue-plugin:peoplemodule (null)

2016-10-04 10:25:56,067 http-nio-8080-exec-19 ERROR arichter 625x116x1 17osmyp 10.176.51.138 /browse/SDBA-5438 [c.a.j.web.component.ModuleWebComponentImpl] An exception occured while rendering the web panel: com.atlassian.jira.jira-view-issue-plugin:descriptionmodule (null)

2016-10-04 10:25:56,055 http-nio-8080-exec-19 ERROR arichter 625x116x1 17osmyp 10.176.51.138 /browse/SDBA-5438 [c.a.j.web.component.ModuleWebComponentImpl] An exception occured while rendering the web panel: com.atlassian.jira.jira-view-issue-plugin:details-module (null)

module_error.JPG

does anyone know what to do about?

[Michael Ngangom · Accepted solution]

Hello There,

Can you make sure the plugins are enabled during the start up?

Manage Add-on section in JIRA.

A restart after increasing the plugin timeout might help. You can refer the workaround section https://confluence.atlassian.com/jirakb/jira-applications-system-plugin-timeout-while-waiting-for-add-ons-to-enable-212173447.html

If that does not helps then a further look into the atlassian-jira.log might be necessary.

BR,

Mike

[Alexander Richter]

we already had the plugin timeout set to 300. should we set it even higher?

[Alexander Richter]

just resolved the issue by myself. there was a wrong database configured in the dbconfig.xml

since changing that to the right one and re-indexing, the issues are shown correctly.

anyway.. thank you for your support