I believe that I have not seen a filesystem permissions problem reported this way, but the traceback suggests that Tomcat was reading DSpace's WEB-INF/web.xml at the time, so it might be well to check the ownership and permissions of the webapp.'s files. If it's not that then I fear that this problem is beyond my current understanding of the java.security package, but others may be able to help.
Tomcat needs read access to the webapp files, naturally. It appears that there are some places in Tomcat where the programmer was careless and requested write access even when writing makes no sense, so "rw" access may be required. Unless you have unusual needs, the files are most simply set to be owned by the same account used to run Tomcat. I looked at one of my own DSpace installations and found: -rw-r--r-- 1 tomcat tomcat 20122 2008-01-22 10:02 web.xml where "tomcat" is the account used to run Tomcat, set up by the distribution's package manager. The DSpace documentation may require some interpretation here, since it assumes that Tomcat is installed manually and run from an account named 'dspace', but if you use your distribution's Tomcat package then the account is almost certainly not named 'dspace'. -- Mark H. Wood, Lead System Programmer mw...@iupui.edu Friends don't let friends publish revisable-form documents.
pgp3ypwq9SZN2.pgp
Description: PGP signature
------------------------------------------------------------------------------ Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are powering Web 2.0 with engaging, cross-platform capabilities. Quickly and easily build your RIAs with Flex Builder, the Eclipse(TM)based development software that enables intelligent coding and step-through debugging. Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com
_______________________________________________ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
