XPP3 Pull Parser Library not Present
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Symptoms
When creating a new issue, the following error occurs:
1
2
3
4
5
6
7
8
9
java.lang.IllegalArgumentException: XPP3 pull parser library not present. Specify another driver. For example: new XStream(new DomDriver())
at com.thoughtworks.xstream.io.xml.XppDriver.createReader(XppDriver.java:19)
at com.thoughtworks.xstream.XStream.fromXML(XStream.java:475)
at com.thoughtworks.xstream.XStream.fromXML(XStream.java:468)
at com.atlassian.jira.issue.customfields.manager.DefaultGenericConfigManager.fromXml(DefaultGenericConfigManager.java:139)
at com.atlassian.jira.issue.customfields.manager.DefaultGenericConfigManager.retrieve(DefaultGenericConfigManager.java:94)
at com.atlassian.jira.issue.customfields.manager.CachedGenericConfigManager.retrieve(CachedGenericConfigManager.java:55)
at com.atlassian.jira.issue.fields.config.manager.IssueTypeSchemeManagerImpl.getDefaultValue(IssueTypeSchemeManagerImpl.java:194)
at com.atlassian.jira.web.action.admin.issuetypes.ConfigureOptionScheme.doDefault(ConfigureOptionScheme.java:70)
Cause
This can be caused by clashes in libraries we ship with JIRA with applications you currently have deployed in the same application server.
Resolution
Inspect your Application Server and see if there is any other xstream*.jar file being loaded in lieu of JIRA's. If so, remove it from the shared library classpath folder.
Was this helpful?