-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Clemens,
On 3/12/14, 1:34 PM, Clemens Wyss DEV wrote: >> By all means, post the relevant portion of the log file. > > I don't think this is of big help here. But you also don't know what you are doing. If you don't help us, we can't help you. Tomcat itself does not usually confuse requests in the way you describe, so the likely conclusion is that it is your web application. >> It would be very helpful if you'd answer my earlier question >> about how you take a request and route it to Velocity > > We put the request into the velocityContext and hence have the > possibility to access "whe(r|n)ever needed" Yes, but how do you build that? There are many ways to do it incorrectly, like inappropriately-sharing resources between threads, etc. that can lead to the situation you are describing. >> How do you know that the requests are coming from certain IPs and >> they are then being reported incorrectly in the access.log or in >> your own web pages. > > 1) in the access.log we see all requests 2) if a specific > monitoring-URL is called from our monitoring site (which's IP we > know ;) ), AND the IP does not "match the monitoring site", we > write out the remote IP into the app-log as an error > > Now if the load on our site is high (bots accessing) then we frm > time to time see these errors AND in the access.log we see that > reported IP matches "the request before the monitoring request" > (from the bot) > > Hope this helps It doesn't. You need to provide more real information instead of just saying "we know something is wrong; help us fix it". - -chris -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBCAAGBQJTIKDiAAoJEBzwKT+lPKRYqvAP/3SLGyn/ABzGYnuyks12Mfqt AUmBxUb3d/4EgccvkMIsjPI7FG8cSUQdRL9JCPosBUXCEoLfv0GMKK7KWe7S88dy VaPkFV+6kWlz2ou5m5Hhs89gGUDuVW6ENGhQSCq+qIGplBpf/PuLzwM5yfraZlCV fTpUgzSPXNTtJrK9rnAllqB2kvCVujpdvfw2/BAUuwa97v4pzdvyAeOKCN6kNVBy SAttVKul2ZC3LEhOasD8ygizf1EbsA1kIrlRHdDPWB6RwX+KU36SJPRrcnTDGkgD s02LyXPDyh9zKuj9eK90no+ZmEPJeJ4HNr//XVx8jaQIyvDOaGm9Br6ov7FPZDvj iMkaEMxeMrEkAfe+R6DvibMPHzrHEcbLUkfz6Lbjf4tooJjIClrYJf4DyAcys/6m b0HYFGwgNHKOEoBuHXJKfr9hvQhJB+Ig2XJwWqsWgwAJWlMcDjpV/36zyPLkIfRk BrjGoHhynk4F1Y87iwqlu6PBo0i1ZpD12njrScXQXxHdnc4xKWU18UETLs1M2M7l QnHmtEqIRHHntHsJeLaFGBTHy7tkZGSBJSqmKEx9EvVNHBRnLTa2mLIUIOQ+UMoj oNa+n25/wCy7kfX/ex8S3h5OcXs1V9EM/clV9oEJD6n1a8RU186WVTKsisoLCFIF Ci/6R1gZuqyR2JJAbP5C =KJXr -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
