Re: [Resin-interest] Problem with CauchoConfigFile and Resin 3.1.1 +Unix + Apache2

2007-06-04 Thread andy.duplain 
I use something like this with Apache 2.2.3:
 
LoadModule caucho_module /usr/lib/apache2/modules/mod_caucho.so

ResinConfigServer localhost 6800
CauchoStatus yes
 
Location /caucho-status
Order deny,allow
Deny from all
Allow from 127.0.0.1 192.168.0.0/16 my-domain.net
/Location

 
Cheers,
Andy
 





From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Ben Strum
Sent: Monday, June 04, 2007 1:57 AM
To: resin-interest@caucho.com
Subject: [Resin-interest] Problem with CauchoConfigFile and
Resin 3.1.1 +Unix + Apache2


I am trying to upgrade servers we have to the latest Resin
version with Apache 2.  Prior to this, we were running older versions of
both Resin and Apache.
 
We are seeing the following error message upong running httpd:
Invalid command 'CauchoConfigFile', perhaps misspelled or
defined by a module not included in the server configuration
 
Our httpd.conf file looks like this:
 
LoadModule caucho_module
/home/blink/blinkproweb/modules/mod_caucho.so
#AddModule mod_caucho.c
IfModule mod_caucho.c
CauchoConfigFile resin.conf
/IfModule
 
I have seen posts that you must call AddModule before you can
call CauchoConfigFile but AddModule does not seem to be supported under
Apache 2 anymore.  
 
Am I missing something when building either Apache or Resin?
Can someone tell me the correct method for specifying resin.conf in this
environment?
 
Thank you,
 
Benjamin Strum
ThinkTron Corporation

___
resin-interest mailing list
resin-interest@caucho.com
http://maillist.caucho.com/mailman/listinfo/resin-interest

[Resin-interest] Watchdog using 127Mb - ouch!

2007-06-04 Thread Rick Ross 
We have recently moved from resin-3.0.x to resin-3.1.x, and we are  
trying to get a measure of control over the new Java-based watchdog  
process. When it was a perl script, it consumed about 3.5-4Mb of  
resident ram, but the Java one (even after giving it fairly  
aggressive jvm arguments via watchdog-args) is consuming 127Mb of  
resident ram on the same server.


Maybe we haven't been aggressive enough in trying to reduce the  
watchdog's footprint. Here are the watchdog-arg values we're using.  
Can we trim this back even further?


watchdog-arg-Dcom.sun.management.jmxremote.port=9003/watchdog-arg
watchdog-arg-Dcom.sun.management.jmxremote/watchdog-arg
watchdog-arg-Xmx64m/watchdog-arg
watchdog-arg-Xss256k/watchdog-arg
watchdog-arg-XX:MaxPermSize=25m/watchdog-arg


Thanks,
Rick

PS - We have affectionately name the new one WatchPig in honor of  
being 30 times larger than the perl watchdog. As a longtime Java  
advocate this one is a little bit embarrassing to me. I don't see why  
the Java proc can't be a LOT more svelte. It does seem to be keeping  
a lot of threads alive (possibly in order to support the JMX remote



---
Rick Ross
www.dzone.com
Phone: +1.919.678.0300
Email: [EMAIL PROTECTED]



___
resin-interest mailing list
resin-interest@caucho.com
http://maillist.caucho.com/mailman/listinfo/resin-interest