Hi Chris,
First, my apologies. Much of the terminology is
unfamiliar to me here. I hope that I've managed to fully answer your
questions.
The "server calls" are all rmi calls on java-based servers
on the same machine. There are no separate threads directly in the .jsp
pages.
The userToken
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Joel,
On 6/17/13 5:12 PM, joel wrote:
> Thanks for the help. I'm not an expert with tomcat management,
> There are no servlets. I don't know what Threadlocal,
> doGet/doPost/etc are, so presumably haven't used them.
Eventually, everything is a ser
Hi Chris,
Thanks for the help. I'm not an expert with tomcat
management, There are no servlets. I don't know what Threadlocal,
doGet/doPost/etc are, so presumably haven't used them. No references are
kept to request,response, session, or stream objects. At login, a user
session token is stored
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Joel,
On 6/17/13 12:01 PM, joel wrote:
> Thanks for the info! I'll look into making the upgrade.
>
> Can you advise how an application bug can cause this when
> restarting tomcat will fix it? That would help me wrap my mind
> around something that
Hi Mark,
Thanks for the info! I'll look into making the upgrade.
Can you advise how an application bug can cause this when restarting
tomcat will fix it? That would help me wrap my mind around something
that isn't imaginable, yet.
Thanks!
Joel
On 2013-06-17 10:46, Mark
Thomas wrote:
On 17/06/2013 16:32, joel wrote:
Hi,
I'm using Apache Tomcat/6.0.24 running on centos and have
several times observed a rare issue in which user sessions are "mixed".
When this occurs, userA clicks on a link and is provided with userB
specific content, content that should only be accessible to
Hi,
I'm using Apache Tomcat/6.0.24 running on centos and have
several times observed a rare issue in which user sessions are "mixed".
When this occurs, userA clicks on a link and is provided with userB
specific content, content that should only be accessible to userB. When
this "mixing" occurs
