Hi there,
I've googled for this, and can't seem to find anyone who wants to do the
same thing, so I figured you guys would be the best source of information.
We run a very large website, which is generated dynamically from resin, and
we are looking at technical failover solutions.
We believe
Hi Michael,
Instead of mapping a servlet url to static content (I'm assuming that that is
what you are trying to do) you can also
get the client to request the url for what the static pages would be and map
the servlet that generates the
static content to the 404 error handler.
In this
I thought that resin could do it for you ??
Normally, if I wanted to do that, I'd modify the cache parameters :
resin:if test=${isResinProfessional}
cache path=cache memory-size=80M/
/resin:if
and
cache-mapping url-pattern=*.html expires=60h/
Did you try this ?
Andre,
That sounds almost perfect, except that we don't want for the system to
behave that way except in very unusual circumstances.
So we need to be able to switch into using this mode only when either we
have a catastrophic database failure, or when we are suffering unusually
high load (such
Michael,
If you experience a catastrofic database failure, you probably don't have the
data to generate the pages, so redirecting to
some kind of out-of-order informartion would seem appropriate as it will be too
late to start building your static pages.
You could keep the setup I described
Andre,
The plan is that there will be a seperate application, run at regular
intervals that will poll the database, look for data that has been modified
recently, and it would press the pages. This would provide us with
potentially out of date, but valid pages for all of our core content,
On Oct 16, 2007, at 8:00 AM, Michael Brunton-Spall wrote:
Andre,
The plan is that there will be a seperate application, run at
regular intervals that will poll the database, look for data that
has been modified recently, and it would press the pages. This
would provide us with
can anyone guide me on how to setup a custom errorpage for error 500 with my
java webapp running on resin 3.0.x ?
I have tried setting it up in web.xml, but all I get is:
*java.lang.IllegalStateException: forward() not allowed after buffer has ***
*committed.
lhrotnes
*
Greetings,
I've been a Resin advocate for several years now. When I first did a
performance comparison between Resin 2 and Tomcat, Resin's performance
simply blew me away. Like many other people on this list, I imagine I
switched entirely to recommending resin as the application server for
Considering that Resin now has a watchdog process that monitors the
servers, is it possible to simply have the watchdog monitor and start
multiple resin servers?
Here's what I'm thinking why this is good.
1) One startup script to startup resin. No need to create multiple
startup scripts
On Oct 16, 2007, at 5:30 PM, Chris Chen wrote:
Considering that Resin now has a watchdog process that monitors the
servers, is it possible to simply have the watchdog monitor and start
multiple resin servers?
Yep. It does that now.
When you start a second Resin, the resin.jar process
Hello.
I try to use new Resin 3.1.3 with linux.
I found little problem with {resin.home}/bin/httpd.sh.
--
exec $java -jar ${RESIN_HOME}/resin.jar $*
--
correct is
exec $java -jar ${RESIN_HOME}/lib/resin.jar $*
12 matches
Mail list logo
