Thanks,
Where should I write the readonly parameter?
here:
<!-- Resource name="UserDatabase" auth="Container"
type="org.apache.catalina.UserDatabase" readonly="true">
or maybe here:
<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>
<parameter>
<name>readonly</name>
<value>true</value>
</parameter>
</ResourceParams>
Sagi
-----Original Message-----
From: Markus Schönhaber [mailto:[EMAIL PROTECTED]
Sent: Wednesday, December 28, 2005 12:11
To: Tomcat Users List
Subject: Re: tomcat-users.xml file corruption
Nachum, Sagi wrote:
> After inquiring a little I discovered that the tomcat-users.xml file
> located at conf directory is empty.
> After I replaced this file with a valid one, the problem was solved. I
> saw some more messages in this and other forums that regard this
> problem.
> And here's my question:
>
> I don't want to need to replace this file every time the computer
> crashes unexpectedly, how can I prevent this file from being corrupted?
You can prevent a recent Tomcat 5.5 from writing tomcat-users.xml by setting
readonly="true"
on the Resource element in server.xml where the UserDatabase is defined.
But if you can't prevent your machine from unexpectedly shutting down, wether
or not tomcat-users.xml get destroyed might be your smallest problem.
Regards
mks
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
__________________________________________________________________________________________
This electronic message contains information from Verint Systems, which may be
privileged and confidential.
The information is intended to be for the use of the individual(s)or entity
named above.
If you are not the intended recipient, be aware that any disclosure, copying,
distribution or use of the contents of this information is prohibited.
If you have received this electronic message in error, please notify us by
replying to this email (1).
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
