Well, assuming you still want to confirm the real crux of your problem, I'll say again that it's not clear if you are saying that in testing replication (taking web sockets out of the equation), did your dump of the session tokens show that they were the same value, over multiple requests and within the two servers on which you were making the requests?
If they were not the same (within requests on one server), or between the two servers, that would explain why it would seem that replication was "failing". It could be that the sessions were replicated, but some other issue left you unable to access it in your requests. Just something to consider. As for proving whether the sessions were replicated (at all, whether you were able to access them), since you mention having the server monitor, you could look at its list of active sessions, and see if a given set of sessionids appears in the list of active sessions on both servers. If there wasn't a single one, then yes it would seem then that replication is not working. If there are matches, then it would seem sessions are being replicated, but then the next challenge is to be able to access them via your browser requests. But again, I'll understand if you're past the point of wanting to dig in further. /charlie -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Kier Simmons Sent: Wednesday, August 28, 2013 9:46 PM To: [email protected] Subject: RE: [Possible SPAM] RE: [houcfug] Using Websockets in a Clustered Environment We did indeed dump the session vars, the application vars, the cookie tokens, used j2ee, set a var one way of you hit one server first and another way of you hot the other. We also used the server monitor tools that allow you to track sessions and applications. What happened in one server in the cluster did not replicate to the other. We even started playing with serializing components. Once you get that complicated, or is better to use your own central data store. As for Web sockets, I'm probably just going to use firebase and be done with it. -- -- 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.
