Hello,
I've noticed today quite a disturbing bug in the 5.0.x series, x <= 27
(I haven't tested this on more recent versions).
I've inadvertently put wrong permissions on a directory which tomcat
needed to traverse at startup time in order to load. As a result, I
got a very confusing "IllegalArgumentException" followed by 'Caused
by: java.lang.FileNotFoundException: no such file or directory'.
Uh. I couldn't make the sense out of it for a good 15 minutes until I
decided to strace the thing and see what was going on. And oh
surprise, what was happening was then much, much clearer:
open("/the/culprit/jar", O_RDONLY) == -1 (EACCESS)
The bug is: why on earth didn't Tomcat output such a simple,
meaningful error message instead of particularly irrelevant exceptions
in this case? I was afraid at a point that a jar was just corrupt or
something, but no, it was as simple as a chmod o+rx on a directory...
--
Francis Galiegue, [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED]
One2team - 12bis rue de la Pierre Levée, 75011 Paris - 0143381980
"When it comes to performance, weight is everything" - Tiff Needell
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
