Is "Action on Service Down - Reselect" ever safe for HTTP virtual servers? E.g., stateless transactions
I've been living the dream, learning about "Reselect Tries" and "Action on Service Down" ... We have web service interfaces that are stateless, from an HTTP perspective - no session is created on the web server side, etc. The goal is to have such calls never fail, as long as one web server (pool member) is up. Setting "Reselect Tries" > 0 accomplishes that for new connections - just looking to do the same for existing connections. Have been looking at "Action on Service Down" - but one thing I can't find clarified is, is a setting of "Reselect" ever safe for a Layer 7 HTTP virtual server? For example, if you know for a fact that your web servers are stateless (no user session involved on the server side, or all user state is written back to the client as cookies), then can reselect be safely used? I'm concerned about a race condition related to HTTP transactions that span multiple packets ... perhaps it's only safe if you know that all transactions will fit in a single packet? If it is safe under those constrained circumstances, is there any configuration guidance to be aware of? E.g., is it necessary to avoid use of a OneConnect or something? If it's not safe, can you explain why, where it breaks things? And, is there any approach that will accomplish what I've described? (maybe, some way to config so that every single transaction is treated like a completely new connection?) thx! We're on 11.5.2, if it's relevant.