one of our service has problem:

on server site, there is warning messages same as below:

BEA-100089

Warning: The session id: sessionID has been accessed from currentServer, a server that is neither the primary (primaryServer) nor the secondary (secondaryServer). The request URL was: requestUrl

Description

The session id: sessionID has been accessed from currentServer, a server that is neither the primary (primaryServer) nor the secondary (secondaryServer). Repeated occurrences of this can cause memory problems and performance degredation, as sessions are loaded into memory on more than two servers at a time.

Cause

The most likely cause is a configuration error on a front end hardware loadbalancer or webserver plugin. They should be configured to respect the values of primary/secondary in the cookie (i.e., stickyness), when possible.

Action

Please ensure that the front end webserver or load-balancer has been properly configured.

I have been adviced that I need increase idle timeout.

but, I still do not understand this problem should increase idle timeout or stickness timeout?

if it is idle timeout, the server is 3 min, but, I looked CSS default, it only 8 second, so, do I cause any problem if I increase to 3 min?

If it is stickness inact timeout, server site has not document about it, how many I should set?

my configuration is:

content myservice-80

vip address 10.1.1.10

port 80

protocol tcp

balance leastconn

advanced-balance arrowpoint-cookie

add service myservice-myhost1-80

add service myservice-myhost2-80

active

service myservice-myhost1-80

ip address 10.2.2.11

protocol tcp

port 80

keepalive type http

keepalive uri "/webct/checkStatusForLb"

keepalive frequency 30

active

Any comments will be apprecaited

Thanks in advance