[mod_cluster-issues] [JBoss JIRA] Commented: (MODCLUSTER-221) Only 100 webapps are detected : Maxcontext doesn't seem to be read

[Baptiste MATHUS (JIRA)]

    [ https://issues.jboss.org/browse/MODCLUSTER-221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12593954#comment-12593954 ] 

Baptiste MATHUS commented on MODCLUSTER-221:
--------------------------------------------

Sorry, I wanted to attach my httpd.conf, but in the end I forgot.

Where should I put Maxcontext?
I put Maxcontext just next to Allow, and this one worked fine (I now see the additional information under /mod_cluster-manager), so I don't think 

Here's the corresponding excerpt:
{quote}
# Configuration Clustering JBoss
LoadModule slotmem_module modules/mod_slotmem.so
LoadModule manager_module modules/mod_manager.so
LoadModule proxy_cluster_module modules/mod_proxy_cluster.so
LoadModule advertise_module modules/mod_advertise.so

Listen sv-t-vtl-sv3lb:6666
<VirtualHost sv-t-vtl-sv3lb:6666>
  <Directory />
    Order deny,allow
    Deny from all
    Allow from 10.
  </Directory>
KeepAliveTimeout 60
MaxKeepAliveRequests 0
Maxcontext 400
AllowDisplay On

ManagerBalancerName migscaleCluster
AdvertiseFrequency 5
<Location /mod_cluster-manager>
SetHandler mod_cluster-manager
Order deny,allow
Deny from all
Allow from 10.
</Location>
</VirtualHost>
# Fin configuration Clustering JBoss
{quote}

I'm also attaching the full httpd.conf in case there's a problem somewhere else.

Thanks a lot!

> Only 100 webapps are detected : Maxcontext doesn't seem to be read
> ------------------------------------------------------------------
>
>                 Key: MODCLUSTER-221
>                 URL: https://issues.jboss.org/browse/MODCLUSTER-221
>             Project: mod_cluster
>          Issue Type: Bug
>    Affects Versions: 1.1.1.Final
>         Environment: RHEL5, 
> JBOSS EAP 5.1.0.GA, 
> JDK Sun 1.6.0_22,
> [root at LB ~/provisionning-from-scratch]$ httpd -V
> Server version: Apache/2.2.3
> Server built:   Mar  4 2010 09:57:54
> Server's Module Magic Number: 20051115:3
> Server loaded:  APR 1.2.7, APR-Util 1.2.7
> Compiled using: APR 1.2.7, APR-Util 1.2.7
> Architecture:   64-bit
> Server MPM:     Prefork
>   threaded:     no
>     forked:     yes (variable process count)
> Server compiled with....
>  -D APACHE_MPM_DIR="server/mpm/prefork"
>  -D APR_HAS_SENDFILE
>  -D APR_HAS_MMAP
>  -D APR_HAVE_IPV6 (IPv4-mapped addresses enabled)
>  -D APR_USE_SYSVSEM_SERIALIZE
>  -D APR_USE_PTHREAD_SERIALIZE
>  -D SINGLE_LISTEN_UNSERIALIZED_ACCEPT
>  -D APR_HAS_OTHER_CHILD
>  -D AP_HAVE_RELIABLE_PIPED_LOGS
>  -D DYNAMIC_MODULE_LIMIT=128
>  -D HTTPD_ROOT="/etc/httpd"
>  -D SUEXEC_BIN="/usr/sbin/suexec"
>  -D DEFAULT_PIDLOG="run/httpd.pid"
>  -D DEFAULT_SCOREBOARD="logs/apache_runtime_status"
>  -D DEFAULT_LOCKFILE="logs/accept.lock"
>  -D DEFAULT_ERRORLOG="logs/error_log"
>  -D AP_TYPES_CONFIG_FILE="conf/mime.types"
>  -D SERVER_CONFIG_FILE="conf/httpd.conf"
> [17:25:43][root at LB ~/provisionning-from-scratch]$ httpd -v
> Server version: Apache/2.2.3
> Server built:   Mar  4 2010 09:57:54
>            Reporter: Baptiste MATHUS
>            Assignee: Jean-Frederic Clere
>              Labels: httpd, jboss-as
>
> We're currently testing an architecture where we deploy 70 webapps in a 3-nodes cluster.
> After some times wondering why only some of the webapps were visible in the /mod_cluster-manager URL, we discovered that a Maxcontext parameter existed and was defaulting to 100.
> Then we set the Maxcontext parameter to 400, but it doesn't seem to change anything. Still only 100 webapp contexts are detected.
> I tried having a look at the C source code, but I don't see anything obvious. 
> Maybe this parameter is just not read?
> Thanks a lot for your help.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira