[users@httpd] Why so much difference in memory used per process in apache2 between two different systems

[Marc Serra]

Hi to all,

I already posted this question to stackoverflow.com but no answer after 9
days:
https://stackoverflow.com/questions/67439771/why-so-much-difference-in-memory-used-per-process-in-apache2-between-two-differe

I hope the apache gurus in this list can help me :)

I have a pair of Ubuntu dedicated servers...

Server1:
Ubuntu 16.04.7 (64 bits)
16GB RAM
8 Xeon CPU
Apache 2.4.18
MPM mode: prefork

Server2:
Ubuntu server 20.04.2 (64 bits)
32GB RAM
8 Xeon CPU
2.4.41
MPM mode: event

On Server1, each apache2 process uses between 7MB and 18MB of RAM ...
# ps axo 'user rss cmd' | grep apache | grep -v "\(root\|grep\|tomcat\)"
www-data 18232 /usr/sbin/apache2 -k start
www-data 11700 /usr/sbin/apache2 -k start
www-data 11276 /usr/sbin/apache2 -k start
www-data 10792 /usr/sbin/apache2 -k start
www-data 11216 /usr/sbin/apache2 -k start
www-data 11600 /usr/sbin/apache2 -k start
www-data 10336 /usr/sbin/apache2 -k start
www-data 11356 /usr/sbin/apache2 -k start
www-data 11348 /usr/sbin/apache2 -k start
www-data 10980 /usr/sbin/apache2 -k start
www-data 11316 /usr/sbin/apache2 -k start
www-data  6808 /usr/sbin/apache2 -k start


On Server2, each apache2 process uses between 120MB and 130MB of RAM ...
# ps axo 'user rss cmd' | grep apache | grep -v "\(root\|grep\|tomcat\)"
www-data 120436 /usr/sbin/apache2 -k start
www-data 119784 /usr/sbin/apache2 -k start
www-data 128720 /usr/sbin/apache2 -k start
www-data 130208 /usr/sbin/apache2 -k start


Why so much difference in memory used?

After read a few documentation and googleing, I thought about loaded
modules, but there are not a lot of difference between each server...

Server1
# apache2 -M
Loaded Modules:
 core_module (static)
 so_module (static)
 watchdog_module (static)
 http_module (static)
 log_config_module (static)
 logio_module (static)
 version_module (static)
 unixd_module (static)
 access_compat_module (shared)
 actions_module (shared)
 alias_module (shared)
 auth_basic_module (shared)
 auth_digest_module (shared)
 auth_openidc_module (shared)
 authn_core_module (shared)
 authn_file_module (shared)
 authz_core_module (shared)
 authz_host_module (shared)
 authz_user_module (shared)
 autoindex_module (shared)
 bw_module (shared)
 cgi_module (shared)
 dav_module (shared)
 dav_fs_module (shared)
 dav_lock_module (shared)
 deflate_module (shared)
 dir_module (shared)
 env_module (shared)
 expires_module (shared)
 fcgid_module (shared)
 filter_module (shared)
 headers_module (shared)
 include_module (shared)
 mime_module (shared)
 mpm_prefork_module (shared)
 negotiation_module (shared)
 proxy_module (shared)
 proxy_balancer_module (shared)
 proxy_fcgi_module (shared)
 proxy_http_module (shared)
 rewrite_module (shared)
 setenvif_module (shared)
 slotmem_shm_module (shared)
 socache_shmcb_module (shared)
 ssl_module (shared)
 status_module (shared)
 suexec_module (shared)
 userdir_module (shared)

Server2
# apache2 -M
Loaded Modules:
 core_module (static)
 so_module (static)
 watchdog_module (static)
 http_module (static)
 log_config_module (static)
 logio_module (static)
 version_module (static)
 unixd_module (static)
 access_compat_module (shared)
 aclr_module (shared)
 actions_module (shared)
 alias_module (shared)
 auth_basic_module (shared)
 auth_digest_module (shared)
 auth_openidc_module (shared)
 authn_core_module (shared)
 authn_file_module (shared)
 authz_core_module (shared)
 authz_host_module (shared)
 authz_user_module (shared)
 autoindex_module (shared)
 cgid_module (shared)
 dav_module (shared)
 dav_fs_module (shared)
 dav_lock_module (shared)
 deflate_module (shared)
 dir_module (shared)
 env_module (shared)
 fcgid_module (shared)
 filter_module (shared)
 headers_module (shared)
 include_module (shared)
 mime_module (shared)
 mpm_event_module (shared)
 negotiation_module (shared)
 proxy_module (shared)
 proxy_balancer_module (shared)
 proxy_fcgi_module (shared)
 proxy_http_module (shared)
 remoteip_module (shared)
 reqtimeout_module (shared)
 rewrite_module (shared)
 security2_module (shared)
 setenvif_module (shared)
 slotmem_shm_module (shared)
 socache_shmcb_module (shared)
 ssl_module (shared)
 status_module (shared)
 suexec_module (shared)
 unique_id_module (shared)
 userdir_module (shared)


I already changed MPM mode from Event to Prefork on Server2, with the same
results.

What else can I check to understand this difference?

Thank's!

-- 

Manxa 
1876, S.L. *
Ctra. 
Les Tries, 85. 17800 Olot (Girona)**Tel. 972 27 
45 30 Fax 972 27 45 32*


* Manxa Industrial | *Coneix
més aquí 




* Manxa Ferros | *Coneix
més aquí 




* Manxa Ferreteria i Parament de la Llar | 
*Coneix
més aquí 


**

-- 


El contingut d’aquest correu electrònic i els seus annexos és 
estrictament confidencial. En el cas que no siguis el destinatari i hagis 
rebut aquest missatge per error, preguem que ho comuniquis al remitent i 
procedeixis a la seva eliminació, sense dif

Re: [users@httpd] Why so much difference in memory used per process in apache2 between two different systems

[Dino Ciuffetti]

Try to comment out mod_security, it's a module that use enough memory.
Also on server2 there are modules not loaded on server1. BTW what's your 
problem? Your server is plenty of ram and RSS memory is not creating any 
problem. Right?
17 maggio 2021 13:34, "Marc Serra" mailto:mse...@manxa.com?to=%22Marc%20Serra%22%20)> wrote:
Hi to all,

I already posted this question to stackoverflow.com (http://stackoverflow.com) 
but no answer after 9 days: 
https://stackoverflow.com/questions/67439771/why-so-much-difference-in-memory-used-per-process-in-apache2-between-two-differe
 
(https://stackoverflow.com/questions/67439771/why-so-much-difference-in-memory-used-per-process-in-apache2-between-two-differe)

I hope the apache gurus in this list can help me :)

I have a pair of Ubuntu dedicated servers...

Server1:
Ubuntu 16.04.7 (64 bits)
16GB RAM
8 Xeon CPU
Apache 2.4.18
MPM mode: prefork

Server2:
Ubuntu server 20.04.2 (64 bits)
32GB RAM
8 Xeon CPU
2.4.41
MPM mode: event

On Server1, each apache2 process uses between 7MB and 18MB of RAM ...
# ps axo 'user rss cmd' | grep apache | grep -v "(root|grep|tomcat)"
www-data 18232 /usr/sbin/apache2 -k start
www-data 11700 /usr/sbin/apache2 -k start
www-data 11276 /usr/sbin/apache2 -k start
www-data 10792 /usr/sbin/apache2 -k start
www-data 11216 /usr/sbin/apache2 -k start
www-data 11600 /usr/sbin/apache2 -k start
www-data 10336 /usr/sbin/apache2 -k start
www-data 11356 /usr/sbin/apache2 -k start
www-data 11348 /usr/sbin/apache2 -k start
www-data 10980 /usr/sbin/apache2 -k start
www-data 11316 /usr/sbin/apache2 -k start
www-data 6808 /usr/sbin/apache2 -k start
On Server2, each apache2 process uses between 120MB and 130MB of RAM ...
# ps axo 'user rss cmd' | grep apache | grep -v "(root|grep|tomcat)"
www-data 120436 /usr/sbin/apache2 -k start
www-data 119784 /usr/sbin/apache2 -k start
www-data 128720 /usr/sbin/apache2 -k start
www-data 130208 /usr/sbin/apache2 -k start
Why so much difference in memory used?

After read a few documentation and googleing, I thought about loaded modules, 
but there are not a lot of difference between each server...

Server1
# apache2 -M
Loaded Modules:
core_module (static)
so_module (static)
watchdog_module (static)
http_module (static)
log_config_module (static)
logio_module (static)
version_module (static)
unixd_module (static)
access_compat_module (shared)
actions_module (shared)
alias_module (shared)
auth_basic_module (shared)
auth_digest_module (shared)
auth_openidc_module (shared)
authn_core_module (shared)
authn_file_module (shared)
authz_core_module (shared)
authz_host_module (shared)
authz_user_module (shared)
autoindex_module (shared)
bw_module (shared)
cgi_module (shared)
dav_module (shared)
dav_fs_module (shared)
dav_lock_module (shared)
deflate_module (shared)
dir_module (shared)
env_module (shared)
expires_module (shared)
fcgid_module (shared)
filter_module (shared)
headers_module (shared)
include_module (shared)
mime_module (shared)
mpm_prefork_module (shared)
negotiation_module (shared)
proxy_module (shared)
proxy_balancer_module (shared)
proxy_fcgi_module (shared)
proxy_http_module (shared)
rewrite_module (shared)
setenvif_module (shared)
slotmem_shm_module (shared)
socache_shmcb_module (shared)
ssl_module (shared)
status_module (shared)
suexec_module (shared)
userdir_module (shared)
Server2
# apache2 -M
Loaded Modules:
core_module (static)
so_module (static)
watchdog_module (static)
http_module (static)
log_config_module (static)
logio_module (static)
version_module (static)
unixd_module (static)
access_compat_module (shared)
aclr_module (shared)
actions_module (shared)
alias_module (shared)
auth_basic_module (shared)
auth_digest_module (shared)
auth_openidc_module (shared)
authn_core_module (shared)
authn_file_module (shared)
authz_core_module (shared)
authz_host_module (shared)
authz_user_module (shared)
autoindex_module (shared)
cgid_module (shared)
dav_module (shared)
dav_fs_module (shared)
dav_lock_module (shared)
deflate_module (shared)
dir_module (shared)
env_module (shared)
fcgid_module (shared)
filter_module (shared)
headers_module (shared)
include_module (shared)
mime_module (shared)
mpm_event_module (shared)
negotiation_module (shared)
proxy_module (shared)
proxy_balancer_module (shared)
proxy_fcgi_module (shared)
proxy_http_module (shared)
remoteip_module (shared)
reqtimeout_module (shared)
rewrite_module (shared)
security2_module (shared)
setenvif_module (shared)
slotmem_shm_module (shared)
socache_shmcb_module (shared)
ssl_module (shared)
status_module (shared)
suexec_module (shared)
unique_id_module (shared)
userdir_module (shared)
I already changed MPM mode from Event to Prefork on Server2, with the same 
results.

What else can I check to understand this difference?

Thank's!

Manxa 1876, S.L. 
Ctra. Les Tries, 85. 17800 Olot (Girona)
Tel. 972 27 45 30 Fax 972 27 45 32
 Manxa Industrial | Coneix més aquí (http://www.manxaindustrial.com)

 Manxa Ferros | Coneix més aquí (http://www.manxaferros.co

Re: [users@httpd] Why so much difference in memory used per process in apache2 between two different systems

[Yann Ylavic]

Hi,

On Mon, May 17, 2021 at 1:34 PM Marc Serra  wrote:
>
> I have a pair of Ubuntu dedicated servers...
>
> Server1:
> Ubuntu 16.04.7 (64 bits)
> 16GB RAM
> 8 Xeon CPU
> Apache 2.4.18
> MPM mode: prefork
>
> Server2:
> Ubuntu server 20.04.2 (64 bits)
> 32GB RAM
> 8 Xeon CPU
> 2.4.41
> MPM mode: event

MPM prefork is single threaded, while MPM event uses multiple threads,
and each thread "consumes" 8MB of rss (for its stack) on a typical
linux system.
The default thread stack size can be changed with "ulimit -s" (or
LimitSTACK= on systemd), depending on the loaded modules and their
stack "consumption".
I usually run httpd with "ulimit -s 512" (KB) without issues, but this
needs testing in your environment (i.e. no crash)..

Regards;
Yann.

-
To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org
For additional commands, e-mail: users-h...@httpd.apache.org

Re: [users@httpd] Why so much difference in memory used per process in apache2 between two different systems

[Daniel Ferradal]

The list of modules is different. I don't think you can compare event and
prefork servers as if they should behave the same, even more if you have a
different list of modules. Consider in prefork each process is a worker,
while on event processes are not workers, but threads of each process.

In order to compare fairly you have to use the same modules, same load,
similar resulting mpm settings and compare the total usage, still your
biggest concern unless you have a faulty module mostly will be CPU.

Also consider there are some different modules in each case too, some are
third party modules.




El lun, 17 may 2021 a las 13:34, Marc Serra () escribió:

> Hi to all,
>
> I already posted this question to stackoverflow.com but no answer after 9
> days:
> https://stackoverflow.com/questions/67439771/why-so-much-difference-in-memory-used-per-process-in-apache2-between-two-differe
>
> I hope the apache gurus in this list can help me :)
>
> I have a pair of Ubuntu dedicated servers...
>
> Server1:
> Ubuntu 16.04.7 (64 bits)
> 16GB RAM
> 8 Xeon CPU
> Apache 2.4.18
> MPM mode: prefork
>
> Server2:
> Ubuntu server 20.04.2 (64 bits)
> 32GB RAM
> 8 Xeon CPU
> 2.4.41
> MPM mode: event
>
> On Server1, each apache2 process uses between 7MB and 18MB of RAM ...
> # ps axo 'user rss cmd' | grep apache | grep -v "\(root\|grep\|tomcat\)"
> www-data 18232 /usr/sbin/apache2 -k start
> www-data 11700 /usr/sbin/apache2 -k start
> www-data 11276 /usr/sbin/apache2 -k start
> www-data 10792 /usr/sbin/apache2 -k start
> www-data 11216 /usr/sbin/apache2 -k start
> www-data 11600 /usr/sbin/apache2 -k start
> www-data 10336 /usr/sbin/apache2 -k start
> www-data 11356 /usr/sbin/apache2 -k start
> www-data 11348 /usr/sbin/apache2 -k start
> www-data 10980 /usr/sbin/apache2 -k start
> www-data 11316 /usr/sbin/apache2 -k start
> www-data  6808 /usr/sbin/apache2 -k start
>
>
> On Server2, each apache2 process uses between 120MB and 130MB of RAM ...
> # ps axo 'user rss cmd' | grep apache | grep -v "\(root\|grep\|tomcat\)"
> www-data 120436 /usr/sbin/apache2 -k start
> www-data 119784 /usr/sbin/apache2 -k start
> www-data 128720 /usr/sbin/apache2 -k start
> www-data 130208 /usr/sbin/apache2 -k start
>
>
> Why so much difference in memory used?
>
> After read a few documentation and googleing, I thought about loaded
> modules, but there are not a lot of difference between each server...
>
> Server1
> # apache2 -M
> Loaded Modules:
>  core_module (static)
>  so_module (static)
>  watchdog_module (static)
>  http_module (static)
>  log_config_module (static)
>  logio_module (static)
>  version_module (static)
>  unixd_module (static)
>  access_compat_module (shared)
>  actions_module (shared)
>  alias_module (shared)
>  auth_basic_module (shared)
>  auth_digest_module (shared)
>  auth_openidc_module (shared)
>  authn_core_module (shared)
>  authn_file_module (shared)
>  authz_core_module (shared)
>  authz_host_module (shared)
>  authz_user_module (shared)
>  autoindex_module (shared)
>  bw_module (shared)
>  cgi_module (shared)
>  dav_module (shared)
>  dav_fs_module (shared)
>  dav_lock_module (shared)
>  deflate_module (shared)
>  dir_module (shared)
>  env_module (shared)
>  expires_module (shared)
>  fcgid_module (shared)
>  filter_module (shared)
>  headers_module (shared)
>  include_module (shared)
>  mime_module (shared)
>  mpm_prefork_module (shared)
>  negotiation_module (shared)
>  proxy_module (shared)
>  proxy_balancer_module (shared)
>  proxy_fcgi_module (shared)
>  proxy_http_module (shared)
>  rewrite_module (shared)
>  setenvif_module (shared)
>  slotmem_shm_module (shared)
>  socache_shmcb_module (shared)
>  ssl_module (shared)
>  status_module (shared)
>  suexec_module (shared)
>  userdir_module (shared)
>
> Server2
> # apache2 -M
> Loaded Modules:
>  core_module (static)
>  so_module (static)
>  watchdog_module (static)
>  http_module (static)
>  log_config_module (static)
>  logio_module (static)
>  version_module (static)
>  unixd_module (static)
>  access_compat_module (shared)
>  aclr_module (shared)
>  actions_module (shared)
>  alias_module (shared)
>  auth_basic_module (shared)
>  auth_digest_module (shared)
>  auth_openidc_module (shared)
>  authn_core_module (shared)
>  authn_file_module (shared)
>  authz_core_module (shared)
>  authz_host_module (shared)
>  authz_user_module (shared)
>  autoindex_module (shared)
>  cgid_module (shared)
>  dav_module (shared)
>  dav_fs_module (shared)
>  dav_lock_module (shared)
>  deflate_module (shared)
>  dir_module (shared)
>  env_module (shared)
>  fcgid_module (shared)
>  filter_module (shared)
>  headers_module (shared)
>  include_module (shared)
>  mime_module (shared)
>  mpm_event_module (shared)
>  negotiation_module (shared)
>  proxy_module (shared)
>  proxy_balancer_module (shared)
>  proxy_fcgi_module (shared)
>  proxy_http_module (shared)
>  remoteip_module (shared)
>  reqtimeout_module (shared)
>  rewrite_module (shared)
>  security2_module (shared)
>  setenvif_module

Re: [users@httpd] Why so much difference in memory used per process in apache2 between two different systems

[Marc Serra]

Wow! The memory eater was security2 ...

With the module enabled (120-160MB per process) ...
# ps axo 'user rss cmd' | grep apache | grep -v "\(root\|grep\|tomcat\)"
www-data 121232 /usr/sbin/apache2 -k start
www-data 120596 /usr/sbin/apache2 -k start
www-data 156816 /usr/sbin/apache2 -k start
www-data 162668 /usr/sbin/apache2 -k start

With the module disabled (9-15MB per process) ...
# a2dismod security2
Module security2 disabled.
To activate the new configuration, you need to run:
  systemctl restart apache2
# systemctl restart apache2
# ps axo 'user rss cmd' | grep apache | grep -v "\(root\|grep\|tomcat\)"
www-data 10340 /usr/sbin/apache2 -k start
www-data  9764 /usr/sbin/apache2 -k start
www-data 14164 /usr/sbin/apache2 -k start
www-data 14220 /usr/sbin/apache2 -k start

Thank's for your answer Dino. That's enough for me.

I didn’t really think a module would cause this change in memory usage,
which is why I haven’t dedicated myself to disabling them one by one. But I
was clearly wrong. Thank you again.

For your information, my problem was understand why so much difference
between to systems because I want to optimize some parameters
like: ServerLimit, StartServers, MinSpareServers, MaxSpareServers,
MaxClients and MaxRequestsPerChild

I need to know the memory used per each Apache process to find
the MaxClients value.

Missatge de Dino Ciuffetti  del dia dl., 17 de maig 2021 a
les 14:54:
>
> Try to comment out mod_security, it's a module that use enough memory.
> Also on server2 there are modules not loaded on server1. BTW what's your
problem? Your server is plenty of ram and RSS memory is not creating any
problem. Right?
>
>
> 17 maggio 2021 13:34, "Marc Serra"  wrote:
>
> Hi to all,
> I already posted this question to stackoverflow.com but no answer after 9
days:
https://stackoverflow.com/questions/67439771/why-so-much-difference-in-memory-used-per-process-in-apache2-between-two-differe
> I hope the apache gurus in this list can help me :)
> I have a pair of Ubuntu dedicated servers...
>
> Server1:
> Ubuntu 16.04.7 (64 bits)
> 16GB RAM
> 8 Xeon CPU
> Apache 2.4.18
> MPM mode: prefork
>
> Server2:
> Ubuntu server 20.04.2 (64 bits)
> 32GB RAM
> 8 Xeon CPU
> 2.4.41
> MPM mode: event
>
> On Server1, each apache2 process uses between 7MB and 18MB of RAM ...
> # ps axo 'user rss cmd' | grep apache | grep -v "\(root\|grep\|tomcat\)"
> www-data 18232 /usr/sbin/apache2 -k start
> www-data 11700 /usr/sbin/apache2 -k start
> www-data 11276 /usr/sbin/apache2 -k start
> www-data 10792 /usr/sbin/apache2 -k start
> www-data 11216 /usr/sbin/apache2 -k start
> www-data 11600 /usr/sbin/apache2 -k start
> www-data 10336 /usr/sbin/apache2 -k start
> www-data 11356 /usr/sbin/apache2 -k start
> www-data 11348 /usr/sbin/apache2 -k start
> www-data 10980 /usr/sbin/apache2 -k start
> www-data 11316 /usr/sbin/apache2 -k start
> www-data 6808 /usr/sbin/apache2 -k start
>
> On Server2, each apache2 process uses between 120MB and 130MB of RAM ...
> # ps axo 'user rss cmd' | grep apache | grep -v "\(root\|grep\|tomcat\)"
> www-data 120436 /usr/sbin/apache2 -k start
> www-data 119784 /usr/sbin/apache2 -k start
> www-data 128720 /usr/sbin/apache2 -k start
> www-data 130208 /usr/sbin/apache2 -k start
>
> Why so much difference in memory used?
>
> After read a few documentation and googleing, I thought about loaded
modules, but there are not a lot of difference between each server...
>
> Server1
> # apache2 -M
> Loaded Modules:
> core_module (static)
> so_module (static)
> watchdog_module (static)
> http_module (static)
> log_config_module (static)
> logio_module (static)
> version_module (static)
> unixd_module (static)
> access_compat_module (shared)
> actions_module (shared)
> alias_module (shared)
> auth_basic_module (shared)
> auth_digest_module (shared)
> auth_openidc_module (shared)
> authn_core_module (shared)
> authn_file_module (shared)
> authz_core_module (shared)
> authz_host_module (shared)
> authz_user_module (shared)
> autoindex_module (shared)
> bw_module (shared)
> cgi_module (shared)
> dav_module (shared)
> dav_fs_module (shared)
> dav_lock_module (shared)
> deflate_module (shared)
> dir_module (shared)
> env_module (shared)
> expires_module (shared)
> fcgid_module (shared)
> filter_module (shared)
> headers_module (shared)
> include_module (shared)
> mime_module (shared)
> mpm_prefork_module (shared)
> negotiation_module (shared)
> proxy_module (shared)
> proxy_balancer_module (shared)
> proxy_fcgi_module (shared)
> proxy_http_module (shared)
> rewrite_module (shared)
> setenvif_module (shared)
> slotmem_shm_module (shared)
> socache_shmcb_module (shared)
> ssl_module (shared)
> status_module (shared)
> suexec_module (shared)
> userdir_module (shared)
> Server2
> # apache2 -M
> Loaded Modules:
> core_module (static)
> so_module (static)
> watchdog_module (static)
> http_module (static)
> log_config_module (static)
> logio_module (static)
> version_module (static)
> unixd_module (static)
> access_compat_module (sh

Re: [users@httpd] Why so much difference in memory used per process in apache2 between two different systems

[Marc Serra]

Thank's for answer Yann,

> MPM prefork is single threaded, while MPM event uses multiple threads,
> and each thread "consumes" 8MB of rss (for its stack) on a typical
> linux system.
> The default thread stack size can be changed with "ulimit -s" (or
> LimitSTACK= on systemd), depending on the loaded modules and their
> stack "consumption".
> I usually run httpd with "ulimit -s 512" (KB) without issues, but this
> needs testing in your environment (i.e. no crash)..


For me is new the ulimit command, I take a look in a near future.

-- 

Manxa 
1876, S.L. *
Ctra. 
Les Tries, 85. 17800 Olot (Girona)**Tel. 972 27 
45 30 Fax 972 27 45 32*


* Manxa Industrial | *Coneix
més aquí 




* Manxa Ferros | *Coneix
més aquí 




* Manxa Ferreteria i Parament de la Llar | 
*Coneix
més aquí 


**

-- 


El contingut d’aquest correu electrònic i els seus annexos és 
estrictament confidencial. En el cas que no siguis el destinatari i hagis 
rebut aquest missatge per error, preguem que ho comuniquis al remitent i 
procedeixis a la seva eliminació, sense difondre, emmagatzemar o copiar el 
seu contingut. Imprimeix aquest correu només si és necessari.

El contenido 
de este correo electrónico y sus anexos es estrictamente confidencial. En 
el caso de que no seas el destinatario y hayas recibido este mensaje por 
error, rogamos lo comuniques al remitente y procedas a su eliminación, sin 
difundir, almacenar o copiar su contenido. Imprimir este correo solo si es 
necesario.

The content of this email and its attachments is strictly 
confidential. If you are not the recipient and you have received this 
message by mistake, please notify the sender and proceed to its 
elimination, without spreading, storing or copying its content. Print this 
email only if necessary.

Le contenu de cet e-mail et de ses pièces jointes 
est strictement confidentiel. Dans le cas où vous n'êtes pas le 
destinataire et avez reçu ce message par erreur, veuillez en informer 
l'expéditeur et procéder à sa suppression, sans diffuser, stocker ou copier 
son contenu. Imprimez cet e-mail uniquement si nécessaire.

Re: [users@httpd] Why so much difference in memory used per process in apache2 between two different systems

[Marc Serra]

Thank's Daniel,

> The list of modules is different. I don't think you can compare event and
prefork servers as if they should behave the same, even more if you have a
different list of modules. Consider in prefork each process is a worker,
 while on event processes are not workers, but threads of each process.
> In order to compare fairly you have to use the same modules, same load,
similar resulting mpm settings and compare the total usage, still your
biggest concern unless you have a faulty module mostly will be CPU.
> Also consider there are some different modules in each case too, some are
third party modules.

As I already commented on my answer to Dino, I didn’t really think a module
would cause this change in memory usage, which is why I haven’t dedicated
myself to disabling them one by one. But I was clearly wrong. Thank you
again too!

-- 

Manxa 
1876, S.L. *
Ctra. 
Les Tries, 85. 17800 Olot (Girona)**Tel. 972 27 
45 30 Fax 972 27 45 32*


* Manxa Industrial | *Coneix
més aquí 




* Manxa Ferros | *Coneix
més aquí 




* Manxa Ferreteria i Parament de la Llar | 
*Coneix
més aquí 


**

-- 


El contingut d’aquest correu electrònic i els seus annexos és 
estrictament confidencial. En el cas que no siguis el destinatari i hagis 
rebut aquest missatge per error, preguem que ho comuniquis al remitent i 
procedeixis a la seva eliminació, sense difondre, emmagatzemar o copiar el 
seu contingut. Imprimeix aquest correu només si és necessari.

El contenido 
de este correo electrónico y sus anexos es estrictamente confidencial. En 
el caso de que no seas el destinatario y hayas recibido este mensaje por 
error, rogamos lo comuniques al remitente y procedas a su eliminación, sin 
difundir, almacenar o copiar su contenido. Imprimir este correo solo si es 
necesario.

The content of this email and its attachments is strictly 
confidential. If you are not the recipient and you have received this 
message by mistake, please notify the sender and proceed to its 
elimination, without spreading, storing or copying its content. Print this 
email only if necessary.

Le contenu de cet e-mail et de ses pièces jointes 
est strictement confidentiel. Dans le cas où vous n'êtes pas le 
destinataire et avez reçu ce message par erreur, veuillez en informer 
l'expéditeur et procéder à sa suppression, sans diffuser, stocker ou copier 
son contenu. Imprimez cet e-mail uniquement si nécessaire.

[users@httpd] Connect to a node instead of a cluster

[vadud3]

Hi All,

I have a load balancer setup like below


BalancerMember http://msts1acnf001:8098 route=1
BalancerMember http://msts1bcnf002:8098 route=2
BalancerMember http://msts1ccnf003:8098 route=3
ProxySet stickysession=ROUTEID


And each node running tomcat and has a context path setup



How do I configure it to access a node instead of the cluster? I do need
the cluster for users, but for admin sometimes need to access a node to
check its UI status.

Thanks,
Asif



-- 
Asif Iqbal
PGP Key: 0xE62693C5 KeyServer: pgp.mit.edu
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?

Re: [users@httpd] Connect to a node instead of a cluster

[Daniel Ferradal]

Define a ProxyPass directive with a unique path pointing to one of the node
you want to use

Hint
ProyPass /adminpath/ http://server1/admin/


El lun., 17 may. 2021 19:03,  escribió:

> Hi All,
>
> I have a load balancer setup like below
>
> 
> BalancerMember http://msts1acnf001:8098 route=1
> BalancerMember http://msts1bcnf002:8098 route=2
> BalancerMember http://msts1ccnf003:8098 route=3
> ProxySet stickysession=ROUTEID
> 
>
> And each node running tomcat and has a context path setup
>
>  reloadable="false" useHttpOnly="true">
>
> How do I configure it to access a node instead of the cluster? I do need
> the cluster for users, but for admin sometimes need to access a node to
> check its UI status.
>
> Thanks,
> Asif
>
>
>
> --
> Asif Iqbal
> PGP Key: 0xE62693C5 KeyServer: pgp.mit.edu
> A: Because it messes up the order in which people normally read text.
> Q: Why is top-posting such a bad thing?
>
>

Re: [users@httpd] Connect to a node instead of a cluster

[vadud3]

I do have this setup

ProxyPass /confluence balancer://confluencedc/confluence
ProxyPassReverse /confluence balancer://confluencedc/confluence

To access confluence node it needs to hit /confluence and that is already
taken by the above config and maps to the context path.

I am not sure if I have a second context path /adminpath and if I can I
suppose I will need to map it to same real dir?

Thanks,
Asif


On Mon, May 17, 2021 at 1:39 PM Daniel Ferradal 
wrote:

> Define a ProxyPass directive with a unique path pointing to one of the
> node you want to use
>
> Hint
> ProyPass /adminpath/ http://server1/admin/
>
>
> El lun., 17 may. 2021 19:03,  escribió:
>
>> Hi All,
>>
>> I have a load balancer setup like below
>>
>> 
>> BalancerMember http://msts1acnf001:8098 route=1
>> BalancerMember http://msts1bcnf002:8098 route=2
>> BalancerMember http://msts1ccnf003:8098 route=3
>> ProxySet stickysession=ROUTEID
>> 
>>
>> And each node running tomcat and has a context path setup
>>
>> > reloadable="false" useHttpOnly="true">
>>
>> How do I configure it to access a node instead of the cluster? I do need
>> the cluster for users, but for admin sometimes need to access a node to
>> check its UI status.
>>
>> Thanks,
>> Asif
>>
>>
>>
>> --
>> Asif Iqbal
>> PGP Key: 0xE62693C5 KeyServer: pgp.mit.edu
>> A: Because it messes up the order in which people normally read text.
>> Q: Why is top-posting such a bad thing?
>>
>>

-- 
Asif Iqbal
PGP Key: 0xE62693C5 KeyServer: pgp.mit.edu
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?

Re: [users@httpd] Connect to a node instead of a cluster

[Daniel Ferradal]

Yes, you need to use a different "source" path for the new directives,
destination path can be different but otherwise, how can apache tell when
to serve which?

El lun., 17 may. 2021 20:08,  escribió:

> I do have this setup
>
> ProxyPass /confluence balancer://confluencedc/confluence
> ProxyPassReverse /confluence balancer://confluencedc/confluence
>
> To access confluence node it needs to hit /confluence and that is already
> taken by the above config and maps to the context path.
>
> I am not sure if I have a second context path /adminpath and if I can I
> suppose I will need to map it to same real dir?
>
> Thanks,
> Asif
>
>
> On Mon, May 17, 2021 at 1:39 PM Daniel Ferradal 
> wrote:
>
>> Define a ProxyPass directive with a unique path pointing to one of the
>> node you want to use
>>
>> Hint
>> ProyPass /adminpath/ http://server1/admin/
>>
>>
>> El lun., 17 may. 2021 19:03,  escribió:
>>
>>> Hi All,
>>>
>>> I have a load balancer setup like below
>>>
>>> 
>>> BalancerMember http://msts1acnf001:8098 route=1
>>> BalancerMember http://msts1bcnf002:8098 route=2
>>> BalancerMember http://msts1ccnf003:8098 route=3
>>> ProxySet stickysession=ROUTEID
>>> 
>>>
>>> And each node running tomcat and has a context path setup
>>>
>>> >> reloadable="false" useHttpOnly="true">
>>>
>>> How do I configure it to access a node instead of the cluster? I do need
>>> the cluster for users, but for admin sometimes need to access a node to
>>> check its UI status.
>>>
>>> Thanks,
>>> Asif
>>>
>>>
>>>
>>> --
>>> Asif Iqbal
>>> PGP Key: 0xE62693C5 KeyServer: pgp.mit.edu
>>> A: Because it messes up the order in which people normally read text.
>>> Q: Why is top-posting such a bad thing?
>>>
>>>
>
> --
> Asif Iqbal
> PGP Key: 0xE62693C5 KeyServer: pgp.mit.edu
> A: Because it messes up the order in which people normally read text.
> Q: Why is top-posting such a bad thing?
>
>

[users@httpd] which bit ?

[back button]

 

Hi,

 

In my application  https://www.backbutton.org/

 

I placed the front end proxy server on the all new  64 Bit Rasperry Pi 4.

It is a wopping 64 bit  processor with 8GM Ram  running the on  linux  lsb_release Ubuntu 20.04 LTS.

 

I used the ubuntu 64 bit OS rather than Raspberry Pi OS because  Raspberry Pi OS was pulling down a different version

of Ubuntu server Apache HTTPD , did not not include all the Ubuntu utilities.

 

I understand that when I startup the HTTPD using systemctl start apache2, it rises directly into RAM

occupying the massive 8 GM of volatile memory. Then it starts listening for urls in the I/O buffer.

I understand the HTTPD socket server with its text parser mod(s) performs quite fast when running in RAM.

 

I have tried out two different bits used talk to HTTPD  with the back  end business logic application server(s) .

 

The first bit  I used is the  mod_jk.

 

This is the bit which talks to each other


LoadModule    jk_module  path/to/mod_jk.so
AddModule     mod_jk.c
JkWorkersFile /path/to/httpd/conf/workers.properties

 


The second bit I used is called mod_proxy.

this is the bit which talks to each other




BalancerMember http://127.0.0.1:8080
BalancerMember http://127.0.0.1:8081


ProxyPreserveHost On

ProxyPass / balancer://mycluster/
ProxyPassReverse / balancer://mycluster/



 

Both bits  I used to talk to each other work fine. The first bit and the second bit.

Questions 

I am a bit confused which bit should I use, the first bit or the second bit  ?

Are any other bit(s) I can also try out  for a bit of practice ?

 

favourite phrase:

How you like them Apples ?

 

 

 

 

 

 

 

-
To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org
For additional commands, e-mail: users-h...@httpd.apache.org

Re: [users@httpd] Connect to a node instead of a cluster

[vadud3]

I added this but it went to a different node instead of node 1 which is
msts1acnf001

ProxyPass /confluencenode1 http://msts1acnf001:8098/confluence
ProxyPassReverse /confluencenode1 http://msts1acnf001:8098/confluence

Any suggestion what am I doing wrong?

Thanks,
Asif




On Mon, May 17, 2021 at 2:18 PM Daniel Ferradal 
wrote:

> Yes, you need to use a different "source" path for the new directives,
> destination path can be different but otherwise, how can apache tell when
> to serve which?
>
> El lun., 17 may. 2021 20:08,  escribió:
>
>> I do have this setup
>>
>> ProxyPass /confluence balancer://confluencedc/confluence
>> ProxyPassReverse /confluence balancer://confluencedc/confluence
>>
>> To access confluence node it needs to hit /confluence and that is already
>> taken by the above config and maps to the context path.
>>
>> I am not sure if I have a second context path /adminpath and if I can I
>> suppose I will need to map it to same real dir?
>>
>> Thanks,
>> Asif
>>
>>
>> On Mon, May 17, 2021 at 1:39 PM Daniel Ferradal 
>> wrote:
>>
>>> Define a ProxyPass directive with a unique path pointing to one of the
>>> node you want to use
>>>
>>> Hint
>>> ProyPass /adminpath/ http://server1/admin/
>>>
>>>
>>> El lun., 17 may. 2021 19:03,  escribió:
>>>
 Hi All,

 I have a load balancer setup like below

 
 BalancerMember http://msts1acnf001:8098 route=1
 BalancerMember http://msts1bcnf002:8098 route=2
 BalancerMember http://msts1ccnf003:8098 route=3
 ProxySet stickysession=ROUTEID
 

 And each node running tomcat and has a context path setup

 >>> reloadable="false" useHttpOnly="true">

 How do I configure it to access a node instead of the cluster? I do
 need the cluster for users, but for admin sometimes need to access a node
 to check its UI status.

 Thanks,
 Asif



 --
 Asif Iqbal
 PGP Key: 0xE62693C5 KeyServer: pgp.mit.edu
 A: Because it messes up the order in which people normally read text.
 Q: Why is top-posting such a bad thing?


>>
>> --
>> Asif Iqbal
>> PGP Key: 0xE62693C5 KeyServer: pgp.mit.edu
>> A: Because it messes up the order in which people normally read text.
>> Q: Why is top-posting such a bad thing?
>>
>>

-- 
Asif Iqbal
PGP Key: 0xE62693C5 KeyServer: pgp.mit.edu
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?

Re: [users@httpd] Connect to a node instead of a cluster

[Eric Covener]

On Mon, May 17, 2021 at 2:51 PM  wrote:

> I added this but it went to a different node instead of node 1 which is
> msts1acnf001
>
> ProxyPass /confluencenode1 http://msts1acnf001:8098/confluence
> ProxyPassReverse /confluencenode1 http://msts1acnf001:8098/confluence
>
> Any suggestion what am I doing wrong?
>

There is a chance your app redirected you along the way and dropped the
custom prefix, I would look at recent access log entries when it fails. Or,
test with a command-line client or developer tools running in the browser.

Re: [users@httpd] Connect to a node instead of a cluster

[vadud3]

On Mon, May 17, 2021 at 2:59 PM Eric Covener  wrote:

>
>
> On Mon, May 17, 2021 at 2:51 PM  wrote:
>
>> I added this but it went to a different node instead of node 1 which is
>> msts1acnf001
>>
>> ProxyPass /confluencenode1 http://msts1acnf001:8098/confluence
>> ProxyPassReverse /confluencenode1 http://msts1acnf001:8098/confluence
>>
>> Any suggestion what am I doing wrong?
>>
>
> There is a chance your app redirected you along the way and dropped the
> custom prefix, I would look at recent access log entries when it fails. Or,
> test with a command-line client or developer tools running in the browser.
>
>
I see this in the vhost. access log

'192.168.0.36' '-' '-' 'proxy.example.com' '[17/May/2021:18:47:56 +]'
'GET /confluencenode1 HTTP/1.1' '302' '-' '-' '-' 'Mozilla/5.0 (Windows NT
10.0; Win64; x64; rv:78.0) Gecko/20100101 Firefox/78.0' '-' '-'i '-'

'192.168.0.36' '' '-' 'proxy.example.com' '[17/May/2021:18:47:56 +]'
'GET /confluence/ HTTP/1.1' '302' '465' '-' '-' 'Mozilla/5.0 (Windows NT
10.0; Win64; x64; rv:78.0) Gecko/20100101 Firefox/78.0' '-' '-'i ''

I do not see msts1acnf001 anywhere in the log




-- 
Asif Iqbal
PGP Key: 0xE62693C5 KeyServer: pgp.mit.edu
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?

Re: [users@httpd] Connect to a node instead of a cluster

[vadud3]

On Mon, May 17, 2021 at 4:29 PM  wrote:

>
>
> On Mon, May 17, 2021 at 2:59 PM Eric Covener  wrote:
>
>>
>>
>> On Mon, May 17, 2021 at 2:51 PM  wrote:
>>
>>> I added this but it went to a different node instead of node 1 which is
>>> msts1acnf001
>>>
>>> ProxyPass /confluencenode1 http://msts1acnf001:8098/confluence
>>> ProxyPassReverse /confluencenode1 http://msts1acnf001:8098/confluence
>>>
>>> Any suggestion what am I doing wrong?
>>>
>>
>> There is a chance your app redirected you along the way and dropped the
>> custom prefix, I would look at recent access log entries when it fails. Or,
>> test with a command-line client or developer tools running in the browser.
>>
>>
> I see this in the vhost. access log
>
> '192.168.0.36' '-' '-' 'proxy.example.com' '[17/May/2021:18:47:56 +]'
> 'GET /confluencenode1 HTTP/1.1' '302' '-' '-' '-' 'Mozilla/5.0 (Windows NT
> 10.0; Win64; x64; rv:78.0) Gecko/20100101 Firefox/78.0' '-' '-'i '-'
>
> '192.168.0.36' '' '-' 'proxy.example.com' '[17/May/2021:18:47:56 +]'
> 'GET /confluence/ HTTP/1.1' '302' '465' '-' '-' 'Mozilla/5.0 (Windows NT
> 10.0; Win64; x64; rv:78.0) Gecko/20100101 Firefox/78.0' '-' '-'i ''
>
> I do not see msts1acnf001 anywhere in the log
>


 Here is the snippet after adding the `/confluencenode1`


BalancerMember http://msts1acnf001:8098 route=1
BalancerMember http://msts1bcnf002:8098 route=2
BalancerMember http://msts1ccnf003:8098 route=3
ProxySet stickysession=ROUTEID

...
ProxyPass /confluencenode1 http://msts1acnf001:8098/confluence
ProxyPassReverse /confluencenode1 http://msts1acnf001:8098/confluence
...
ProxyPass /confluence balancer://confluencedc/confluence
ProxyPassReverse /confluence balancer://confluencedc/confluence

Not sure if the second proxypass interferring with the first one

Thanks,
Asif



>
> --
> Asif Iqbal
> PGP Key: 0xE62693C5 KeyServer: pgp.mit.edu
> A: Because it messes up the order in which people normally read text.
> Q: Why is top-posting such a bad thing?
>
>

-- 
Asif Iqbal
PGP Key: 0xE62693C5 KeyServer: pgp.mit.edu
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?

Re: [users@httpd] which bit ?

[Nick Folino]

Bit 5 has always been my favorite bit.  He just hangs out there between 6
and 4.  Nobody bothers him.
Plus you can't get past 15 without him.  He's a really good guy.
For what you called a horrible product you sure seem to want to figure it
out.
Keep reading.

On Mon, May 17, 2021 at 2:21 PM back button  wrote:

>
> Hi,
>
> In my application  https://www.backbutton.org/
>
> I placed the front end proxy server on the all new  64 Bit Rasperry Pi 4.
> It is a wopping 64 bit  processor with 8GM Ram  running the on  linux
> lsb_release Ubuntu 20.04 LTS.
>
> I used the ubuntu 64 bit OS rather than Raspberry Pi OS because  Raspberry
> Pi OS was pulling down a different version
> of Ubuntu server Apache HTTPD , did not not include all the Ubuntu
> utilities.
>
> I understand that when I startup the HTTPD using systemctl start apache2,
> it rises directly into RAM
> occupying the massive 8 GM of volatile memory. Then it starts listening
> for urls in the I/O buffer.
> I understand the HTTPD socket server with its text parser mod(s) performs
> quite fast when running in RAM.
>
> I have tried out two different bits used talk to HTTPD  with the back  end
> business logic application server(s) .
>
> The first bit  I used is the  mod_jk.
>
> This is the bit which talks to each other
>
> LoadModulejk_module  path/to/mod_jk.so
> AddModule mod_jk.c
> JkWorkersFile /path/to/httpd/conf/workers.properties
>
>
> The second bit I used is called mod_proxy.
> this is the bit which talks to each other
>
> 
> BalancerMember http://127.0.0.1:8080
> BalancerMember http://127.0.0.1:8081
>
> ProxyPreserveHost On
>
> ProxyPass / balancer://mycluster/
> ProxyPassReverse / balancer://mycluster/
>
>
> Both bits  I used to talk to each other work fine. The first bit and the
> second bit.
> *Questions *
> I am a bit confused which bit should I use, the first bit or the second
> bit  ?
> Are any other bit(s) I can also try out  for a bit of practice ?
>
> favourite phrase:
> How you like them Apples ?
>
>
>
>
>
>
>
> - To
> unsubscribe, e-mail: users-unsubscr...@httpd.apache.org For additional
> commands, e-mail: users-h...@httpd.apache.org

Re: [users@httpd] which bit ?

[Joan Touzet]

All:

I have read back a few weeks in the archives for posts from this
individual, "Back button." I do not see any contravention of the code of
conduct on the lists by Nick Folino, or other project members.

In fact, what I see is Nick asking "Back button" to tone it down, and
then because of repeated disregard for the list moderators, they were
removed from the mailing list for abuse by Eric Covener.

Regular list members, apologies for this intrusion on your time - feel
free to mute this thread in your MUA.

"Back Button," you went on ban-evaded by signing up to the mailing list
with a new address. It even appears that you set up a sock puppet
account to act as your daughter to complain to the mailing list.

So, "Back button," the code of conduct contravention here is your own
actions. You are not being concise. You are assuming bad intentions. You
were asked to stop posting, and you did not. And, finally, you are
picking arguments because you are not personally being catered to.

As an open source developer of nearly 30 years, I can tell you this:
what you're doing is *not* how you go about asking for help, not from
other users, and especially not from the maintainers of a project.

The Apache License v2.0 (under which httpd is distributed) states you
get permission to do whatever you want with the code, subject to a
license and copyright notice, and notification of state changes, with
limitations around liability, trademark use, and - most importantly -
**zero warranty**.

No one on this list is obligated to help you with your problem. These
are people giving freely of their time to try and resolve your problems.
Please be respectful of their limitations, and understand that your
actions to date do not inspire those here to give more of their time to
help you out.

In fact, quoting from the Apache License v2.0: You get the code "on an
'AS IS' BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either
express or implied." It then goes on to say that "**YOU** [emphasis
mine] are solely responsible for determining the appropriateness of
using... the Work and assume any risks associated"

Finally, at the risk of upsetting you, I want to cite a reference. In a
famous GitHub post from 2014[1], Steve Klabnik summed it up perfectly:
"You are the reason people burn out on open source. Don't be such an
ass." It is entirely possible for you to seek the help you need
regarding httpd, but everything you have shown to date suggests you are
the problem here, not the members of the users@httpd.apache.org mailing
list.

Best regards,
Joan Touzet

[1]: https://github.com/wpeterson/emoji/issues/23

On 18/05/2021 00:53, back Button wrote:
> Fact: 
> All Java EE compliant application servers have the same directory
> structure , so all Java EE applications are portable and familiar to
> developers, including tomcat which is not fully Java EE compliant.
> 
> Apache HTTPD versions contradict this.
> There isn't even a recognition anywhere that this  should be an
> expectation. You are not going to get it anyway.
> 
> You did not answer any questions regarding this nor shed any light on it.
> 
> You goal is just to try to bother me.
> 
> FAO: Joan Touzet Apache  code of conduct. 
> 
> Ms. Touzet please have a look at this email account's history in the
> archives . You will find all his messages are either derogatory towards
> me or about. 
> 
> 
> 
> back.but...@aol.com
> 
> 
> On Monday, 17 May 2021, 23:53:23 BST, Nick Folino  wrote:
> 
> 
> Bit 5 has always been my favorite bit.  He just hangs out there between
> 6 and 4.  Nobody bothers him.
> Plus you can't get past 15 without him.  He's a really good guy.
> For what you called a horrible product you sure seem to want to figure
> it out.
> Keep reading.
> 
> On Mon, May 17, 2021 at 2:21 PM back button  > wrote:
> 
>  
> Hi,
>  
> In my application  https://www.backbutton.org/
> 
>  
> I placed the front end proxy server on the all new  64 Bit Rasperry
> Pi 4.
> It is a wopping 64 bit  processor with 8GM Ram  running the on 
> linux  lsb_release Ubuntu 20.04 LTS.
>  
> I used the ubuntu 64 bit OS rather than Raspberry Pi OS because 
> Raspberry Pi OS was pulling down a different version
> of Ubuntu server Apache HTTPD , did not not include all the Ubuntu
> utilities.
>  
> I understand that when I startup the HTTPD using systemctl start
> apache2, it rises directly into RAM
> occupying the massive 8 GM of volatile memory. Then it starts
> listening for urls in the I/O buffer.
> I understand the HTTPD socket server with its text parser mod(s)
> performs quite fast when running in RAM.
>  
> I have tried out two different bits used talk to HTTPD  with the
> back  end business logic application server(s) .
>  
> The first bit  I used is the  mod_jk.
>  
> This is the bit which talks to each other
>