Error creating bean with name 'cacheFactory' in JIRA

Edit by Adrien: Since the question was posted without a body, I took the liberty of filling in the symptoms.


If a plugin needs a cache, the Atlassian documentation advises to import following, which doesn't work:

<component-import key="cacheFactory" interface="com.atlassian.cache.CacheFactory" />

The plugin installation fails with the following messages:

Plugin 'com.[...]' never resolved service '&cacheFactory' with filter '(objectClass=com.atlassian.cache.CacheFactory)'

How to use the cache in JIRA?

3 answers

1 accepted

This widget could not be displayed.
Chris Fuller Atlassian Team Mar 31, 2015

As Nic said, you haven't given us much to work with, but I'll take a wild stab...

For historic reasons, JIRA exports the heavier CacheManager interface instead of the nice, thin CacheFactory.  It really shouldn't do this, because CacheManager has management interfaces that plugins have no business using, like flushing all of the caches, but it's what we did so it's here to stay for the time being.

This may make it harder for the plugin system to resolve it as a CacheFactory, particularly if you are using the atlassian-cache-compat for cross-version compatibility or have made your plugin "transformerless".

  • If you are just trying to use a CacheFactory, try using CacheManager instead to see if that resolves it.
  • If you are trying to use the compatibility library, take a look at https://bitbucket.org/cfuller/atlassian-scheduler-compat-example for an example of using it
  • If it is somebody else's plugin, check that it is listed as compatible with the version of JIRA you are using

 

 

tick tl;dr: Replace CacheFactory with CacheManager (even though the former has @PublicApi and the latter @Internal, yes)

<component-import key="cacheFactory" interface="com.atlassian.cache.CacheManager" />
This widget could not be displayed.

Might need a bit more detail on this one...

This widget could not be displayed.
Chris Fuller Atlassian Team Feb 09, 2016

@Adrien Ragot (Play SQL / CYO): "... the Atlassian documentation advises ..."

Could you provide a link to the documentation that you're speaking of?  The only example of that I have been able to find was in the documentation for Stash add-on developers, and it actually works there because they were not burdened with this historical usage and chose to register it in the container properly.

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted Tuesday in Jira

What modern development practices are at the heart of how your team delivers software?

Hey Community mates! Claire here from the Software Product Marketing team. We all know software development changes rapidly, and it's often tough to keep up. But from our research, we've found the h...

220 views 1 3
Join discussion

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you