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
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
Hello together,
just a short question.
Does a single Tomcat thread handle more than one connection at a time? (kind of
multiplexing)
Is it possible that if there are more connections at a time per thread that
there is a bug that
a GET variable is exchanged between these connections?
An
Thanks for the answer.
We have a test environment but there it isn't reproducible.
Just on the production system. But everything is configured identical.
We use Apache with mod_proxy (via AJP).
Only the connector? It is pretty standard.
Server port=8005 shutdown=SHUTDOWN
Listener
It is a webformular.
The java code should this fragment.
final String username = req.getParameter(username);
String uParam = ;
if (StringUtils.isBlank(username) == false) {
uParam = u=.concat(username);
}
logonFilter.setLoginFailedUrl(/action?login_error=1.concat(uParam));
It is Tomcat 5.5.26
summarize all information which I have gathered so far from your answers it
looks like a
problem which seem to occur trhough a not-thread safe implementation of a class
or the whole servlet?
If this is the case I get some munition to go the the developers.
Thanks for all
Yes you are completely right, but that is not my decision it is the customers.
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.
But on the other hand I have to prove that it is not tomcats failure which
causes
us everything is fine.
Mit freundlichen Grüßen / Yours sincerely
Uwe Hellmann
T-Systems International GmbH
Production CSS
GCU Large Accounts
AC Express Logistics LT1
Gradestr. 20, 30163 Hannover
+49 511 333 - 1233 (Tel.)
+49 511 333 - 1287 (Fax)
Email: uwe.hellm...@t
freundlichen Grüßen / Yours sincerely
Uwe Hellmann
T-Systems International GmbH
Production CSS
GCU Large Accounts
AC Express Logistics LT1
Gradestr. 20, 30163 Hannover
+49 511 333 - 1233 (Tel.)
+49 511 333 - 1287 (Fax)
Email: uwe.hellm...@t-systems.commailto:uwe.hellm...@t-systems.com
Internet
have a clue? Or do you need some more info?
Thanks in advance.
Mit freundlichen Grüßen / Yours sincerely
Uwe Hellmann
T-Systems International GmbH
Production CSS
GCU Large Accounts
AC Express Logistics LT1
Gradestr. 20, 30163 Hannover
+49 511 333 - 1233 (Tel.)
+49 511 333 - 1287 (Fax)
Email
Hello
Thanks for the info, I checked it. There are many entries for
servlet-nameManager/servlet-name
in webapps/manager/WEB-INF/web.xml.
But I checked in original file from tomcat.apache.org and there it is also more
from them. So this could not be the failure
hence it runs under one instance
there are no entries for servlet-nameManager/servlet-name
currently with the exception of the defined ports in server.xml these tomcats
are running with default settings.
-Ursprüngliche Nachricht-
Von: Konstantin Kolinko [mailto:knst.koli...@gmail.com]
Gesendet: Dienstag, 30. August
thank you very much for your help.
I have found the problem. it was no real tomcat problem.
by accident I had copied the manager web.xml to a wrong destination so tomcat
assumed that is has to start another application
with it.
- Uwe
-Ursprüngliche Nachricht-
Von: Hellmann, Uwe
13 matches
Mail list logo
