com.thoughtworks.xstream.mapper.CannotResolveClassException: WallPosting : WallPosting

logging-log4j-user | Godmar Back | 7 years 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

    Q: how to prevent log4j from cutting off stack traces?

    logging-log4j-user | 7 years ago | Godmar Back
    com.thoughtworks.xstream.mapper.CannotResolveClassException: WallPosting : WallPosting
  2. 0

    Q: how to prevent log4j from cutting off stack traces?

    logging-log4j-user | 7 years ago | Godmar Back
    com.thoughtworks.xstream.mapper.CannotResolveClassException: WallPosting : WallPosting
  3. 0

    This issue occurs when upgrading from JIRA 4.1 and earlier and using one of the multi value custom field. The issue has been documented in https://confluence.atlassian.com/display/JIRAKB/JIRA+Crashes+while+Creating+an+Issue however a bug report has never been filed. h3. Steps to reproduce # On a JIRA 4.1 instance, create a custom field, of type multi select # Add a few values to that field # Run an in-place upgrade to any newer version h3. Expected Results Upgrades without issue h3. Actual Results JIRA crashes mid-upgrade with stack trace (below) OR upgrade finishes, but crashes when creating an issue. {noformat} com.thoughtworks.xstream.mapper.CannotResolveClassException: java.util.Collections-UnmodifiableList : java.util.Collections-UnmodifiableList at com.thoughtworks.xstream.mapper.DefaultMapper.realClass(DefaultMapper.java:68) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:38) at com.thoughtworks.xstream.mapper.DynamicProxyMapper.realClass(DynamicProxyMapper.java:71) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:38) at com.thoughtworks.xstream.mapper.PackageAliasingMapper.realClass(PackageAliasingMapper.java:88) ... {noformat} h3. Workaround See the KB article at https://confluence.atlassian.com/display/JIRAKB/JIRA+Crashes+while+Creating+an+Issue

    Atlassian JIRA | 4 years ago | Chris Shim [Atlassian]
    com.thoughtworks.xstream.mapper.CannotResolveClassException: java.util.Collections-UnmodifiableList : java.util.Collections-UnmodifiableList
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

  5. 0

    This issue occurs when upgrading from JIRA 4.1 and earlier and using one of the multi value custom field. The issue has been documented in https://confluence.atlassian.com/display/JIRAKB/JIRA+Crashes+while+Creating+an+Issue however a bug report has never been filed. h3. Steps to reproduce # On a JIRA 4.1 instance, create a custom field, of type multi select # Add a few values to that field # Run an in-place upgrade to any newer version h3. Expected Results Upgrades without issue h3. Actual Results JIRA crashes mid-upgrade with stack trace (below) OR upgrade finishes, but crashes when creating an issue. {noformat} com.thoughtworks.xstream.mapper.CannotResolveClassException: java.util.Collections-UnmodifiableList : java.util.Collections-UnmodifiableList at com.thoughtworks.xstream.mapper.DefaultMapper.realClass(DefaultMapper.java:68) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:38) at com.thoughtworks.xstream.mapper.DynamicProxyMapper.realClass(DynamicProxyMapper.java:71) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:38) at com.thoughtworks.xstream.mapper.PackageAliasingMapper.realClass(PackageAliasingMapper.java:88) ... {noformat} h3. Workaround See the KB article at https://confluence.atlassian.com/display/JIRAKB/JIRA+Crashes+while+Creating+an+Issue

    Atlassian JIRA | 4 years ago | Chris Shim [Atlassian]
    com.thoughtworks.xstream.mapper.CannotResolveClassException: java.util.Collections-UnmodifiableList : java.util.Collections-UnmodifiableList
  6. 0

    [JENKINS-27992] Unable to launch weblogic Deployer plugin after installation - Jenkins JIRA

    jenkins-ci.org | 1 year ago
    com.thoughtworks.xstream.mapper.CannotResolveClassException: xs:schema

    Root Cause Analysis

    1. com.thoughtworks.xstream.mapper.CannotResolveClassException

      WallPosting : WallPosting

      at com.thoughtworks.xstream.mapper.DefaultMapper.realClass()
    2. XStream Core
      PackageAliasingMapper.realClass
      1. com.thoughtworks.xstream.mapper.DefaultMapper.realClass(DefaultMapper.java:68)
      2. com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:38)
      3. com.thoughtworks.xstream.mapper.DynamicProxyMapper.realClass(DynamicProxyMapper.java:71)
      4. com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:38)
      5. com.thoughtworks.xstream.mapper.PackageAliasingMapper.realClass(PackageAliasingMapper.java:88)
      5 frames