persist based on cookie with URI pools

Yes that is the standard reason, which escaped me, which is why I always use simple persistence as a backup in case the cookie fails, but doesn't always work.

 

 

At any rate, the problem is the nodes have to be the same for the JSessionID to work, match across pools should preserve the JSessionID in the header, if you use the profile that I suggested earlier, if not, then you have the issue of trying to keep track of the SessionID.