Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-21873

FlushCachesFunction post-function is deprecated and should be removed during upgrade

    XMLWordPrintable

Details

    Description

      com.atlassian.jira.workflow.function.misc.FlushCachesFunction

      This came up from a support ticket I got. User imported a XML backup from JIRA 3.13 to JIRA 4.1.2 and realized that his workflow operations didn't work anymore. I found several post-functions from a deprecated code: FlushCachesFunction.
      The workaround for the customer is really painfull and unpleasant, because it is necessary to create a draft of each workflow and edit each step at a time, deleting the post-function that is not working (screenshot attached).

      The other option is to make a XML backup of your JIRA data, and scan and remove this post-function, and re-import it again.

      Stacktrace: 

      2010-07-26 01:55:32,706 http-80-13 INFO xxxx 115x5299x1 19kmi0b xxx.xxx.xx.xx /secure/CommentAssignIssue.jspa [atlassian.jira.workflow.DefaultOSWorkflowConfigurator] No TypeResolvers found registered for class 'com.atlassian.jira.workflow.function.misc.FlushCachesFunction'.
2010-07-26 01:55:32,707 http-80-13 ERROR xxxx 115x5299x1 19kmi0b xxx.xxx.xx.xx /secure/CommentAssignIssue.jspa [atlassian.jira.workflow.SimpleWorkflowManager] An exception occurred
com.opensymphony.workflow.WorkflowException: Could not load FunctionProvider class
	at com.opensymphony.workflow.AbstractWorkflow.executeFunction(AbstractWorkflow.java:865)
	at com.opensymphony.workflow.AbstractWorkflow.transitionWorkflow(AbstractWorkflow.java:1265)
	at com.opensymphony.workflow.AbstractWorkflow.doAction(AbstractWorkflow.java:567)
	at com.atlassian.jira.workflow.SimpleWorkflowManager.doWorkflowAction(SimpleWorkflowManager.java:300)
	at com.atlassian.jira.bc.issue.DefaultIssueService.transition(DefaultIssueService.java:416)
	at com.atlassian.jira.web.action.issue.CommentAssignIssue.doExecute(CommentAssignIssue.java:204)
	at webwork.action.ActionSupport.execute(ActionSupport.java:165)
	at com.atlassian.jira.action.JiraActionSupport.execute(JiraActionSupport.java:54)
	at webwork.dispatcher.GenericDispatcher.executeAction(GenericDispatcher.java:139)
	at com.atlassian.jira.web.dispatcher.JiraServletDispatcher.service(JiraServletDispatcher.java:171)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)

      Attachments

        Issue Links

          relates to

          Bug - A problem which impairs or prevents the functions of the product. JRASERVER-22397 DefaultOSWorkflowConfigurator.JiraTypeResolverDelegator should fall back to JiraUtils.loadComponent(objClass) to load the class if type resolver is not found

          • Medium - Medium priority issues
          • Closed

          Activity

            People

              Unassigned Unassigned
              ldacorrea Luciano de Andrade Correa [Atlassian]
              Votes:
              4 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: