www-apache-bugdb mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From samuel.ea...@acterna.com
Subject Re: general/7783: critical File Not Found error as apachectl start runs
Date Thu, 07 Jun 2001 15:35:19 GMT


I have found that this problem is on Solaris 2.8 and not on NT.  A work-around
that has been effective is to wait until Tomcat creates mod_jk.conf-auto before
kicking off Apache.  Apparently, the file locking semantics to support Java file
access do not work on Solaris 2.8 like one would expect.  In particular, when
one calls file.close() (e.g. after updating the Tomcat file), any subsequent
call that one makes (e.g. to kick off Apache) assumes that the file exists, is
not locked, and is available for use.  This does not seem to be the case.





submit@bugz.apache.org on 05/29/2001 02:50:03 PM

Please respond to submit@bugz.apache.org; Please respond to
      apache-bugdb@apache.org

To:   Samuel Eaves/SAR/Global@Global
cc:

Subject:  Re: general/7783: critical File Not Found error as apachectl start
      runs



Thank you very much for your problem report.
It has the internal identification `general/7783'.
The individual assigned to look at your
report is: apache.

>Category:       general
>Responsible:    apache
>Synopsis:       critical File Not Found error as apachectl start runs
>Arrival-Date:   Tue May 29 11:50:02 PDT 2001







Mime
View raw message