On 20/12/2011 13:36, uwe.hellm...@t-systems.com wrote: > Hello together, > > just a short question. > Does a single Tomcat thread handle more than one connection at a time? (kind > of multiplexing)
No. > Is it possible that if there are more connections at a time per thread that > there is a bug that > a GET variable is exchanged between these connections? > > An example: > I have requested a page > http://myhost.de/action=login&user=username&pass= > > I send it away and because of a wrong pass Variable It returned the following > http://myhost.de/action=login&user=username&errorcode=1 The above doesn't make sense to me, can you explain it again please? > I can repeat that a hundred times and sometime It returns > > http://myhost.de/action=login&user=otherusername&errorcode=1 A connection is assigned to a thread. A thread may then access a Servlet. Servlet classes are not inherently thread-safe. If I understand your problem correctly (I'm not sure I do) this kind of error usually occurs because the developer has incorrectly stored some data as an instance field in a Servlet (or related subclass) and subsequent threads access the field causing it to mutate before the current thread finishes using it. p > Every other ideas are welcome. > > Kind Regards > Uwe > > > -- [key:62590808]
signature.asc
Description: OpenPGP digital signature
