Could it have to do with caching or some other lingering stuff? Maybe it's not failing on the client-side, but somewhere on the server-side, displaying the wrong content because of... cached SQL responses, or wrongly scoped variables?
The variable thing sounds plausible, if user A does something that sets a global variable, user B then sees the same thing? On Tuesday, June 24, 2014 6:15:39 PM UTC-5, Rawk wrote: > > There was a reason I wasn't using J2EE sessions, but I can't recall that > reason anymore. I might have to give that a try. > > Sometimes they'll copy/paste the page to me, but it doesn't seem > page-specific at all. And the page they send me is just someone else's > page. Sometimes it happens to me, so I'll reload the same a random page > over and over and each page load is basically showing me the last page that > a user experiencing the same issue is seeing (not the URL I'm reloading). > I'll then tell that user to log out, and through my page reloading it will > take me to login page as soon as the user logs out. > > It's hard to make sense of. Next time this happens to me, I should video > record my desktop so can show everyone. > > On Tuesday, June 24, 2014 7:05:03 PM UTC-4, Marcus F wrote: >> >> J2EE sessions should actually help, if I remember right J2EE sessions are >> automatically cleared when the browser closes. >> >> I can't think of many ways that would result in session-leakage. >> >> Are your users reporting exactly on what pages it's happening? >> >> On Tuesday, June 24, 2014 5:41:20 PM UTC-5, Rawk wrote: >>> >>> Ugh. So I went through all my code and updated my CFLOCATION tags >>> immediately after I my last post in this thread. I also restarted the >>> server. >>> >>> Since then, I have received reports from 3 users that the issue has >>> cropped up again. >>> >>> Any other ideas how users might be sharing their sessions? The tokens >>> never appear in the URL through use of my app, so there's no way my users >>> are copy/pasting URLs containing tokens to each other. >>> >>> I have also determined that sometimes the users see the session that is >>> used either by Task Scheduler or a WGet script that runs in a loop on the >>> server. In brief, the WGet script is designed to work as a process queue >>> in order to break up large processes into smaller chunks and execute them >>> sequentially. This allows me the server to handle processes that take an >>> abnormal amount of time to execute without the server stopping execution >>> due to timeouts. >>> >> -- -- online documentation: http://openbd.org/manual/ http://groups.google.com/group/openbd?hl=en --- You received this message because you are subscribed to the Google Groups "Open BlueDragon" 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/d/optout.
