0 Replies Latest reply on Jun 20, 2005 10:17 AM by Roland Räz

    No effect when defining session manager for non distributabl

    Roland Räz Newbie

      Why uses the TomcatDeployer the catalina StandardManager as the session manager for a not distributed web application, even if an other session manager has been defined?


      <Context path="/xxx" docBase="./deploy/clusteredservlet.war">
       <Manager className="org.apache.catalina.session.PersistentManager">
       <Store className="org.apache.catalina.session.StoneChisel" directory="./mySessions"/>

      <web-app id="WebApp_ID" version="2.4">

      By the above defined configuration the PersistentManager will not be used.

      The TomcatDeployer.performDeployInternal() correctly creates the in the context.xml defined session Manager at the beginning of the method. At the end of the method it gets overwritten by the StandardManager.
      Therefore any in the context.xml defined Manager has no effect.
      Is this behaviour wanted, or is it a bug?