Re: [Resin-interest] CentOS 5 mod_caucho compile issue
Actually, I got it compile without errors by puttung the absolute path to apxs. Thanks The future is here. It's just not widely distributed yet. -William Gibson On Mon, Jan 12, 2009 at 2:17 AM, Vinny xaym...@gmail.com wrote: I think this may be my issue as well. How do I add those apr flags to my mod_caucho build? The future is here. It's just not widely distributed yet. -William Gibson On Wed, Apr 18, 2007 at 11:31 AM, Chris Jones cjo...@gdisoftware.comwrote: Ding Deng wrote: On 4/17/07, Chris Jones cjo...@gdisoftware.com wrote: Hey all, I have run into some issues compiling mod_caucho from resin 2.1.17 on CentOS 5. I have managed to get rid of an issue where the compiler was reporting missing apr header files. I modified the Makefile to include -I/usr/include/apr-1 to APACHE_INC=. This resolved the missing files issue but now running into other issues which I can't figure out. Here the output from make: (cd src/c/plugin; make) make[1]: Entering directory `/usr/src/resin-2.1.17/src/c/plugin' for dir in common apache2; do (cd $dir; make); done make[2]: Entering directory `/usr/src/resin-2.1.17/src/c/plugin/common' gcc -c -g -O2 stream.c gcc -c -g -O2 registry.c gcc -c -g -O2 config.c gcc -c -g -O2 memory.c /usr/bin/ld -r -o common.o stream.o registry.o config.o memory.o make[2]: Leaving directory `/usr/src/resin-2.1.17/src/c/plugin/common' make[2]: Entering directory `/usr/src/resin-2.1.17/src/c/plugin/apache2' gcc -c -I/usr/include/httpd -I/usr/include/apr-1 -DRESIN_HOME=\/usr/src/resin-2.1.17\ -I../common -g -O2 -fpic mod_caucho.c mv mod_caucho.o mod_caucho.lo In file included from /usr/include/apr-1/apr.h:7, from /usr/include/httpd/ap_config.h:25, from /usr/include/httpd/httpd.h:43, from mod_caucho.c:42: /usr/include/apr-1/apr-i386.h:270: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'apr_off_t' It's an APR issue: http://mail-archives.apache.org/mod_mbox/apr-dev/200410.mbox/%3c20041022090014.ga9...@redhat.com%3e HTH. Thanks, that worked. In file included from /usr/include/apr-1/apr_file_io.h:29, from /usr/include/apr-1/apr_network_io.h:26, from /usr/include/httpd/httpd.h:53, from mod_caucho.c:42: /usr/include/apr-1/apr_file_info.h:204: error: expected specifier-qualifier-list before 'apr_off_t' In file included from /usr/include/apr-1/apr_network_io.h:26, from /usr/include/httpd/httpd.h:53, from mod_caucho.c:42: /usr/include/apr-1/apr_file_io.h:548: error: expected declaration specifiers or '...' before 'apr_off_t' /usr/include/apr-1/apr_file_io.h:740: error: expected declaration specifiers or '...' before 'apr_off_t' In file included from /usr/include/httpd/httpd.h:53, from mod_caucho.c:42: /usr/include/apr-1/apr_network_io.h:545: error: expected declaration specifiers or '...' before 'apr_off_t' In file included from /usr/include/apr-1/apr_buckets.h:32, from /usr/include/httpd/httpd.h:54, from mod_caucho.c:42: /usr/include/apr-1/apr_mmap.h:134: error: expected declaration specifiers or '...' before 'apr_off_t' /usr/include/apr-1/apr_mmap.h:161: error: expected declaration specifiers or '...' before 'apr_off_t' In file included from /usr/include/httpd/httpd.h:54, from mod_caucho.c:42: /usr/include/apr-1/apr_buckets.h:242: error: expected specifier-qualifier-list before 'apr_off_t' /usr/include/apr-1/apr_buckets.h:706: error: expected declaration specifiers or '...' before 'apr_off_t' /usr/include/apr-1/apr_buckets.h:718: error: expected declaration specifiers or '...' before 'apr_off_t' /usr/include/apr-1/apr_buckets.h:754: error: expected declaration specifiers or '...' before 'apr_off_t' /usr/include/apr-1/apr_buckets.h:890: error: expected declaration specifiers or '...' before 'apr_off_t' /usr/include/apr-1/apr_buckets.h:891: error: expected declaration specifiers or '...' before 'apr_off_t' /usr/include/apr-1/apr_buckets.h:1168: error: expected declaration specifiers or '...' before 'apr_off_t' /usr/include/apr-1/apr_buckets.h:1367: error: expected declaration specifiers or '...' before 'apr_off_t' /usr/include/apr-1/apr_buckets.h:1381: error: expected declaration specifiers or '...' before 'apr_off_t' /usr/include/apr-1/apr_buckets.h:1431: error: expected declaration specifiers or '...' before 'apr_off_t' /usr/include/apr-1/apr_buckets.h:1447: error: expected declaration specifiers or '...' before 'apr_off_t' In file included from mod_caucho.c:42: /usr/include/httpd/httpd.h:826: error: expected specifier-qualifier-list before 'apr_off_t' In file included from /usr/include/httpd/http_core.h:32, from mod_caucho.c:44: /usr/include/httpd/util_filter.h:142:
[Resin-interest] a good ratio?
httpd-2.2.3-11.el5_2.centos.4 resin 3.1.8 What should be a good ratio between external apache connections and mod_caucho connections. Here is a sample are seeing this like this from netstat: [netstat -tan |grep \:80 | grep EST |wc -l ; netstat -tan |grep \:6802 | grep EST |wc -l (80:) 26 (6802:)110 5 32 7 48 10 34 Do the connection between apache httpd and resin count against apache 's MaxClients config ? or resin's maximums in the server.xml? The future is here. It's just not widely distributed yet. -William Gibson ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
[Resin-interest] Resin 4.0 clustering notes
I've added some notes about our clustering direction for Resin 4.0 at http://blog.caucho.com/?p=120 The main capabilities that we want for 4.0 clustering are: 1. dynamic servers (for load matching, and power savings) 2. simplify the administration model The main complexity of the current distributed session is that every server acts as a primary and a backup for some data. So it's difficult or impossible for an administrator to know exactly what happens when a server goes down due to maintenance or a crash. The new triad hub and spoke model simplifies that administration question. All replication occurs on the triad hub servers. So it's always safe to take down servers 4-64 at any time. The 3 hub servers (servers 1-3) are critical, but administrators can take more care with them because it's only 3 servers, and they're known as being more important. Those two requirements sound relatively simple, but imply a good deal of underlying infrastructure work. For example, distributed sessions since we no longer have the concept of an owning server, which means I need to add a temporary leasing concept that gives the same performance gains. For users, the changes should be mostly invisible. The first 3 servers in a cluster automatically form the triad, and all the replication and session caching happens under the covers using the current API. Single and dual servers work just like today. In other words, we're not adding a minimum requirement of 3 servers. -- Scott ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
[Resin-interest] Quercus w/ Virtual Hosts
Hi all, I'm trying to get Quercus working on Resin 3.2.1 (open source) under virtual hosts. I can create PHP pages under the default host as defined in resin.xml, and they're interpreted and run just fine. However, if I create a new host, e.g.: host id=example.company.com root-directory=/path/to/root/directory web-app id=/ document-directory=webapp/doc/directory/ /host PHP is not interpreted for that host. Instead, resin returns the php code as plain text. I'm at a bit of a loss as to why. I'm probably missing something absurdly simple, but it's just escaping me at the moment. Can anyone clue me in? Thanks, Tim ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
Re: [Resin-interest] Quercus w/ Virtual Hosts
On Jan 12, 2009, at 2:15 PM, Tim O'Donnell wrote: Hi all, I'm trying to get Quercus working on Resin 3.2.1 (open source) under virtual hosts. I can create PHP pages under the default host as defined in resin.xml, and they're interpreted and run just fine. However, if I create a new host, e.g.: host id=example.company.com root-directory=/path/to/root/directory web-app id=/ document-directory=webapp/doc/directory/ /host PHP is not interpreted for that host. Instead, resin returns the php code as plain text. I'm at a bit of a loss as to why. I'm probably missing something absurdly simple, but it's just escaping me at the moment. Can anyone clue me in? Have you deleted the resin:import for the app-default.xml? The app- default.xml contains the servlet definitions for Quercus. (Inside web-app-default blocks.) -- Scott Thanks, Tim ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
Re: [Resin-interest] a good ratio?
On Jan 12, 2009, at 10:49 AM, Vinny wrote: httpd-2.2.3-11.el5_2.centos.4 resin 3.1.8 What should be a good ratio between external apache connections and mod_caucho connections. Here is a sample are seeing this like this from netstat: [netstat -tan |grep \:80 | grep EST |wc -l ; netstat -tan |grep \: 6802 | grep EST |wc -l (80:) 26 (6802:)110 Do the connection between apache httpd and resin count against apache 's MaxClients config ? or resin's maximums in the server.xml? ratio isn't the right way of thinking about it. The detailed answer gets into how Apache spawns its processes and reuses them for following requests. Basically, as long as the 6802 count is reasonably low (100-200ish) or a bit more for a heavy site, then you're fine. The trouble starts when you have 1 TIME_WAIT connections or so. -- Scott The future is here. It's just not widely distributed yet. -William Gibson ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
Re: [Resin-interest] Quercus w/ Virtual Hosts
Okay, I'm an idiot. I was faked out by a second (pre-quercus) resin instance running on the server, with a nearly identical config as the new one I was setting up. I must've damaged some brain cells banging my head against this so as not to see the problem. Now let's all pretend this email exchange never happened. Thanks again, Scott. Tim On Mon, Jan 12, 2009 at 4:17 PM, Scott Ferguson f...@caucho.com wrote: On Jan 12, 2009, at 2:15 PM, Tim O'Donnell wrote: Hi all, I'm trying to get Quercus working on Resin 3.2.1 (open source) under virtual hosts. I can create PHP pages under the default host as defined in resin.xml, and they're interpreted and run just fine. However, if I create a new host, e.g.: host id=example.company.com root-directory=/path/to/root/directory web-app id=/ document-directory=webapp/doc/directory/ /host PHP is not interpreted for that host. Instead, resin returns the php code as plain text. I'm at a bit of a loss as to why. I'm probably missing something absurdly simple, but it's just escaping me at the moment. Can anyone clue me in? Have you deleted the resin:import for the app-default.xml? The app-default.xml contains the servlet definitions for Quercus. (Inside web-app-default blocks.) -- Scott Thanks, Tim ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
[Resin-interest] debugging mod_caucho
I enabled debugging on mod_caucho and I am seeing line like : config.c:1286:cse_update_host(): foo.com:80(0x918ad50) old:0 now:1231827067() config.c:1164:cse_update_host_from_resin(): can't open any connections config.c:1291:cse_update_host(): complete foo.com:80(0x918ad50) old:0 now:1231827067() config.c:1286:cse_update_host(): :0(0x9189c70) old:0 now:1231827067() config.c:1164:cse_update_host_from_resin(): can't open any connections config.c:1291:cse_update_host(): complete :0(0x9189c70) old:0 now:1231827067() mod_caucho.c:922:caucho_request(): session index: -1 mod_caucho.c:934:caucho_request(): no connection: cluster(0x9189cb0) in my resin.conf I have : !-- define the servers in the cluster -- server id= address=127.0.0.1 port=6802/ and netstat shows : # netstat -atnp |grep 68 tcp0 0 127.0.0.1:6802 0.0.0.0:* LISTEN 32667/java the httpd.conf has : LoadModule caucho_module /usr/lib/httpd/modules/mod_caucho.so ResinConfigServer 127.0.0.1 6800 CauchoHost 127.0.0.1 6800 AddHandler caucho-request .jsp Location /caucho-status SetHandler caucho-status /Location resin 3.1.8 /apache 2.2.3 centos Any ideas? The future is here. It's just not widely distributed yet. -William Gibson ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
