Clustered Confluence Remote API Session Expires After 30 Minutes
This article applies to Confluence clustered 5.4 or earlier.
Symptoms
When using remote API scripts against a Confluence cluster, the session is expired after 30 minutes.
The following appears in the atlassian-confluence.log
:
Remote error: com.atlassian.confluence.rpc.InvalidSessionException: User not authenticated or session expired. Call login() to open a new session
Cause
There is a token cache that is set to expire in 30 minutes by default.
Resolution
- Locate and open the following file in a text editor: <confluence_home>/config/confluence-coherence-cache-config-clustered.xml
Find the following section:
<replicated-scheme> <scheme-name>cache:com.atlassian.confluence.rpc.auth.TokenAuthenticationManager.tokens</scheme-name> <scheme-ref>default</scheme-ref> <backing-map-scheme> <local-scheme> <scheme-ref>local:default</scheme-ref> <high-units>5000</high-units> <expiry-delay>1800s</expiry-delay> </local-scheme> </backing-map-scheme> </replicated-scheme>
- Edit the
expiry-delay
value as appropriate. Default is 1800 seconds (30 minutes).
Last modified on Mar 30, 2016
Powered by Confluence and Scroll Viewport.