This issue seems to creep up from time to time and I just filed
another bug with it, http://bugs.caucho.com/view.php?id=2635, but now
I figured it out:
Resin does indeed require write access to the work directory (i.e.,
/ROOT/WEB-INF/work/) and everything under it; otherwise, it will
complain with bogus 404, not found errors.
>Resin is inappropriately requiring write access to the jsp files it handles.
>This was previously submitted as bug
>http://bugs.caucho.com/view.php?id=1818, but because it couldn't be
>reproduced, it was closed.
>After I recently upgraded to sun-jdk-1.6.0.03, 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
>>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
>>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?
Maurice Volaski, [EMAIL PROTECTED]
Computing Support, Rose F. Kennedy Center
Albert Einstein College of Medicine of Yeshiva University
resin-interest mailing list