java.lang.IllegalArgumentException: No event type with id 9

Atlassian JIRA | Ron Kim | 1 decade ago
tip
Your exception is missing from the Samebug knowledge base.
Here are the best solutions we found on the Internet.
Click on the to mark the helpful solution and get rewards for you help.
  1. 0

    I've just upgraded from 3.4.2 to 3.6.1. Most things work fine. However when IssueEvents are fired (created , updated ,assigned, resolved, closed, commented, reopened, deleted, moved, worklogged, workstarted, workstopped, genericevent), IllegalArgumentException is thrown by these three listeners: IssueIndexListener, IssueCacheListner and MailListener and logged in catalina.out as follows: 2006-05-15 15:40:19,468 ERROR [jira.event.issue.IssueEventDispatcher] Exception thrown from listener [com.atlassian.jira.event.listeners.search.IssueIndexList ener] : No event type with id 9 java.lang.IllegalArgumentException: No event type with id 9 2006-05-15 15:40:19,470 ERROR [jira.event.issue.IssueEventDispatcher] Exception thrown from listener [com.atlassian.jira.event.listeners.mail.MailListener] : No event type with id 9 java.lang.IllegalArgumentException: No event type with id 9 2006-05-15 15:40:19,471 ERROR [jira.event.issue.IssueEventDispatcher] Exception thrown from listener [com.atlassian.jira.event.listeners.cache.IssueCacheListe ner] : No event type with id 9 java.lang.IllegalArgumentException: No event type with id 9 at com.atlassian.jira.event.type.DefaultEventTypeManager.getEventType(DefaultEventTypeManager.java:100) at com.atlassian.jira.event.issue.AbstractIssueEventListener.workflowEvent(AbstractIssueEventListener.java:91) at com.atlassian.jira.event.issue.IssueEventDispatcher.dispatchEvent(IssueEventDispatcher.java:105) at com.atlassian.jira.event.issue.IssueEventDispatcher.dispatchEvent(IssueEventDispatcher.java:80) at com.atlassian.jira.event.issue.IssueEventDispatcher.dispatchEvent(IssueEventDispatcher.java:67) at com.atlassian.jira.web.action.issue.MoveIssueConfirm.issueUpdate(MoveIssueConfirm.java:265) at com.atlassian.jira.web.action.issue.MoveIssueConfirm.doExecute(MoveIssueConfirm.java:224) at webwork.action.ActionSupport.execute(ActionSupport.java:153) at com.atlassian.jira.action.JiraActionSupport.execute(JiraActionSupport.java:58) at webwork.dispatcher.GenericDispatcher.executeAction(GenericDispatcher.java:132) . . . Is this a bug with jira in this release?

    Atlassian JIRA | 1 decade ago | Ron Kim
    java.lang.IllegalArgumentException: No event type with id 9
  2. 0

    I've just upgraded from 3.4.2 to 3.6.1. Most things work fine. However when IssueEvents are fired (created , updated ,assigned, resolved, closed, commented, reopened, deleted, moved, worklogged, workstarted, workstopped, genericevent), IllegalArgumentException is thrown by these three listeners: IssueIndexListener, IssueCacheListner and MailListener and logged in catalina.out as follows: 2006-05-15 15:40:19,468 ERROR [jira.event.issue.IssueEventDispatcher] Exception thrown from listener [com.atlassian.jira.event.listeners.search.IssueIndexList ener] : No event type with id 9 java.lang.IllegalArgumentException: No event type with id 9 2006-05-15 15:40:19,470 ERROR [jira.event.issue.IssueEventDispatcher] Exception thrown from listener [com.atlassian.jira.event.listeners.mail.MailListener] : No event type with id 9 java.lang.IllegalArgumentException: No event type with id 9 2006-05-15 15:40:19,471 ERROR [jira.event.issue.IssueEventDispatcher] Exception thrown from listener [com.atlassian.jira.event.listeners.cache.IssueCacheListe ner] : No event type with id 9 java.lang.IllegalArgumentException: No event type with id 9 at com.atlassian.jira.event.type.DefaultEventTypeManager.getEventType(DefaultEventTypeManager.java:100) at com.atlassian.jira.event.issue.AbstractIssueEventListener.workflowEvent(AbstractIssueEventListener.java:91) at com.atlassian.jira.event.issue.IssueEventDispatcher.dispatchEvent(IssueEventDispatcher.java:105) at com.atlassian.jira.event.issue.IssueEventDispatcher.dispatchEvent(IssueEventDispatcher.java:80) at com.atlassian.jira.event.issue.IssueEventDispatcher.dispatchEvent(IssueEventDispatcher.java:67) at com.atlassian.jira.web.action.issue.MoveIssueConfirm.issueUpdate(MoveIssueConfirm.java:265) at com.atlassian.jira.web.action.issue.MoveIssueConfirm.doExecute(MoveIssueConfirm.java:224) at webwork.action.ActionSupport.execute(ActionSupport.java:153) at com.atlassian.jira.action.JiraActionSupport.execute(JiraActionSupport.java:58) at webwork.dispatcher.GenericDispatcher.executeAction(GenericDispatcher.java:132) . . . Is this a bug with jira in this release?

    Atlassian JIRA | 1 decade ago | Ron Kim
    java.lang.IllegalArgumentException: No event type with id 9

    Root Cause Analysis

    1. java.lang.IllegalArgumentException

      No event type with id 9

      at com.atlassian.jira.event.type.DefaultEventTypeManager.getEventType()
    2. com.atlassian.jira
      MoveIssueConfirm.doExecute
      1. com.atlassian.jira.event.type.DefaultEventTypeManager.getEventType(DefaultEventTypeManager.java:100)
      2. com.atlassian.jira.event.issue.AbstractIssueEventListener.workflowEvent(AbstractIssueEventListener.java:91)
      3. com.atlassian.jira.event.issue.IssueEventDispatcher.dispatchEvent(IssueEventDispatcher.java:105)
      4. com.atlassian.jira.event.issue.IssueEventDispatcher.dispatchEvent(IssueEventDispatcher.java:80)
      5. com.atlassian.jira.event.issue.IssueEventDispatcher.dispatchEvent(IssueEventDispatcher.java:67)
      6. com.atlassian.jira.web.action.issue.MoveIssueConfirm.issueUpdate(MoveIssueConfirm.java:265)
      7. com.atlassian.jira.web.action.issue.MoveIssueConfirm.doExecute(MoveIssueConfirm.java:224)
      7 frames
    3. webwork.action
      ActionSupport.execute
      1. webwork.action.ActionSupport.execute(ActionSupport.java:153)
      1 frame
    4. com.atlassian.jira
      JiraActionSupport.execute
      1. com.atlassian.jira.action.JiraActionSupport.execute(JiraActionSupport.java:58)
      1 frame
    5. webwork.dispatcher
      GenericDispatcher.executeAction
      1. webwork.dispatcher.GenericDispatcher.executeAction(GenericDispatcher.java:132)
      1 frame