Details
-
Bug
-
Resolution: Duplicate
-
Medium
-
None
-
6.3.9
-
None
-
6.03
-
Description
Summary
Getting 500 Page Error while browsing issues. The following error thrown in the logs:
2015-03-04 07:29:30,026 http-bio-8443-exec-5039 ERROR XXXX 449x6581431x2 XXXX 127.0.0.1 /i [com.atlassian.velocity.DefaultVelocityManager] MethodInvocationException occurred getting message body from Velocity: com.atlassian.jira.util.dbc.Assertions$NullArgumentException: url should not be null! com.atlassian.jira.util.dbc.Assertions$NullArgumentException: url should not be null! at com.atlassian.jira.util.dbc.Assertions.notNull(Assertions.java:29) at com.atlassian.jira.plugin.webfragment.model.SimpleLinkImpl.<init>(SimpleLinkImpl.java:71) at com.atlassian.jira.plugin.webfragment.DefaultSimpleLinkManager.convertWebItemToSimpleLink(DefaultSimpleLinkManager.java:228) at com.atlassian.jira.plugin.webfragment.DefaultSimpleLinkManager.getLinks(DefaultSimpleLinkManager.java:184) at com.atlassian.jira.plugin.webfragment.DefaultSimpleLinkManager.getLinksForSectionIgnoreConditions(DefaultSimpleLinkManager.java:138) <+2> (DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:483)
Steps to reproduce
There isn't any steps known at the moment.
Actual Results
Facing 500 page error while browsing issues
Expected Results
Having a (broken) link without any url value should not cause a 500 page but continue to load and render the Issue View page with warnings that there are errors which can be found in the logs.
Workaround
Restart JIRA
Attachments
Issue Links
- is duplicated by
-
-
- Closed
-