Details
-
Bug
-
Resolution: Unresolved
-
Low
-
None
-
4.4, 5.1, 5.2, 6.0
-
4.04
-
1
-
Severity 3 - Minor
-
0
-
Description
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.
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
Expected Results
Upgrades without issue
Actual Results
JIRA crashes mid-upgrade with stack trace (below) OR upgrade finishes, but crashes when creating an issue.
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) ...
Workaround
See the KB article at https://confluence.atlassian.com/display/JIRAKB/JIRA+Crashes+while+Creating+an+Issue