java.lang.IllegalArgumentException: type = -9

Oracle Community | 3004 | 1 decade ago
  1. 0

    Reverse Mapping

    Oracle Community | 1 decade ago | 3004
    java.lang.IllegalArgumentException: type = -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
  3. 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
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

  5. 0

    GitHub comment 1104#255848739

    GitHub | 1 month ago | wasdennnoch
    java.lang.IllegalArgumentException: method com.android.systemui.statusbar.SignalClusterView.setMobileDataIndicators [XposedOriginal] argument 9 has type int, got java.lang.Boolean
  6. 0

    GitHub comment 7204#231936574

    GitHub | 5 months ago | jnguyenx
    java.lang.IllegalArgumentException: Unknown entry type 9 for version 0. At position LogPosition{logVersion=23, byteOffset=16} and entry version V2_0

    Not finding the right solution?
    Take a tour to get the most out of Samebug.

    Tired of useless tips?

    Automated exception search integrated into your IDE

    Root Cause Analysis

    1. java.lang.IllegalArgumentException

      type = -9

      at com.solarmetric.rd.kodo.impl.jdbc.schema.Schemas.getJDBCName()
    2. com.solarmetric.rd
      SchemaGenerator.main
      1. com.solarmetric.rd.kodo.impl.jdbc.schema.Schemas.getJDBCName(Schemas.java:83)
      2. com.solarmetric.rd.kodo.impl.jdbc.schema.XMLSchemaSerializer.serializeColumn(XMLSchemaSerializer.java:217)
      3. com.solarmetric.rd.kodo.impl.jdbc.schema.XMLSchemaSerializer.serializeTable(XMLSchemaSerializer.java:194)
      4. com.solarmetric.rd.kodo.impl.jdbc.schema.XMLSchemaSerializer.serializeSchema(XMLSchemaSerializer.java:171)
      5. com.solarmetric.rd.kodo.impl.jdbc.schema.XMLSchemaSerializer.serialize(XMLSchemaSerializer.java:145)
      6. com.solarmetric.rd.meta.XMLMetaDataSerializer.serialize(XMLMetaDataSerializer.java:184)
      7. com.solarmetric.rd.meta.XMLMetaDataSerializer.serialize(XMLMetaDataSerializer.java:168)
      8. com.solarmetric.rd.meta.XMLMetaDataSerializer.serialize(XMLMetaDataSerializer.java:152)
      9. com.solarmetric.rd.meta.XMLMetaDataSerializer.serialize(XMLMetaDataSerializer.java:131)
      10. com.solarmetric.rd.kodo.impl.jdbc.schema.SchemaGenerator.run(SchemaGenerator.java:600)
      11. com.solarmetric.rd.kodo.impl.jdbc.schema.SchemaGenerator.main(SchemaGenerator.java:558)
      11 frames