Jadu support storing PHP session files in one of three locations:

  • on the file system
  • using memcached
  • in the database

For single server sites, storing session files on the file system (the PHP default) is generally fine. However, when multiple servers are deployed it is desirable for a user to have their session maintained regardless of the server that they access.

This can be achieved by storing sessions in the database or in memcached.

We do not recommend using Destination Address Affinity Persistence (often referred to as sticky sessions).

Storing session on the file system

This is the default storage option for a single server environment and is used by setting session.save_path in php.ini.


Storing sessions in memcached

It is possible to store sessions in memcached by changing the session.save_handler and session.save_path values in /etc/php.d/memcached.ini, for example:

session.save_handler = memcache
session.save_path = "tpc://server:port?persistent=1&weight=1&timeout=1

This is the preferred method of storing sessions across multiple servers with Continuum CMS.

Note: when sessions are stored in memcached, restarting memcached will terminate any active sessions.

Storing sessions in the database

Session data can be stored in the database by adding the constant USE_JADU_SESSION_HANDLER to <install_path>/config/constants.xml.

In this file add:


Sessions are stored within JaduPHPSessions database table.

Storing sessions in Redis

Its possible to store session information in Redis, however this has not been tested with Continuum CMS.

results matching ""

    No results matching ""