[JBoss JIRA] Created: (MODCLUSTER-221) Only 100 webapps are detected : Maxcontext doesn't seem to be read
5:29 p.m.
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@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@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
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
9:29 a.m.
New subject: [JBoss JIRA] Commented: (MODCLUSTER-221) Only 100 webapps are detected : Maxcontext doesn't seem to be read
[
https://issues.jboss.org/browse/MODCLUSTER-221?page=com.atlassian.jira.pl...
]
Jean-Frederic Clere commented on MODCLUSTER-221:
------------------------------------------------
I guess that you have put Maxcontext in the wrong VirtualHost.
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@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@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
11:15 a.m.
New subject: [JBoss JIRA] Commented: (MODCLUSTER-221) Only 100 webapps are detected : Maxcontext doesn't seem to be read
[
https://issues.jboss.org/browse/MODCLUSTER-221?page=com.atlassian.jira.pl...
]
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@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@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
11:17 a.m.
New subject: [JBoss JIRA] Updated: (MODCLUSTER-221) Only 100 webapps are detected : Maxcontext doesn't seem to be read
[
https://issues.jboss.org/browse/MODCLUSTER-221?page=com.atlassian.jira.pl...
]
Baptiste MATHUS updated MODCLUSTER-221:
---------------------------------------
Attachment: httpd.conf
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@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@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
Attachments: httpd.conf
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
11:17 a.m.
New subject: [JBoss JIRA] Issue Comment Edited: (MODCLUSTER-221) Only 100 webapps are detected : Maxcontext doesn't seem to be read
[
https://issues.jboss.org/browse/MODCLUSTER-221?page=com.atlassian.jira.pl...
]
Baptiste MATHUS edited comment on MODCLUSTER-221 at 4/6/11 5:17 AM:
--------------------------------------------------------------------
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}
{code}
# 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
{code}
{quote}
I'm also attaching the full httpd.conf in case there's a problem somewhere else.
Thanks a lot!
was (Author: bmathus):
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@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@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
Attachments: httpd.conf
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
11:19 a.m.
New subject: [JBoss JIRA] Issue Comment Edited: (MODCLUSTER-221) Only 100 webapps are detected : Maxcontext doesn't seem to be read
[
https://issues.jboss.org/browse/MODCLUSTER-221?page=com.atlassian.jira.pl...
]
Baptiste MATHUS edited comment on MODCLUSTER-221 at 4/6/11 5:17 AM:
--------------------------------------------------------------------
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 AllowDisplay, 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}
{code}
# 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
{code}
{quote}
I'm also attaching the full httpd.conf in case there's a problem somewhere else.
Thanks a lot!
was (Author: bmathus):
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}
{code}
# 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
{code}
{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@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@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
Attachments: httpd.conf
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
10:03 a.m.
New subject: [JBoss JIRA] Commented: (MODCLUSTER-221) Only 100 webapps are detected : Maxcontext doesn't seem to be read
[
https://issues.jboss.org/browse/MODCLUSTER-221?page=com.atlassian.jira.pl...
]
Baptiste MATHUS commented on MODCLUSTER-221:
--------------------------------------------
For the record, I put the Maxcontext outside the VirtualHost block, no better.
Really wondering if this param is ever read? Couldn't there possibly be a typo
somewhere in the code that reads this parameter?
Cheers
Thanks.
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@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@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
Attachments: httpd.conf
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
3:32 p.m.
New subject: [JBoss JIRA] Commented: (MODCLUSTER-221) Only 100 webapps are detected : Maxcontext doesn't seem to be read
[
https://issues.jboss.org/browse/MODCLUSTER-221?page=com.atlassian.jira.pl...
]
Jean-Frederic Clere commented on MODCLUSTER-221:
------------------------------------------------
According to my traces it is read correctly.
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@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@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
Attachments: httpd.conf
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
3:43 p.m.
New subject: [JBoss JIRA] Commented: (MODCLUSTER-221) Only 100 webapps are detected : Maxcontext doesn't seem to be read
[
https://issues.jboss.org/browse/MODCLUSTER-221?page=com.atlassian.jira.pl...
]
Baptiste MATHUS commented on MODCLUSTER-221:
--------------------------------------------
You mean there's a trace somewhere about that, or did you add something in your local
code to track this?
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@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@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
Attachments: httpd.conf
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
4:37 p.m.
New subject: [JBoss JIRA] Commented: (MODCLUSTER-221) Only 100 webapps are detected : Maxcontext doesn't seem to be read
[
https://issues.jboss.org/browse/MODCLUSTER-221?page=com.atlassian.jira.pl...
]
Jean-Frederic Clere commented on MODCLUSTER-221:
------------------------------------------------
I added a trace to check.
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@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@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
Attachments: httpd.conf
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
11:19 a.m.
New subject: [JBoss JIRA] Commented: (MODCLUSTER-221) Only 100 webapps are detected : Maxcontext doesn't seem to be read
[
https://issues.jboss.org/browse/MODCLUSTER-221?page=com.atlassian.jira.pl...
]
Jean-Frederic Clere commented on MODCLUSTER-221:
------------------------------------------------
With r550 I had a test for it... It seems to work... Weird.
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.0.9, 1.1.1.Final
Environment: RHEL5,
JBOSS EAP 5.1.0.GA,
JDK Sun 1.6.0_22,
[root@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@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
Attachments: httpd.conf
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
11:19 a.m.
New subject: [JBoss JIRA] Updated: (MODCLUSTER-221) Only 100 webapps are detected : Maxcontext doesn't seem to be read
[
https://issues.jboss.org/browse/MODCLUSTER-221?page=com.atlassian.jira.pl...
]
Jean-Frederic Clere updated MODCLUSTER-221:
-------------------------------------------
Affects Version/s: 1.0.9
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.0.9, 1.1.1.Final
Environment: RHEL5,
JBOSS EAP 5.1.0.GA,
JDK Sun 1.6.0_22,
[root@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@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
Attachments: httpd.conf
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
1:41 p.m.
New subject: [JBoss JIRA] Commented: (MODCLUSTER-221) Only 100 webapps are detected : Maxcontext doesn't seem to be read
[
https://issues.jboss.org/browse/MODCLUSTER-221?page=com.atlassian.jira.pl...
]
Baptiste MATHUS commented on MODCLUSTER-221:
--------------------------------------------
For the record, now it works. I somehow had mixed things with an old and the new
httpd.conf file.
Aftert making sure I'm using the right one, it's ok.
Btw, an additional note in the documentation would be great precising where Maxcontext
should be put (outside VHost declaration), unlike AllowDisplay.
Thanks for your help.
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.0.9, 1.1.1.Final
Environment: RHEL5,
JBOSS EAP 5.1.0.GA,
JDK Sun 1.6.0_22,
[root@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@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
Attachments: httpd.conf
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
4:35 p.m.
New subject: [JBoss JIRA] Commented: (MODCLUSTER-221) Only 100 webapps are detected : Maxcontext doesn't seem to be read
[
https://issues.jboss.org/browse/MODCLUSTER-221?page=com.atlassian.jira.pl...
]
Jean-Frederic Clere commented on MODCLUSTER-221:
------------------------------------------------
Now you get an error message if the directive is not in the main server (r531)
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.0.9, 1.1.1.Final
Environment: RHEL5,
JBOSS EAP 5.1.0.GA,
JDK Sun 1.6.0_22,
[root@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@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
Attachments: httpd.conf
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
4:37 p.m.
New subject: [JBoss JIRA] Resolved: (MODCLUSTER-221) Only 100 webapps are detected : Maxcontext doesn't seem to be read
[
https://issues.jboss.org/browse/MODCLUSTER-221?page=com.atlassian.jira.pl...
]
Jean-Frederic Clere resolved MODCLUSTER-221.
--------------------------------------------
Resolution: Done
by user report + r531 for an error message.
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.0.9, 1.1.1.Final
Environment: RHEL5,
JBOSS EAP 5.1.0.GA,
JDK Sun 1.6.0_22,
[root@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@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
Attachments: httpd.conf
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
10:56 a.m.
New subject: [JBoss JIRA] Updated: (MODCLUSTER-221) Only 100 webapps are detected : Maxcontext doesn't seem to be read
[
https://issues.jboss.org/browse/MODCLUSTER-221?page=com.atlassian.jira.pl...
]
Radoslav Husar updated MODCLUSTER-221:
--------------------------------------
Fix Version/s: 1.0.10
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.0.9, 1.1.1.Final
Environment: RHEL5,
JBOSS EAP 5.1.0.GA,
JDK Sun 1.6.0_22,
[root@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@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
Fix For: 1.0.10
Attachments: httpd.conf
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
4754
days inactive
4763
days old
mod_cluster-issues@lists.jboss.org
15 comments
3 participants
participants (3)
-
Baptiste MATHUS (JIRA) -
Jean-Frederic Clere (JIRA)
-
Radoslav Husar (JIRA)