Hi,
So I think this is a thread/security issue, but I am not sure. However
it is definitely weird.
I have been conducting some tests with multiple users. Various servlets
are contacted that supply pages to each user, that include information
such as user name etc. The version of tomcat in use
26, 2001 11:18 AM
To: [EMAIL PROTECTED]
Subject: Weird thread/security problem
Hi,
So I think this is a thread/security issue, but I am not sure. However
it is definitely weird.
I have been conducting some tests with multiple users. Various servlets
are contacted that supply pages to each
]
Subject: Weird thread/security problem
Hi,
So I think this is a thread/security issue, but I am not sure. However
it is definitely weird.
I have been conducting some tests with multiple users. Various servlets
are contacted that supply pages to each user, that include information
Application wide content should be stored in the context, not as servlet
variables. This is because if the servlets are load balanced across
multiple jvms, or if servles implement the SingleThreadedModel then tomcat
will need to ensure that all instances of servlets on all jvms share the
one
Tomcat runs multiple individual threads per *request*, not per *user*.
99.9% of the time, this kind of thing is caused by application programming
errors related to threading. For example, if you use an instance variable
in a servlet to store information specific to a particular request, and
On Thu, 26 Jul 2001, Sam Joseph wrote:
I guess I have two options, either make the servlet implement the
SingleThreadModel interface, or create some new classes to encapsulate the
appropriate data, and either store that in the session or in some instance
variable like a hashtable ...
