Is Active Objects Caching Confluence cluster compatible?

[Ulrich Kuhnhardt [Comalatech]]

Hi Jason :)

We're investigating moving some data to A/O. The add-on in question is currently Confluence cluster compatible.

We need updates in A/O tables immediately available across all nodes. Does A/O caching support that? Could you (or anyone) elaborate how A/O caching works and how it can be configured.

Are A/O streaming and lazy loading affected/supported?

Thanks in Advance, appreciate your help.

Cheers Ulrich

[jhinch (Atlassian) · Accepted solution]

Depending on what version of ActiveObjects you are using, it may incorrectly cache entities in a thread local. That has been completely stripped out in 0.22 and above and there is no caching done. I know that Confluence continued to using the caching version for quite some time.

The caching done by AO is ineffective and incorrect. I would suggest calling ActiveObjects.flushAll() before interacting with AO on earlier versions.

In terms of cluster-safety, CRUD operations are cluster safe and will be mirrored across the cluster when the transaction commits. We are working on making the upgrade tasks also cluster safe so they only run once in the cluster. This should be available in a future release of Confluence.