Hello together, the developers have committed now that indeed there is a library implemented in the application which causes the below discussed error. Something about a filter which uses a static component for URL and the passed username.
Just wanted to let you know. Uwe -----Ursprüngliche Nachricht----- Von: Hellmann, Uwe Gesendet: Donnerstag, 22. Dezember 2011 08:22 An: users@tomcat.apache.org Betreff: AW: AW: How much connections are handled per thread? Hello Chris, you helped me enough with all the infos or hints you and the other persons on this list have provided. I can't provide any code, because I am not allowed to do so. My work is to try to prove that it is not our infrastructure including tomcat which does create this issue. Until now I am not that firm in java-coding so I think searching in the applications code would be useless at least for me and it is not my job. Like I said before you all helped me much, now it is time for the developers to check. Kind regards any have a nice Christmas. Uwe -----Ursprüngliche Nachricht----- Von: Christopher Schultz [mailto:ch...@christopherschultz.net] Gesendet: Mittwoch, 21. Dezember 2011 16:41 An: Tomcat Users List Betreff: Re: AW: How much connections are handled per thread? -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Uwe, On 12/20/11 11:11 AM, uwe.hellm...@t-systems.com wrote: > I tried everything the last half year to convince him to switch to > current tomcat or at least to tomcat 6. It was a waste of energy. Tomcat 5.5 will experience EOL on 30 September 2012. So, they have about 9 months to get an upgrade into testing before they are flying without a parachute. Tell them that they can either upgrade while there is support for the older version, or wait until there is essentially no choice (some security bug found that will not be fixed) before making a hasty upgrade. > But on the other hand I have to prove that it is not tomcats > failure which causes this issues. *sigh* One cannot prove a negative. If Tomcat were exchanging parameter values between requests don't you think the entire world would fall apart? Given that only your webapp appears to be suffering from this problem, the logical conclusion is that the problem is in the webapp. I'm not saying there definitely is NOT a problem with Tomcat, but the odds are against Tomcat being the problem. You ave provided virtually no information across both of your discussion threads other than "we issue request to X and get no parameter value somewhere". We can't read your code. We can't read your mind. Given those circumstances, we cannot help you. If you want to send your developers here so they can give us more information, maybe we /can/ help. - -chris -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.17 (Darwin) Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk7x/fwACgkQ9CaO5/Lv0PB2vACdF1s7RIodWYCFY9LrbsPAqYG4 ktQAn1/fTYmH2zkY5LiIgnDK+E+iDkRc =ftTS -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
