You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by André Warnier <aw...@ice-sa.com> on 2008/12/28 14:01:49 UTC
Sudden and unexpected exception at Tomcat startup
Hi.
Does someone have an idea of what is going as per the logfile
catalina.out below ?
What is this IOException all about ?
This is a Tomcat 5.0.x under Suse Enterprise Linux 10.1, which had been
working fine until now and suddenly logs this at startup.
This Tomcat runs under an IBM JVM 1.5.
Tomcat is started, as per the listening ports and the "ps" display I can
see, but apparently the access to Tomcat (through Apache and mod_jk)
does not work anymore (tells me : The server is temporarily unable to
service your request due to maintenance downtime or capacity problems.
Please try again later. )
Additional info :
- the directory /srv/www/tomcat5/base/conf/ is writeable by the user
"tomcat" under which Tomcat is started.
- To my knowledge, the server.xml has not been changed since the
previous succesful restart 2 days ago, and neither has tomcat-users.xml
server.xml (excerpts) :
...
<!-- Editable user database that can also be used by
UserDatabaseRealm to authenticate users -->
<Resource name="UserDatabase" auth="Container"
type="org.apache.catalina.UserDatabase"
description="User database that can be updated and saved">
</Resource>
<ResourceParams name="UserDatabase">
<parameter>
<name>factory</name>
<value>org.apache.catalina.users.MemoryUserDatabaseFactory</value>
</parameter>
<parameter>
<name>pathname</name>
<value>conf/tomcat-users.xml</value>
</parameter>
</ResourceParams>
...
(further under <Engine> and <Host> :)
<Realm className="org.apache.catalina.realm.UserDatabaseRealm"
debug="0" resourceName="UserDatabase"/>
...
catalina.out :
2008-12-28 13:21:58,543 [main] INFO
org.apache.catalina.core.StandardService - Starting service Catalina
2008-12-28 13:21:58,545 [main] INFO
org.apache.catalina.core.StandardEngine - Starting Servlet Engine:
Apache Tomcat/5.0
2008-12-28 13:21:58,548 [main] WARN org.apache.naming.NamingContext -
Unexpected exception resolving reference
java.io.IOException: IOException writing to
/srv/www/tomcat5/base/conf/tomcat-users.xml.new
at
org.apache.catalina.users.MemoryUserDatabase.save(MemoryUserDatabase.java:495)
at
org.apache.catalina.users.MemoryUserDatabaseFactory.getObjectInstance(MemoryUserDatabaseFactory.java:98)
at
org.apache.naming.factory.ResourceFactory.getObjectInstance(ResourceFactory.java:129)
at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:316)
at org.apache.naming.NamingContext.lookup(NamingContext.java:791)
at org.apache.naming.NamingContext.lookup(NamingContext.java:151)
at
org.apache.catalina.realm.UserDatabaseRealm.start(UserDatabaseRealm.java:252)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1075)
at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:478)
at org.apache.catalina.core.StandardService.start(StandardService.java:480)
at org.apache.catalina.core.StandardServer.start(StandardServer.java:2313)
at org.apache.catalina.startup.Catalina.start(Catalina.java:556)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:618)
at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:287)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:425)
javax.naming.NamingException: IOException writing to
/srv/www/tomcat5/base/conf/tomcat-users.xml.new
at org.apache.naming.NamingContext.lookup(NamingContext.java:803)
at org.apache.naming.NamingContext.lookup(NamingContext.java:151)
at
org.apache.catalina.realm.UserDatabaseRealm.start(UserDatabaseRealm.java:252)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1075)
at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:478)
at org.apache.catalina.core.StandardService.start(StandardService.java:480)
at org.apache.catalina.core.StandardServer.start(StandardServer.java:2313)
at org.apache.catalina.startup.Catalina.start(Catalina.java:556)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:618)
at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:287)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:425)
2008-12-28 13:21:58,549 [main] ERROR
org.apache.catalina.startup.Catalina - Catalina.start:
LifecycleException: No UserDatabase component found under key UserDatabase
at
org.apache.catalina.realm.UserDatabaseRealm.start(UserDatabaseRealm.java:259)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1075)
at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:478)
at org.apache.catalina.core.StandardService.start(StandardService.java:480)
at org.apache.catalina.core.StandardServer.start(StandardServer.java:2313)
at org.apache.catalina.startup.Catalina.start(Catalina.java:556)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:618)
at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:287)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:425)
2008-12-28 13:21:58,550 [main] INFO
org.apache.catalina.startup.Catalina - Server startup in 105 ms
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Sudden and unexpected exception at Tomcat startup
Posted by Gregor Schneider <rc...@googlemail.com>.
André,
it lookes as if Tomcat indeed tries to write to a file
tomcat-users.xml.new as indicated in this thread:
http://mail-archives.apache.org/mod_mbox/tomcat-users/200508.mbox/%3C4381.80.136.127.17.1122968130.squirrel@mailserver.kippdata.de%3E
That's really new to me, and I don't see any sense, but let's take it
as a fact now.
- Are you running Tomcat native or are you using startup.sh?
- Is it possible that you post your startup-script here?
- Do those staements work?
su tomcat
echo "fubar" > /srv/www/tomcat5/base/conf/tomcat-users.xml.new
If writing to a file is not possible, it's usually a rights-problem.
If this happens without having changed anything, you might want to
check the healthyness of your harddisk...
Gregor
--
just because your paranoid, doesn't mean they're not after you...
gpgp-fp: 79A84FA526807026795E4209D3B3FE028B3170B2
gpgp-key available @ http://pgpkeys.pca.dfn.de:11371
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Sudden and unexpected exception at Tomcat startup
Posted by André Warnier <aw...@ice-sa.com>.
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-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Sudden and unexpected exception at Tomcat startup
Posted by Gregor Schneider <rc...@googlemail.com>.
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 .
AFAIK Tomcat will never ever change configuration-files, except
creating new context-definitions when deploying an application
containing one in META-IF.
The next sentence is just a shot from the hip, and maybe I'm wrong,
but it might be worth a try if you're out of any other ideas:
Looking back, I recall that Suse is very special with the installation
of some programs - meaning, sometimes Suse duplicates
configuration-files on places where you'd never expect them. Worse,
when you change a configuration-file in their original location, Suse
sometimes just doesn't care and copies the old copy over new new
version.
I guess that you've installed Tomcat from the Suse repositories using
something like Yast, right?
Just to be on the fase side, try the following (as root):
find / -type f -name server.xml -print
Maybe Suse keeps a copy in some hidden place and is using this one.
To me, according to your description above, it looks pretty much as if
the server.xml is not read by Tomcat but another file.
Btw., what gives "echo ${CATALINA_HOME} ${CATALINA_BASE}" ?
On your box, do you have a directory "/usr/share/tomcat" containing
something like "config"?
Maybe one hint for the future:
It's strongly recommended using a vanilla installation of Tomcat, and
not the one fro the OS-repositories: It's easier to maintain when
sticking to the documentation, it's easier to apply updates, you'll
get updates faster and so on..
HTH
Gregor
--
just because your paranoid, doesn't mean they're not after you...
gpgp-fp: 79A84FA526807026795E4209D3B3FE028B3170B2
gpgp-key available @ http://pgpkeys.pca.dfn.de:11371
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Sudden and unexpected exception at Tomcat startup
Posted by Gregor Schneider <rc...@googlemail.com>.
Hi André,
good to hear that you got the issue solved.
On Mon, Dec 29, 2008 at 10:55 AM, André Warnier <aw...@ice-sa.com> wrote:
>
> If anything, I feel that the log message is not very clear :
>
> 2008-12-28 13:21:58,548 [main] WARN org.apache.naming.NamingContext -
> Unexpected exception resolving reference
> java.io.IOException: IOException writing to
> /srv/www/tomcat5/base/conf/tomcat-users.xml.new
well, what do you expect Tomcat (or Java) to do here?
The Java-Runtime throws an exception that writing is not possible and
delegates the exception to Tomcat.
What should Tomcat do without the appropriate information?
The only solution would be to enhance the Java Runtime to give a more
talkative Exception, however, that's a Java - not a Tomcat-issue.
Cheers
Gregor
--
just because your paranoid, doesn't mean they're not after you...
gpgp-fp: 79A84FA526807026795E4209D3B3FE028B3170B2
gpgp-key available @ http://pgpkeys.pca.dfn.de:11371
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Sudden and unexpected exception at Tomcat startup
Posted by André Warnier <aw...@ice-sa.com>.
Alan Chaney wrote:
[...]
Hi.
I found the reason, and apologise for waisting everyone's time.
Thanks for the tips anyway, they helped.
It was a simple diskspace issue.
Unknown to me, someone created a huge backup file in the directory /mnt,
part of the "/" filesystem, and filled up this filesystem.
On the other hand, as mentioned in my posts, the "conf" directory of
Tomcat (where tomcat-users.xml lives) is in reality linked to
/etc/tomcat5, also under "/".
Thus when Tomcat during startup tried to rewrite tomcat-users.xml
(apparently first as tomcat-users.xml.new, which was also something I
did not know), it encountered a full disk and got the IO Exception.
If anything, I feel that the log message is not very clear :
2008-12-28 13:21:58,548 [main] WARN org.apache.naming.NamingContext -
Unexpected exception resolving reference
java.io.IOException: IOException writing to
/srv/www/tomcat5/base/conf/tomcat-users.xml.new
at
org.apache.catalina.users.MemoryUserDatabase.save(MemoryUserDatabase.java:495)
at
...
a simple mention of "no space left on device" or something would have
saved a lot of looking at permissions, config changes, etc..
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Sudden and unexpected exception at Tomcat startup
Posted by Alan Chaney <al...@compulsivecreative.com>.
Hi Andre
Tomcat DOES in fact rewrite the tomcat-users.xml file during startup.
This has been mentioned on this list several times as being insecure but
the general opinion is that you should not be using the
MemoryUserDatabaseRealm in production.
Actually, I found that not only does it rewrite it, but it also uses the
current umask so that it is quite likely that the file will become
world-readable. You should probably do what the gurus suggest and switch
to a more robust realm (eg JDBC etc)
Here are some suggestions you have probably already tried:
What are the permissions on the /svr/www/tomcat/base/conf folder?
Are you sure that the user that tomcat runs as can write to that folder?
Have you checked that tomcat is running as the user that you expect?
Is it possible that there is a filing system error or even a disk error?
Regards
Alan Chaney
André Warnier wrote:
> Hi.
>
> Does someone have an idea of what is going as per the logfile
> catalina.out below ?
> What is this IOException all about ?
>
> This is a Tomcat 5.0.x under Suse Enterprise Linux 10.1, which had been
> working fine until now and suddenly logs this at startup.
> This Tomcat runs under an IBM JVM 1.5.
>
> Tomcat is started, as per the listening ports and the "ps" display I can
> see, but apparently the access to Tomcat (through Apache and mod_jk)
> does not work anymore (tells me : The server is temporarily unable to
> service your request due to maintenance downtime or capacity problems.
> Please try again later. )
>
>
> Additional info :
> - the directory /srv/www/tomcat5/base/conf/ is writeable by the user
> "tomcat" under which Tomcat is started.
> - To my knowledge, the server.xml has not been changed since the
> previous succesful restart 2 days ago, and neither has tomcat-users.xml
>
>
> server.xml (excerpts) :
> ...
> <!-- Editable user database that can also be used by
> UserDatabaseRealm to authenticate users -->
> <Resource name="UserDatabase" auth="Container"
> type="org.apache.catalina.UserDatabase"
> description="User database that can be updated and saved">
> </Resource>
> <ResourceParams name="UserDatabase">
> <parameter>
> <name>factory</name>
> <value>org.apache.catalina.users.MemoryUserDatabaseFactory</value>
> </parameter>
> <parameter>
> <name>pathname</name>
> <value>conf/tomcat-users.xml</value>
> </parameter>
> </ResourceParams>
> ...
> (further under <Engine> and <Host> :)
>
> <Realm className="org.apache.catalina.realm.UserDatabaseRealm"
> debug="0" resourceName="UserDatabase"/>
> ...
>
>
>
> catalina.out :
>
> 2008-12-28 13:21:58,543 [main] INFO
> org.apache.catalina.core.StandardService - Starting service Catalina
> 2008-12-28 13:21:58,545 [main] INFO
> org.apache.catalina.core.StandardEngine - Starting Servlet Engine:
> Apache Tomcat/5.0
> 2008-12-28 13:21:58,548 [main] WARN org.apache.naming.NamingContext -
> Unexpected exception resolving reference
> java.io.IOException: IOException writing to
> /srv/www/tomcat5/base/conf/tomcat-users.xml.new
> at
> org.apache.catalina.users.MemoryUserDatabase.save(MemoryUserDatabase.java:495)
>
> at
> org.apache.catalina.users.MemoryUserDatabaseFactory.getObjectInstance(MemoryUserDatabaseFactory.java:98)
>
> at
> org.apache.naming.factory.ResourceFactory.getObjectInstance(ResourceFactory.java:129)
>
> at
> javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:316)
> at org.apache.naming.NamingContext.lookup(NamingContext.java:791)
> at org.apache.naming.NamingContext.lookup(NamingContext.java:151)
> at
> org.apache.catalina.realm.UserDatabaseRealm.start(UserDatabaseRealm.java:252)
>
> at
> org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1075)
> at
> org.apache.catalina.core.StandardEngine.start(StandardEngine.java:478)
> at
> org.apache.catalina.core.StandardService.start(StandardService.java:480)
> at
> org.apache.catalina.core.StandardServer.start(StandardServer.java:2313)
> at org.apache.catalina.startup.Catalina.start(Catalina.java:556)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79)
>
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>
> at java.lang.reflect.Method.invoke(Method.java:618)
> at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:287)
> at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:425)
> javax.naming.NamingException: IOException writing to
> /srv/www/tomcat5/base/conf/tomcat-users.xml.new
> at org.apache.naming.NamingContext.lookup(NamingContext.java:803)
> at org.apache.naming.NamingContext.lookup(NamingContext.java:151)
> at
> org.apache.catalina.realm.UserDatabaseRealm.start(UserDatabaseRealm.java:252)
>
> at
> org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1075)
> at
> org.apache.catalina.core.StandardEngine.start(StandardEngine.java:478)
> at
> org.apache.catalina.core.StandardService.start(StandardService.java:480)
> at
> org.apache.catalina.core.StandardServer.start(StandardServer.java:2313)
> at org.apache.catalina.startup.Catalina.start(Catalina.java:556)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79)
>
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>
> at java.lang.reflect.Method.invoke(Method.java:618)
> at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:287)
> at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:425)
> 2008-12-28 13:21:58,549 [main] ERROR
> org.apache.catalina.startup.Catalina - Catalina.start:
> LifecycleException: No UserDatabase component found under key UserDatabase
> at
> org.apache.catalina.realm.UserDatabaseRealm.start(UserDatabaseRealm.java:259)
>
> at
> org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1075)
> at
> org.apache.catalina.core.StandardEngine.start(StandardEngine.java:478)
> at
> org.apache.catalina.core.StandardService.start(StandardService.java:480)
> at
> org.apache.catalina.core.StandardServer.start(StandardServer.java:2313)
> at org.apache.catalina.startup.Catalina.start(Catalina.java:556)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79)
>
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>
> at java.lang.reflect.Method.invoke(Method.java:618)
> at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:287)
> at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:425)
> 2008-12-28 13:21:58,550 [main] INFO org.apache.catalina.startup.Catalina
> - Server startup in 105 ms
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
>
>
> !DSPAM:49577b49258841336712104!
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Sudden and unexpected exception at Tomcat startup
Posted by Rainer Jung <ra...@kippdata.de>.
On 28.12.2008 14:01, André Warnier wrote:
> Hi.
>
> Does someone have an idea of what is going as per the logfile
> catalina.out below ?
> What is this IOException all about ?
>
> This is a Tomcat 5.0.x under Suse Enterprise Linux 10.1, which had been
> working fine until now and suddenly logs this at startup.
> This Tomcat runs under an IBM JVM 1.5.
>
> Tomcat is started, as per the listening ports and the "ps" display I can
> see, but apparently the access to Tomcat (through Apache and mod_jk)
> does not work anymore (tells me : The server is temporarily unable to
> service your request due to maintenance downtime or capacity problems.
> Please try again later. )
>
>
> Additional info :
> - the directory /srv/www/tomcat5/base/conf/ is writeable by the user
> "tomcat" under which Tomcat is started.
> - To my knowledge, the server.xml has not been changed since the
> previous succesful restart 2 days ago, and neither has tomcat-users.xml
>
>
> server.xml (excerpts) :
> ...
> <!-- Editable user database that can also be used by
> UserDatabaseRealm to authenticate users -->
> <Resource name="UserDatabase" auth="Container"
> type="org.apache.catalina.UserDatabase"
> description="User database that can be updated and saved">
> </Resource>
> <ResourceParams name="UserDatabase">
> <parameter>
> <name>factory</name>
> <value>org.apache.catalina.users.MemoryUserDatabaseFactory</value>
> </parameter>
> <parameter>
> <name>pathname</name>
> <value>conf/tomcat-users.xml</value>
> </parameter>
> </ResourceParams>
> ...
> (further under <Engine> and <Host> :)
>
> <Realm className="org.apache.catalina.realm.UserDatabaseRealm"
> debug="0" resourceName="UserDatabase"/>
> ...
>
>
>
> catalina.out :
>
> 2008-12-28 13:21:58,543 [main] INFO
> org.apache.catalina.core.StandardService - Starting service Catalina
> 2008-12-28 13:21:58,545 [main] INFO
> org.apache.catalina.core.StandardEngine - Starting Servlet Engine:
> Apache Tomcat/5.0
> 2008-12-28 13:21:58,548 [main] WARN org.apache.naming.NamingContext -
> Unexpected exception resolving reference
> java.io.IOException: IOException writing to
> /srv/www/tomcat5/base/conf/tomcat-users.xml.new
> at
> org.apache.catalina.users.MemoryUserDatabase.save(MemoryUserDatabase.java:495)
Starting with TC 5.5.12 you can add
<parameter>
<name>readonly</name>
<value>true</value>
</parameter>
to prevent this behaviour (e.g. during startup tomcat-users.xml gets
written out in a normalized way with an additional suffix ".new", and
then the new file gets renamed to the old one). The parameter is not
available for any 5.0 version.
Regards,
Rainer
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org