You are viewing a plain text version of this content. The canonical link for it is here.
Posted to infrastructure-issues@apache.org by "Jeff Turner (JIRA)" <ji...@apache.org> on 2010/12/16 09:15:01 UTC
[jira] Created: (INFRA-3290) Stacktrace on activemq-imported JIRA
issues with subtasks
Stacktrace on activemq-imported JIRA issues with subtasks
---------------------------------------------------------
Key: INFRA-3290
URL: https://issues.apache.org/jira/browse/INFRA-3290
Project: Infrastructure
Issue Type: Sub-task
Security Level: public (Regular issues)
Components: JIRA
Reporter: Jeff Turner
Many ActiveMQ, Camel and ServiceMix issues imported from the old activemq JIRA instance are displaying a stacktrace in their 'Sub-Tasks' section:
An error occurred whilst rendering this message. Please contact the administrators, and inform them of this bug. Details: ------- org.apache.velocity.exception.MethodInvocationException: Invocation of method 'getHtml' in class com.atlassian.jira.web.component.subtask.SubTaskReorderColumnLayoutItem threw exception class java.lang.NullPointerException : null at org.apache.velocity.runtime.parser.node.ASTMethod.execute(ASTMethod.java:246) at org.apache.velocity.runtime.parser.node.ASTReference.execute(ASTReference.java:175) at org.apache.velocity.runtime.parser.node.ASTReference.value(ASTReference.java:327) at org.apache.velocity.runtime.parser.node.ASTExpression.value(ASTExpression.java:51) at org.apache.velocity.runtime.parser.node.ASTSetDirective.render(ASTSetDirective.java:95) at org.apache.velocity.runtime.parser.node.ASTBlock.render(ASTBlock.java:55) at org.apache.velocity.runtime.directive.Foreach.render(Foreach.java:166) at org.apache.velocity.runtime.parser.node.ASTDirective.render(ASTDirective.java:114) at org.apache.velocity.runtime.parser.node.SimpleNode.render(SimpleNode.java:230) at org.apache.velocity.runtime.directive.VelocimacroProxy.render(VelocimacroProxy.java:172) at org.apache.velocity.runtime.parser.node.ASTDirective.render(ASTDirective.java:114) at org.apache.velocity.runtime.parser.node.SimpleNode.render(SimpleNode.java:230) at org.apache.velocity.Template.merge(Template.java:256) at org.apache.velocity.app.VelocityEngine.mergeTemplate(VelocityEngine.java:450) at com.atlassian.velocity.DefaultVelocityManager.getEncodedBody(DefaultVelocityManager.java:77) at com.atlassian.velocity.DefaultVelocityManager.getEncodedBody(DefaultVelocityManager.java:61) at com.atlassian.velocity.DefaultVelocityManager.getEncodedBody(DefaultVelocityManager.java:56) at com.atlassian.jira.web.component.AbstractWebComponent.getHtml(AbstractWebComponent.java:33) at com.atlassian.jira.web.component.IssueTableWebComponent$1.write(IssueTableWebComponent.java:100) at com.atlassian.jira.web.component.IssueTableWebComponent.getHtml(IssueTableWebComponent.java:57) at org.apache.jsp.includes.panels.issue.view_005fsubtaskissues_jsp._jspService(view_005fsubtaskissues_jsp.java:330) at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70) at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) at
......
This appears to be because the JIRA project importer hasn't set the 'sequence' value for the 'issuelink' table rows, and if there is more than one subtask this causes breakage. The following 35 issues are affected:
jira_3135=# select distinct pkey from jiraissue ji, issuelink a, issuelink b where ji.id=a.source and a.source=b.source and a.destination!=b.destination and a.linktype=b.linktype and a.linktype=(select id from issuelinktype where pstyle='jira_subtask') and (a.sequence is null or b.sequence is null);
pkey
-------------
SMX4-663
AMQ-301
AMQ-1797
AMQNET-185
CAMEL-8
AMQNET-113
CAMEL-420
CAMEL-1037
SM-233
CAMEL-2565
CAMEL-2056
AMQ-2736
CAMEL-2496
CAMEL-1043
SMXCOMP-570
SMXCOMP-260
CAMEL-1072
AMQNET-68
SM-189
CAMEL-1873
SMX4-442
SMXCOMP-499
CAMEL-115
CAMEL-375
CAMEL-1276
CAMEL-961
AMQNET-107
CAMEL-797
SM-1246
CAMEL-2248
CAMEL-527
CAMEL-720
CAMEL-1168
AMQ-2123
CAMEL-1112
(35 rows)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (INFRA-3290) Stacktrace on activemq-imported JIRA
issues with subtasks
Posted by "Jeff Turner (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-3290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jeff Turner resolved INFRA-3290.
--------------------------------
Resolution: Fixed
Assignee: Jeff Turner
Fixed with some cunning SQL:
select * into broken_issuelink_sequences from (select jiraissue.pkey, issuelink.*, rank() over (partition by issuelink.source order by issuelink.id)-1 as r from jiraissue, issuelink where jiraissue.id=issuelink.source and issuelink.linktype=10010 and sequence is null ) a;
update issuelink il set sequence=(select r from broken_issuelink_sequences where id=il.id) where sequence is null;
> Stacktrace on activemq-imported JIRA issues with subtasks
> ---------------------------------------------------------
>
> Key: INFRA-3290
> URL: https://issues.apache.org/jira/browse/INFRA-3290
> Project: Infrastructure
> Issue Type: Sub-task
> Security Level: public(Regular issues)
> Components: JIRA
> Reporter: Jeff Turner
> Assignee: Jeff Turner
>
> Many ActiveMQ, Camel and ServiceMix issues imported from the old activemq JIRA instance are displaying a stacktrace in their 'Sub-Tasks' section:
> An error occurred whilst rendering this message. Please contact the administrators, and inform them of this bug. Details: ------- org.apache.velocity.exception.MethodInvocationException: Invocation of method 'getHtml' in class com.atlassian.jira.web.component.subtask.SubTaskReorderColumnLayoutItem threw exception class java.lang.NullPointerException : null at org.apache.velocity.runtime.parser.node.ASTMethod.execute(ASTMethod.java:246) at org.apache.velocity.runtime.parser.node.ASTReference.execute(ASTReference.java:175) at org.apache.velocity.runtime.parser.node.ASTReference.value(ASTReference.java:327) at org.apache.velocity.runtime.parser.node.ASTExpression.value(ASTExpression.java:51) at org.apache.velocity.runtime.parser.node.ASTSetDirective.render(ASTSetDirective.java:95) at org.apache.velocity.runtime.parser.node.ASTBlock.render(ASTBlock.java:55) at org.apache.velocity.runtime.directive.Foreach.render(Foreach.java:166) at org.apache.velocity.runtime.parser.node.ASTDirective.render(ASTDirective.java:114) at org.apache.velocity.runtime.parser.node.SimpleNode.render(SimpleNode.java:230) at org.apache.velocity.runtime.directive.VelocimacroProxy.render(VelocimacroProxy.java:172) at org.apache.velocity.runtime.parser.node.ASTDirective.render(ASTDirective.java:114) at org.apache.velocity.runtime.parser.node.SimpleNode.render(SimpleNode.java:230) at org.apache.velocity.Template.merge(Template.java:256) at org.apache.velocity.app.VelocityEngine.mergeTemplate(VelocityEngine.java:450) at com.atlassian.velocity.DefaultVelocityManager.getEncodedBody(DefaultVelocityManager.java:77) at com.atlassian.velocity.DefaultVelocityManager.getEncodedBody(DefaultVelocityManager.java:61) at com.atlassian.velocity.DefaultVelocityManager.getEncodedBody(DefaultVelocityManager.java:56) at com.atlassian.jira.web.component.AbstractWebComponent.getHtml(AbstractWebComponent.java:33) at com.atlassian.jira.web.component.IssueTableWebComponent$1.write(IssueTableWebComponent.java:100) at com.atlassian.jira.web.component.IssueTableWebComponent.getHtml(IssueTableWebComponent.java:57) at org.apache.jsp.includes.panels.issue.view_005fsubtaskissues_jsp._jspService(view_005fsubtaskissues_jsp.java:330) at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70) at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) at
> ......
> This appears to be because the JIRA project importer hasn't set the 'sequence' value for the 'issuelink' table rows, and if there is more than one subtask this causes breakage. The following 35 issues are affected:
> jira_3135=# select distinct pkey from jiraissue ji, issuelink a, issuelink b where ji.id=a.source and a.source=b.source and a.destination!=b.destination and a.linktype=b.linktype and a.linktype=(select id from issuelinktype where pstyle='jira_subtask') and (a.sequence is null or b.sequence is null);
> pkey
> -------------
> SMX4-663
> AMQ-301
> AMQ-1797
> AMQNET-185
> CAMEL-8
> AMQNET-113
> CAMEL-420
> CAMEL-1037
> SM-233
> CAMEL-2565
> CAMEL-2056
> AMQ-2736
> CAMEL-2496
> CAMEL-1043
> SMXCOMP-570
> SMXCOMP-260
> CAMEL-1072
> AMQNET-68
> SM-189
> CAMEL-1873
> SMX4-442
> SMXCOMP-499
> CAMEL-115
> CAMEL-375
> CAMEL-1276
> CAMEL-961
> AMQNET-107
> CAMEL-797
> SM-1246
> CAMEL-2248
> CAMEL-527
> CAMEL-720
> CAMEL-1168
> AMQ-2123
> CAMEL-1112
> (35 rows)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] [Closed] (INFRA-3290) Stacktrace on activemq-imported JIRA
issues with subtasks
Posted by "#asfinfra IRC Bot (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-3290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
#asfinfra IRC Bot closed INFRA-3290.
------------------------------------
> Stacktrace on activemq-imported JIRA issues with subtasks
> ---------------------------------------------------------
>
> Key: INFRA-3290
> URL: https://issues.apache.org/jira/browse/INFRA-3290
> Project: Infrastructure
> Issue Type: Sub-task
> Security Level: public(Regular issues)
> Components: JIRA
> Reporter: Jeff Turner
> Assignee: Jeff Turner
>
> Many ActiveMQ, Camel and ServiceMix issues imported from the old activemq JIRA instance are displaying a stacktrace in their 'Sub-Tasks' section:
> An error occurred whilst rendering this message. Please contact the administrators, and inform them of this bug. Details: ------- org.apache.velocity.exception.MethodInvocationException: Invocation of method 'getHtml' in class com.atlassian.jira.web.component.subtask.SubTaskReorderColumnLayoutItem threw exception class java.lang.NullPointerException : null at org.apache.velocity.runtime.parser.node.ASTMethod.execute(ASTMethod.java:246) at org.apache.velocity.runtime.parser.node.ASTReference.execute(ASTReference.java:175) at org.apache.velocity.runtime.parser.node.ASTReference.value(ASTReference.java:327) at org.apache.velocity.runtime.parser.node.ASTExpression.value(ASTExpression.java:51) at org.apache.velocity.runtime.parser.node.ASTSetDirective.render(ASTSetDirective.java:95) at org.apache.velocity.runtime.parser.node.ASTBlock.render(ASTBlock.java:55) at org.apache.velocity.runtime.directive.Foreach.render(Foreach.java:166) at org.apache.velocity.runtime.parser.node.ASTDirective.render(ASTDirective.java:114) at org.apache.velocity.runtime.parser.node.SimpleNode.render(SimpleNode.java:230) at org.apache.velocity.runtime.directive.VelocimacroProxy.render(VelocimacroProxy.java:172) at org.apache.velocity.runtime.parser.node.ASTDirective.render(ASTDirective.java:114) at org.apache.velocity.runtime.parser.node.SimpleNode.render(SimpleNode.java:230) at org.apache.velocity.Template.merge(Template.java:256) at org.apache.velocity.app.VelocityEngine.mergeTemplate(VelocityEngine.java:450) at com.atlassian.velocity.DefaultVelocityManager.getEncodedBody(DefaultVelocityManager.java:77) at com.atlassian.velocity.DefaultVelocityManager.getEncodedBody(DefaultVelocityManager.java:61) at com.atlassian.velocity.DefaultVelocityManager.getEncodedBody(DefaultVelocityManager.java:56) at com.atlassian.jira.web.component.AbstractWebComponent.getHtml(AbstractWebComponent.java:33) at com.atlassian.jira.web.component.IssueTableWebComponent$1.write(IssueTableWebComponent.java:100) at com.atlassian.jira.web.component.IssueTableWebComponent.getHtml(IssueTableWebComponent.java:57) at org.apache.jsp.includes.panels.issue.view_005fsubtaskissues_jsp._jspService(view_005fsubtaskissues_jsp.java:330) at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70) at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) at
> ......
> This appears to be because the JIRA project importer hasn't set the 'sequence' value for the 'issuelink' table rows, and if there is more than one subtask this causes breakage. The following 35 issues are affected:
> jira_3135=# select distinct pkey from jiraissue ji, issuelink a, issuelink b where ji.id=a.source and a.source=b.source and a.destination!=b.destination and a.linktype=b.linktype and a.linktype=(select id from issuelinktype where pstyle='jira_subtask') and (a.sequence is null or b.sequence is null);
> pkey
> -------------
> SMX4-663
> AMQ-301
> AMQ-1797
> AMQNET-185
> CAMEL-8
> AMQNET-113
> CAMEL-420
> CAMEL-1037
> SM-233
> CAMEL-2565
> CAMEL-2056
> AMQ-2736
> CAMEL-2496
> CAMEL-1043
> SMXCOMP-570
> SMXCOMP-260
> CAMEL-1072
> AMQNET-68
> SM-189
> CAMEL-1873
> SMX4-442
> SMXCOMP-499
> CAMEL-115
> CAMEL-375
> CAMEL-1276
> CAMEL-961
> AMQNET-107
> CAMEL-797
> SM-1246
> CAMEL-2248
> CAMEL-527
> CAMEL-720
> CAMEL-1168
> AMQ-2123
> CAMEL-1112
> (35 rows)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira