"Ambiguous write methods" warning after upgrading Confluence

Description

When we upgrade Confluence from 5.5.x to 5.10.x, Confluence logs a Warning regarding ambiguous write methods every time the application starts.

This bug was first observed upgrading Confluence from 5.5.3 to 5.10.6

Steps to reproduce;

1. Install a fresh Confluence 5.5.3;
2. Add some page to make sure it's working;
3. Upgrade to Confluence 5.10.x
4. Check atlassian-confluence.log

Expected result
Upgrade process starts with no warnings

Actual Result

• Stopping Confluence 5.5.3

  2017-01-30 15:51:58,940 INFO [localhost-startStop-2] [com.atlassian.confluence.lifecycle] contextDestroyed Stopping Confluence
  

• Starting 5.10.8 to upgrade

  2017-01-30 16:34:58,521 INFO [localhost-startStop-1] [com.atlassian.confluence.lifecycle] contextInitialized Starting Confluence 5.10.8 [build 6441 based on commit hash 82994790ee2f720a5ec8daf4850ac5b7b34d2194]
  2017-01-30 16:35:00,538 INFO [localhost-startStop-1] [springframework.web.context.ContextLoader] initWebApplicationContext Root WebApplicationContext: initialization started
  2017-01-30 16:35:03,158 INFO [localhost-startStop-1] [com.atlassian.confluence.lifecycle] <init> Loading EhCache cache manager
  

• Ambiguous write methods message right before starting

  2017-01-30 16:35:04,268 WARN [localhost-startStop-1] [org.springframework.beans.GenericTypeAwarePropertyDescriptor] getWriteMethodForActualAccess Invalid JavaBean property 'cacheFactory' being accessed! Ambiguous write methods found next to actually used [public void com.atlassian.confluence.spaces.persistence.dao.hibernate.HibernateSpaceDao.setCacheFactory(com.atlassian.vcache.VCacheFactory)]: [public void com.atlassian.confluence.core.persistence.hibernate.VersionedHibernateObjectDao.setCacheFactory(com.atlassian.cache.CacheFactory)]
  2017-01-30 16:35:12,609 INFO [localhost-startStop-1] [springframework.web.context.ContextLoader] initWebApplicationContext Root WebApplicationContext: initialization completed in 12070 ms
  

Workaround

No workaround found yet.