com.opensymphony.workflow.InternalWorkflowException: An unknown exception occured while executing FunctionProvider: com.atlassian.jira.workflow.function.issue.UpdateIssueFieldFieldFunction

Atlassian JIRA | Nick Minutello | 1 decade ago
  1. 0

    On Oracle, we have a size limitation for issue Description and Comment fields of 4000 characters. So, if you add a description or a comment that is greater than that, you get an error: Exception: com.opensymphony.workflow.InternalWorkflowException: An unknown exception occured while executing FunctionProvider: com.atlassian.jira.workflow.function.issue.UpdateIssueFieldFieldFunction at com.opensymphony.workflow.AbstractWorkflow.executeFunction(AbstractWorkflow.java:934) at com.opensymphony.workflow.AbstractWorkflow.transitionWorkflow(AbstractWorkflow.java:1107) at com.opensymphony.workflow.AbstractWorkflow.initialize(AbstractWorkflow.java:366) at com.atlassian.jira.issue.IssueUtils.createIssue(IssueUtils.java:80) at com.atlassian.jira.issue.IssueUtils.createIssue(IssueUtils.java:65) The problem here is that there is no hint as to what caused the error. It would be better to be able to give an error: "Your comment is too large. Consider creating an attachment." Its practically impossible from the Entity Engine exception, to programmatically work out what happened (even the error message depends on what version of oracle) The only other thing to do is to make it part of the Web Action validation - thereby forcing a limit on everyone. This would actually be a good thing, because they might otherwise end up hitting this limitation when changing databases (as we did). Especially since HSQLDB in the stand-alone version doesnt have any limit....

    Atlassian JIRA | 1 decade ago | Nick Minutello
    com.opensymphony.workflow.InternalWorkflowException: An unknown exception occured while executing FunctionProvider: com.atlassian.jira.workflow.function.issue.UpdateIssueFieldFieldFunction
  2. 0

    On Oracle, we have a size limitation for issue Description and Comment fields of 4000 characters. So, if you add a description or a comment that is greater than that, you get an error: Exception: com.opensymphony.workflow.InternalWorkflowException: An unknown exception occured while executing FunctionProvider: com.atlassian.jira.workflow.function.issue.UpdateIssueFieldFieldFunction at com.opensymphony.workflow.AbstractWorkflow.executeFunction(AbstractWorkflow.java:934) at com.opensymphony.workflow.AbstractWorkflow.transitionWorkflow(AbstractWorkflow.java:1107) at com.opensymphony.workflow.AbstractWorkflow.initialize(AbstractWorkflow.java:366) at com.atlassian.jira.issue.IssueUtils.createIssue(IssueUtils.java:80) at com.atlassian.jira.issue.IssueUtils.createIssue(IssueUtils.java:65) The problem here is that there is no hint as to what caused the error. It would be better to be able to give an error: "Your comment is too large. Consider creating an attachment." Its practically impossible from the Entity Engine exception, to programmatically work out what happened (even the error message depends on what version of oracle) The only other thing to do is to make it part of the Web Action validation - thereby forcing a limit on everyone. This would actually be a good thing, because they might otherwise end up hitting this limitation when changing databases (as we did). Especially since HSQLDB in the stand-alone version doesnt have any limit....

    Atlassian JIRA | 1 decade ago | Nick Minutello
    com.opensymphony.workflow.InternalWorkflowException: An unknown exception occured while executing FunctionProvider: com.atlassian.jira.workflow.function.issue.UpdateIssueFieldFieldFunction

    Root Cause Analysis

    1. com.opensymphony.workflow.InternalWorkflowException

      An unknown exception occured while executing FunctionProvider: com.atlassian.jira.workflow.function.issue.UpdateIssueFieldFieldFunction

      at com.opensymphony.workflow.AbstractWorkflow.executeFunction()
    2. com.opensymphony.workflow
      AbstractWorkflow.initialize
      1. com.opensymphony.workflow.AbstractWorkflow.executeFunction(AbstractWorkflow.java:934)
      2. com.opensymphony.workflow.AbstractWorkflow.transitionWorkflow(AbstractWorkflow.java:1107)
      3. com.opensymphony.workflow.AbstractWorkflow.initialize(AbstractWorkflow.java:366)
      3 frames
    3. com.atlassian.jira
      IssueUtils.createIssue
      1. com.atlassian.jira.issue.IssueUtils.createIssue(IssueUtils.java:80)
      2. com.atlassian.jira.issue.IssueUtils.createIssue(IssueUtils.java:65)
      2 frames