Resin is inappropriately requiring write access to the jsp files it handles.

This was previously submitted as bug, but because it couldn't be 
reproduced, it was closed.

After I recently upgraded to sun-jdk-,  resin 3.1.2 and 
apache 2.2.6, I retested and it's still present. I wonder whether the 
right environment had been tested (64-bit Linux), so I've resubmitted 

If anyone else has run into this situation, please let me know.

>In our previous setup, I worked around this apparent requirement
>simply by running resin under the username that owns the jsp files.
>But in our new server, I wanted to keep resin running as resin. All
>the files in the ROOT directory are set as
>-rwxr-xr-x  somejspfile.jsp
>and resin will often, but not always claim that it can't find a
>particular jsp file. When I added the resin user to the group that
>owns the file and changed the permissions to
>-rwxrwxr-x  somejspfile.jsp
>then resin runs fine finding and executing every jsp file. But do I
>really have to do that? Why does resin to need write access to the
>jsp files?
>I'm using resin 3.1.1, sun-jdk-, and apache 2.2.4.


Maurice Volaski, [EMAIL PROTECTED]
Computing Support, Rose F. Kennedy Center
Albert Einstein College of Medicine of Yeshiva University

resin-interest mailing list

Reply via email to