We have a new installation of RedHat Apache httpd-2.0.52 and Resin 3.1.3 and
since production, we randomly receive 404 errors (Using mod_cacho). This can
only be reproduced by continuously refreshing the browser but requires numerous
attempts to produce the 404.
There are a few posts from mid
Resin 3.1.3 with Apache 2.0.52
While troubleshooting a site failing to respond, I've found many
connections remain in CLOSE_WAIT indefinitely, even after leaving
Resin shut down for hours. Connections are between Resin and
Apache/mod_caucho on the server in question, or another load balanced
I've also been looking into versions installed with mod_caucho after
3.1.6 and get not communication between mod_caucho and Resin.
http://bugs.caucho.com/view.php?id=3013 indicates build scripts are
fixed in 4.0.0. Does this mean there is a fix I can apply in a later
stable, or will I have to
We recently had problems building resin-pro-3.1.8 for Apache and
applied the solution in 0003698 of removing line CFLAGS=$CFLAGS from
the configure file. That change allowed a successful build in a test
environment.
Using this same method on our new production server results in
Service
I have test against another 32 bit server running
2.6.18-92.1.22.el5.centos.plusPAE with same installed packages as the
older 32 bit server running 2.6.18-92.1.22.el5.centos.plus also fails.
Another test on a new 64 bit CentOS release 5.2 (Final) build running
2.6.18-92.el5 yields same results.
On Wed, Feb 25, 2009 at 5:37 PM, Scott Ferguson f...@caucho.com wrote:
Good. In that case, you're not hitting the alignment bug, because
that bug wouldn't try to connect to Resin.
What does the /caucho-status show?
Status : Caucho Servlet Engine
Start Time Wed Feb 25 16:01:29 2009
Now
I have a server with apache+resin-3.1.6 installed.
Are you running caucho_module?
Have you used netstat command during troubleshooting? We had our
thread-max fairly high and I was seeing mass quantities of connections
to the srun port. Shutting down the JVM would clear the connections,
but it
Is there a way to limit access to site/caucho-status URL either per
IP or per user/password?
Have you checked out Location directive?
This works nicely.
Location /caucho-status
SetHandler default-handler
Order Deny,Allow
Deny from all
Allow from 192.168.
/Location
David
In our case, we still use Apache, due to other things we need, but we
have always used mod_proxy to communicate with the backoffice Resin
instances, instead of mod_caucho.
This is a smashing idea, and I feel like an idiot for not seeing it.
Unfortunately, ProxyPassMatch is broken in the RPM
The resin docs on the caucho site are badly in need of revision,
reorganization, and some TLC.
I'd love to see Caucho make their course material available. I don't
anticipate a training budget that includes travel, so am dependent on
resin-interest and the documentation that is online.
I've started researching rewrite-dispatch and ip-constraint in an
effort to move more configuration from Apache to Resin. I've found
quite a few threads on these that discuss settings in both
WEB-INF/resin-web.xml and ${resin.home}/conf/resin.conf, but not much
about why one is used over the
Until recently we have removed the work directory when making code and
content changes. We now have the flexibility to modify, add, and
remove content related JSPs individually. While adding and modifying
work as expected, removing a JSP does not result in an eventual
removal of the associated
OK, there is a solution. It was not APR which was high on our suspect
list. Mea culpa. The test servers built to evaluate upgrading from
3.1.3 to 3.1.8 were built on CentOS 5 with SELinux enabled. There,
I've said it. Self inflicted. We don't use SELinux, not sure how it
was missed on the
On Fri, Mar 13, 2009 at 1:43 PM, Aaron Freeman wrote:
I used to be a big Apache fan about 5 years ago, but since I have decoupled
Apache from Resin and went exclusively with Resin I have had no regrets.
Good to know. I've done the majority of site management via Apache,
so transitioning
14 matches
Mail list logo
