> From: Yefym Dmukh [mailto:[EMAIL PROTECTED] > Subject: Tomcat 5.0.5 threads + log4j Mapped Diagnostic > Contexts. Simultaneous clients access problem. > > "In a typical multithreaded implementation of such a > system, different threads will handle different clients."
This is only true at a single point in time. > The tests showed that two clients not necessarily become the > different threads. Quite often the thread, taken by the client > A is shared later with the client B and afterwards is used > again by the client A. Normal and expected behavior. Tomcat (like most other servers) maintains a pool of threads, any of which can be used to service any particular request. There is no correlation between threads and sessions. If you have session-specific data, store it in the session; if it's request-specific, keep it with the request. Synchronization is important when dealing with the session. - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
