It is possible that Tomcat resuses request objects. I'm not sure it does, but it might. For that reason, you're only allowed to use the request object in your servlet's doGet or doPost method, you can't stash it somewhere (e.g. in the HttpSession) and access it later. (This is mentioned in the servlet spec.) Of course I don't know if that's your problem, it's just something that came to mind. -- Len
On 5/28/07, Dejan Krsmanovic <[EMAIL PROTECTED]> wrote:
We have two applications running on the same Tomcat instance. These two applications are used by completely different people and one of them has much higher traffic than another one. Recently we have upgraded to Tomcat 6.10 and start experiencing strange behavior. After a lot of debugging, we have noticed that the first application sometimes receives request parameters sent to second application. Parameters are mixed-up, that is, request.getParameterMap() returns parameters from both applications. This is not happening all the time (probably because one of these applications is used rarely), but we had this situation several times a day. After some time we have decided to return back to Tomcat 5.5.x and the problems stopped. What can be reason for such problems? Is it possible that Tomcat re-uses some objects internally without clearing them up? Regards, Dejan --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
