Hi Scott,
You might double check the timeouts and netstat between Resin and
Apache. It sounds like something is timing out incorrectly.
Are the timeouts specified in Resin or Apache or are they native to
Linux? I know netstat is a Linux command.
I have narrowed the problem down to
Darn - I should really explore all possibilities before posting. I
downloaded the source in the end and found out what was creating these
logs - the solution is to use the (undocumented?) command line argument
-log-directory when starting resin, and making the logfile name relative
(i.e.
Andy,
I'm not sure if this still applies in 3.1.x, but in prior versions there
was a downside to co-opting that core JVM log. If you force that into
your main console (stderr/out) log, Resin may not be able to roll it any
more. You can use that arg to put the core jvm log where you want it,
Before you start doing it the hard way:
Double check your apache.conf and resin.conf to make sure keepalive are both
off.
If you want to have keepalive on, set the timeout to be the same. Mismatching
of keepalive settings (on all the servers for your web site, including proxy)
might cause
In 3.0.x, the server mbean has a clearCache() and a clearCacheByPattern(host,
url) method in com.caucho.server.resin.mbean.ServletServerMBean. The name
of the mbean should be resin:type=Server,name=default
Bill
On 5/31/07, Bernard Bernstein [EMAIL PROTECTED] wrote:
We are using the Resin
First of all, Expire header and If-Modified-Since header are there to serve 2
different purposes
There was an email in this forum that I think should address your concern, IF
you actually follow the link and read the articles.
I dug this email up from my deleted section, and attached it
