Summary: | Tomcat loses request parameters | ||
---|---|---|---|
Product: | Tomcat 5 | Reporter: | Thiago Costa <thiagocosta> |
Component: | Catalina | Assignee: | Tomcat Developers Mailing List <dev> |
Status: | RESOLVED FIXED | ||
Severity: | critical | ||
Priority: | P2 | ||
Version: | 5.5.9 | ||
Target Milestone: | --- | ||
Hardware: | PC | ||
OS: | Windows XP |
Description
Thiago Costa
2006-11-01 04:29:15 UTC
I suppose the logical conclusion would be to look why the flag is false, rather than resort to hacking. Most likely you are seeing concurrent access to the request object. (In reply to comment #1) > I suppose the logical conclusion would be to look why the flag is false, rather > than resort to hacking. Most likely you are seeing concurrent access to the > request object. But i´m an user and not a developer. As an user i cant do nothing to resolve the problem. As i observe, the recycle must set to false! There is a finally clause that force the recycle! I supose that or the recycle may throw an exception or an other process is accessing the request object. A new request object is generated for each request. Therefore, the only ways I can for what you report to happen are: - Multiple threads trying to read the parameters at the same time. This isn't something any of the internal Tomcat code does. - An exception during the parameter processing. I have added additional logging if the parameter processing fails to SVN and this will be included in 5.5.21 onwards. If you still see this problem post 5.5.21 and there is no helpful information in the logs, please re-open and provide a test case so I can investigate further. |