Yes, this would have to do with your server setup. Your load balancer is
not keeping your session on the same server.
As stated in the docs, redirect persist uses the application or session
scope to store a temporary copy of the data. The key in the URL is used
to retrieve it. If your load balancer is not acting correctly,
sometimes you will be routed to server B when your session actually
lives on server A.
You don't have to worry about sticky sessions in CF's clustering (which
you indicated you can't do)...all arrows point to an incorrectly
configured load balancer.
.Peter
jbuda said the following on 11/24/2009 03:58 AM: