Hey Charlie, sorry for the late response. I work with Kier, and was/am doing a large part of the testing. In case it wasn't mentioned, we are not using Sticky Sessions, because doing so does not allow for persistent session variables in the case of a server failure. We are using J2EE sessions which is required for ColdFusion 10 session replication across clustered servers.
We did in fact take a look at the list of active sessions for both servers, and the application instance only existed on one of the two servers (whichever was being hit at the time). So there was no communication between the two servers that a session had been created and that it should be replicated. Server fail over was working in that if one server went down, the other would take over, but the session ID and variables were not persistent (the session ID changed, and session variables cleared). What aggravates me is that the documentation from Adobe is so incredibly insufficient for what is to be expected from session replication, how to test it, how the servers must be configured, etc. At this point, I don't know whether it's not working because the servers aren't configured correctly, or if I'm just testing it improperly. I'd be willing to test the session replication again, but I would need to know that I'm either A) Testing it properly, or B) The servers are configured correctly. Trying to test one of the two without knowing that the other is correct is excruciating. I really appreciate any help or input. -- -- You received this message because you are subscribed to the "Houston ColdFusion Users' Group" discussion list. To unsubscribe, send email to [email protected] For more options, visit http://groups.google.com/group/houcfug?hl=en --- You received this message because you are subscribed to the Google Groups "Houston ColdFusion Users' Group" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
