Thanks for your answer and tips.
Gregor Schneider wrote:
Well, the exception looks like, as if somebody has tried to change the
name of the user-realm from
/srv/www/tomcat5/base/conf/tomcat-users.xml to
/srv/www/tomcat5/base/conf/tomcat-users.xml.new .
Do you have any idea where one would do that ?
I rather suspect that this is something that Tomcat does on its own,
although without inspecting the code it's difficult to tell.
But even if someone had modified this filename somewhere, fundamentally
it should not matter, should it ? I mean, as long as Tomcat can indeed
write this new file (and it should be able to, permissions-wise), it
should not produce an exception.
Part of the problem is that Tomcat here says there is an IO exception,
but is not very clear (at least to me) about what exception that is.
About the strange ways of packagers under the various Linuxes, I know
all about it. As I also know that one should preferably use the
Official Tomcat, and I would if I could.
But in this case I can't, for a number of reasons that it would be
tedious to re-expose. I have to live with what I get, even if that is a
Tomcat 5.0 running under an IBM JVM and with lots of strange links all
over the place.
I just know that
/srv/www/tomcat5/base/conf/tomcat-users.xml exists and is writeable
/srv/www/tomcat5/base/conf exists and is writeable
CATALINA_HOME is /usr/share/tomcat5
CATALINA_BASE is /srv/www/tomcat5/base
/srv/www/tomcat5/base/conf is a link to /etc/tomcat5/base, which exists
and is writeable
I also know that things do not change by themselves,
and I know that this Tomcat was running up until this morning when I
restarted it and when these strange messages first appeared in catalina.out.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
