You're visiting the Confluence Knowledge Base. Visit the Confluence Knowledge Base Home for an overview.

Skip to end of metadata
Go to start of metadata


Logs contain exceptions similar to this:


This is because Confluence's HTTP sessions may contain objects which cannot be serialized to disk. Tomcat tries to serialize existing sessions by default during shutdown.


You can add the following configuration parameter into Tomcat's server.xml file between the <Context> tags to disable this:

For more information regarding the saveOnRestart parameter, please refer to the Server Configuration Reference for the Manager Component.

Help us improve!

Is this article helpful?
Is it well written?
Is the content complete?





























  1. When would someone want to implement this configuration and when would they not (besides because they don't want to be "bothered" by this error message)?  What are the implications of using or not using this configuration setting?  For example, what is the implication of simply ignoring the error if it occurs verses using this configuration setting even if the error has not yet been seen?

    1. If you leave the default settings in place, you get the benefit of Tomcat saving your sessions on restart. The impact of enabling or disabling this feature is minimal as Confluence makes very sparing use of sessions. Hence our recommendation is that you should disable it and get the benefit of not having those errors in your logs. Our standalone distribution already has this feature disabled.


  2. Anonymous

    Wouldn't that not be in the server.xml, but rather in the specific .xml file in tomcat/conf/Catalina/localhost?

    1. Hi,

      Yes.You could specify,example the "context.xml" file in the $CATALINA_HOME/conf/Catalina/localhost/context.xml when you are installing Confluence EAR-WAR on Tomcat.


      <Context path="/confluence" docBase="c:/applications/confluence-2.1.3/confluence" debug="0" reloadable="false">
      <Manager className="org.apache.catalina.session.PersistentManager" saveOnRestart="false"/>

      It's advisable to configure at the conf/server.xml, since it's the main configuration file in the tomcat.

      Hope this information helps.


      1. Anonymous

        It's advisable to configure at the conf/server.xml, since it's the main configuration file in the tomcat. 

        If we are running other apps in a virtual host and we do want persistent management for them, then using the context for confluence would be the way - particularly when having to do a live-restart for some reason or what not....

        not everyone is running ONLY confluence. ^.^ 

  3. Anonymous

    Isn´t it better to use

        <Manager className="org.apache.catalina.session.StandardManager" pathname=""/>

    because of the warnings written here:

    Persistent Manager Implementation

    WARNING - Use of this Manager implementation has not been thoroughly tested, and should be considered experimental!

    1. Hi,

      Thanks for the suggestion. For your information, the Persistent Manager implementation have been tested by different users in Confluence and they seems to work fine. Having said that, using this implementation shouldn't be a problem in Confluence.

      Meanwhile, I have created an improvement request regarding adding further clarification which relates to the "PersistentManager" parameter. The improvement request can be accessed via:

      Feel free to add yourself as a watcher on the improvement above to get its updates.

      Choy Li