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 ...
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
acce
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 obje
ursday, July 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
Hi,
Application-wide data (within a container in the case of balanced servers)
can be put in instance variables, but access must then be synchronized.
User-related data must be put in the session object...
Regards,
Francis Pallini
At 06:18 PM 7/26/01 +0900, you wrote:
>Hi,
>
>So I think this
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
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
