On 12/21/2011 07:10 AM, huang kun wrote:
This is my MSM config:
I got a lot of "LockingStrategyAuto- Found no validity info for
session id " WARN, but my website seems OK.
Is the Found no validity WARN info is something wrong, or I could just
ignore it ?
To give you the context of the warning: for non-sticky sessions some
metadata is stored separately from the session. The metadata includes
e.g. the lastAccessedTime which is used to determine session
validity/timeout. The metadata is updated in memcached always, even if
the session itself has not been modified.
The warning "Found no validity info for session..." is logged at the end
of a request that didn't load the session (there was no
request.getSession()), when the validity info for this session could not
be found in memcached. One reason for this might be that the memcached
does not have enough memory assigned and therefore had to evict cache
entries. For this you should check your memcached config and memcached
stats (evictions particularly).
Do you have some knowledge about the sessions for that this was logged,
e.g. if they had just been created, how long they did already exist
etc.? Can you reproduce this issue?