If our servers are real busy and we have REPLY_ASYNC, could there be the potential that when redirected to a new server, the session will not be there by the time a request happens, causing a user to have the same sessionID but not the session data?
We have a HTTPS load balancer that decrypts and routes to 5 machines. I consistently have 2006-02-27 14:24:01,511 WARN [org.jboss.cache.TreeCache] node /JSESSION/localhost/ui/ghr3Zl589yxgKKGPzE6Z6g** not found in my logs (about 400 per day).
And each server has about 350 logouts per day because the session data is not available.

Does anybody else have this problem with their servers?