URGENT: Plugin update fails after upgrade to Confluence DC

[Yohaan Sunny]

Hi,

We have just setup Confluence DC on AWS using the CLoudFormation template provided by AWS.

Migrated our existing confluence site and restored our database backup as well. The Data Center is up and running with no issues.

However, only one issue remains. We cannot seem to update the plugins from the plugin manager.

Checking the atlassian-confluence.log file I can see the error pasted below:

[atlassian.confluence.cache.TransactionalCacheFactory] handleCacheSynchronizationFailure Could not synchronise transactional cache [com.atlassian.confluence.user.crowd.CachedCrowdUserDao.USER_CACHE]. Attempting flush instead.

Caused by: java.io.IOException: unexpected exception type

We are in the middle of the migration process so it is quite critical.

Can someone please help?

[AnnWorley · Accepted solution]

Hi Yohaan,

The error you are reporting doesn't seem related to updating plugins. So we can take a closer look, I opened a support request on your behalf. You should receive an email from our service desk shortly.

Thanks,

Ann

[Yohaan Sunny]

Hi Ann,

Thank you for responding.

It is resolved now. It looks like it was a bug. Logged in from a different system and it worked. Plugins have been updated. WIERD!

Still, would be good to know what this error log was for. Do you know what this error means? Just want to be certain before we go live with this.

[AnnWorley]

Hi Yohaan,

To find out what caused the error, please follow up with the support engineer who worked on your support request as they have a wider perspective from which to draw.

Thanks,

Ann

[Paul_Pagel]

I'm actually getting the same error on our recently migrated instance to Confluence DC:

2019-12-20 17:44:32,250 ERROR [Caesium-1-4] [atlassian.confluence.cache.TransactionalCacheFactory] handleCacheSynchronizationFailure Could not synchronise transactional cache [com.atlassian.confluence.user.crowd.CachedCrowdUserDao.USER_CACHE]. Attempting flush instead.

Could you please share some insight as to what causes this? There's multiple errors like this.