in Confluence log" printError The response from one or more JIRA instances cannot be parsed."

[DI2E Licensing]

Any idea what might be causing this error found in my confluence log?

It's popping up frequently pointing to two different confluence pages, neither of which have any apparent link to JIRA whatsoever.  In fact there aren't even any macros on those two pages.

printError The response from one or more JIRA instances cannot be parsed.
com.atlassian.confluence.plugins.metadata.jira.exception.JiraMetadataException: java.lang.ClassCastException
	at com.atlassian.confluence.plugins.metadata.jira.aggregate.JiraAggregateProvider.parse(JiraAggregateProvider.java:248)
	at com.atlassian.confluence.plugins.metadata.jira.aggregate.JiraAggregateProvider.getDataForSingleApplink(JiraAggregateProvider.java:108)
	at com.atlassian.confluence.plugins.metadata.jira.aggregate.JiraAggregateProvider.access$100(JiraAggregateProvider.java:41)
	at com.atlassian.confluence.plugins.metadata.jira.aggregate.JiraAggregateProvider$1.call(JiraAggregateProvider.java:92)
	at com.atlassian.confluence.plugins.metadata.jira.aggregate.JiraAggregateProvider$1.call(JiraAggregateProvider.java:77)
	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
	at java.lang.Thread.run(Thread.java:745)
Caused by: java.lang.ClassCastException

Thanks!

[Remo Siegwart]

We saw the same error in our Confluence log after upgrading JIRA to version 7.0.10. Updating the JIRA Metadata Plugin in Confluence to version 1.7.14 fixed it for us.

See also the following knowledge base article: Error 'cannot be cast to com.google.gson.JsonArray' showing in Confluence logs after upgrading to JIRA 7

Hope this helps.

[Stefan Hett]

Started getting the same error today after we upgraded from Confluence 5.4.4 to Confluence 5.5.7 (including manually upgrading the JIRA macro plugin to the latest one aka: 5.6.17).

[Luc Filion]

We have the same error here, seemed to be caused by a JSON translation somehow. However, I noticed it does that when I save I a Confluence Template containing a variable ($var) in it. If I remove the variable, it can properly save the page. Can you retry on your side and see if you get the same behavior?

Confluence 5.8.5

2015-11-05 11:22:41,831 ERROR [JIRAMetadataPlugin_aggregate:thread-8] [metadata.jira.helper.JiraMetadataErrorHelper] printError The response from one or more JIRA instances cannot be parsed.
-- referer: http://blabla.com:8090/confluence/pages/editpage.action?pageId=4390946 | url: /confluence/display/REQ/Requirement | userName: lfilion | action: viewpage | page: 4390946
com.atlassian.confluence.plugins.metadata.jira.exception.JiraMetadataException: java.lang.ClassCastException: com.google.gson.JsonObject cannot be cast to com.google.gson.JsonArray
at com.atlassian.confluence.plugins.metadata.jira.aggregate.JiraAggregateProvider.parse(JiraAggregateProvider.java:248)
at com.atlassian.confluence.plugins.metadata.jira.aggregate.JiraAggregateProvider.getDataForSingleApplink(JiraAggregateProvider.java:108)
at com.atlassian.confluence.plugins.metadata.jira.aggregate.JiraAggregateProvider.access$100(JiraAggregateProvider.java:41)
at com.atlassian.confluence.plugins.metadata.jira.aggregate.JiraAggregateProvider$1.call(JiraAggregateProvider.java:92)
at com.atlassian.confluence.plugins.metadata.jira.aggregate.JiraAggregateProvider$1.call(JiraAggregateProvider.java:77)
at java.util.concurrent.FutureTask.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Caused by: java.lang.ClassCastException: com.google.gson.JsonObject cannot be cast to com.google.gson.JsonArray
at com.google.gson.JsonObject.getAsJsonArray(JsonObject.java:178)
at com.atlassian.confluence.plugins.metadata.jira.aggregate.JiraAggregateProvider.parse(JiraAggregateProvider.java:223)
... 8 more

I reported it  https://jira.atlassian.com/browse/CONF-39822

Luc from Nuum Solutions

[IshanL]

any idea? I also see this in our logs

[Illingus]

Same issue here, it completely pollutes the log file :(