Identifying a problem custom field

Cody Church1

I have an issue with upgrading JIRA.  It seems whenever we attempt an upgrade to a version beyond 6.2, our current version, the indexing is destroyed by a rogue customfield.  However, we have so many customfields generated I am uncertain of how to isolate the one causing the problem.  Here is a sample of the errors we are getting:

2015-03-31 11:20:04,842 JiraImportTaskExecutionThread-1 WARN administrator 678x866x1 1c9z6p1 10.160.49.147 /secure/admin/XmlRestore.jspa [atlassian.jira.index.AccumulatingResultBuilder] Indexing failed for Issue - '16700'
2015-03-31 11:20:04,842 JiraImportTaskExecutionThread-1 WARN administrator 678x866x1 1c9z6p1 10.160.49.147 /secure/admin/XmlRestore.jspa [atlassian.jira.index.AccumulatingResultBuilder] com.atlassian.cache.CacheException: com.atlassian.cache.CacheException: com.atlassian.cache.CacheException: com.atlassian.util.concurrent.LazyReference$InitializationException: com.atlassian.util.concurrent.LazyReference$InitializationException: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'net.customware.plugins.connector.jira.issue.customfield.RemoteSystemIDCustomFieldType': Instantiation of bean failed; nested exception is org.springframework.beans.BeanInstantiationException: Could not instantiate bean class [net.customware.plugins.connector.jira.issue.customfield.RemoteSystemIDCustomFieldType]: Constructor threw exception; nested exception is java.lang.IllegalStateException: The default text renderer for Jira has been disabled, please re-enable the text renderer for correct funtioning to resume.

 

Rahul Aich [Nagra]

The best way for you to go forward would be to upgrade with no plugins in. It is more likely caused by a plugin rather than a custom field created by that plugin.

Once you have upgraded fine, you can then enable oneplugin at a time and seewhich one malfunctions.

 

Rahul