[JBoss JIRA] Created: (MODCLUSTER-120) Apache with mod_cluster refuses to start at first, after 7 retries it starts up
by Radoslav Husar (JIRA)
Apache with mod_cluster refuses to start at first, after 7 retries it starts up
-------------------------------------------------------------------------------
Key: MODCLUSTER-120
URL: https://jira.jboss.org/jira/browse/MODCLUSTER-120
Project: mod_cluster
Issue Type: Bug
Affects Versions: 1.0.2.GA
Environment: x64, RHEL 5, Server version: Apache/2.2.3, Server built: Jul 6 2009 05:29:28
Reporter: Radoslav Husar
Assignee: Jean-Frederic Clere
When starting up Apache with mod cluster, by command:
[hudson@perf10 httpd]$ /usr/sbin/apachectl -k start -d /tmp/hudson/httpd
It refuses to start, but creates files in logs one-by-one and then when all files are created it accepts to start.
[hudson@perf10 httpd]$ cat logs/error_log
[Tue Jan 05 12:01:11 2010] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Tue Jan 05 12:01:11 2010] [notice] Digest: generating secret for digest authentication ...
[Tue Jan 05 12:01:11 2010] [notice] Digest: done
[Tue Jan 05 12:01:11 2010] [emerg] create_mem_node /tmp/hudson/httpd/logs/manager.node failed
Configuration Failed
[Tue Jan 05 12:01:37 2010] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Tue Jan 05 12:01:37 2010] [notice] Digest: generating secret for digest authentication ...
[Tue Jan 05 12:01:37 2010] [notice] Digest: done
[Tue Jan 05 12:01:37 2010] [emerg] create_mem_context failed
Configuration Failed
[Tue Jan 05 12:02:40 2010] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Tue Jan 05 12:02:40 2010] [notice] Digest: generating secret for digest authentication ...
[Tue Jan 05 12:02:40 2010] [notice] Digest: done
[Tue Jan 05 12:02:40 2010] [emerg] create_mem_host failed
Configuration Failed
[Tue Jan 05 12:04:43 2010] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Tue Jan 05 12:04:43 2010] [notice] Digest: generating secret for digest authentication ...
[Tue Jan 05 12:04:43 2010] [notice] Digest: done
[Tue Jan 05 12:04:43 2010] [emerg] create_mem_balancer failed
Configuration Failed
[Tue Jan 05 12:04:44 2010] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Tue Jan 05 12:04:44 2010] [notice] Digest: generating secret for digest authentication ...
[Tue Jan 05 12:04:44 2010] [notice] Digest: done
[Tue Jan 05 12:04:44 2010] [emerg] create_mem_sessionid failed
Configuration Failed
[Tue Jan 05 12:04:45 2010] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Tue Jan 05 12:04:45 2010] [notice] Digest: generating secret for digest authentication ...
[Tue Jan 05 12:04:45 2010] [notice] Digest: done
[Tue Jan 05 12:04:45 2010] [emerg] create_mem_domain failed
Configuration Failed
[Tue Jan 05 12:04:46 2010] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Tue Jan 05 12:04:46 2010] [notice] Digest: generating secret for digest authentication ...
[Tue Jan 05 12:04:46 2010] [notice] Digest: done
[Tue Jan 05 12:04:46 2010] [notice] Advertise initialized for process 1713
[Tue Jan 05 12:04:46 2010] [notice] Apache/2.2.3 (Red Hat) configured -- resuming normal operations
The configuration is here:
https://svn.devel.redhat.com/repos/jboss-qa/load-testing/etc/httpd/mod_cl...
Is there a workaround? What might be causing this?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years
[JBoss JIRA] Created: (MODCLUSTER-91) Connector bind address of 0.0.0.0 propagated to proxy
by Brian Stansberry (JIRA)
Connector bind address of 0.0.0.0 propagated to proxy
-----------------------------------------------------
Key: MODCLUSTER-91
URL: https://jira.jboss.org/jira/browse/MODCLUSTER-91
Project: mod_cluster
Issue Type: Bug
Affects Versions: 1.0.1.GA
Reporter: Brian Stansberry
Assignee: Jean-Frederic Clere
Marek Goldmann wrote:
> I'm encountered a strange error. When I bind JBoss instance to 0.0.0.0
> address instead of a fixed ethernet address, node gets registered in
> mod_cluster, shows in mod_cluster-manager, but every request to
> registered contexts throws 503 error.
>
> httpd error log:
>
> [Fri Aug 07 03:21:05 2009] [error] (111)Connection refused: proxy:
> ajp: attempt to connect to 0.0.0.0:8009 (0.0.0.0) failed
> [Fri Aug 07 03:21:05 2009] [error] ap_proxy_connect_backend disabling
> worker for (0.0.0.0)
> [Fri Aug 07 03:21:15 2009] [error] proxy: ajp: disabled connection for
> (0.0.0.0)
> [Fri Aug 07 03:21:25 2009] [error] proxy: ajp: disabled connection for
> (0.0.0.0)
>
> This looks like a bug for me, because many administrators are binding
> JBoss to 0.0.0.0.
The java side needs to understand that 0.0.0.0 is useless as a client address and send something useful. Trick is deciding what's useful.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 4 months
[JBoss JIRA] Created: (MODCLUSTER-112) Refactor project into modules for HA, catalina, core, etc.
by Paul Ferraro (JIRA)
Refactor project into modules for HA, catalina, core, etc.
----------------------------------------------------------
Key: MODCLUSTER-112
URL: https://jira.jboss.org/jira/browse/MODCLUSTER-112
Project: mod_cluster
Issue Type: Sub-task
Reporter: Paul Ferraro
Assignee: Jean-Frederic Clere
Restructure maven project to create separate module jars.
mod-cluster-spi: ContainerEventHandler, Server, Engine, Connector, Host, Context
mod-cluster-core: ModClusterService and dependencies
mod-cluster-ha: HAModClusterService and dependencies
mod-cluster-catalina: ModClusterListener, CatalinaEventHandlerAdapter and spi implementation
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 11 months
[JBoss JIRA] Created: (MODCLUSTER-151) Modify jbossweb metrics to use service provider spi, instead of jmx
by Paul Ferraro (JIRA)
Modify jbossweb metrics to use service provider spi, instead of jmx
-------------------------------------------------------------------
Key: MODCLUSTER-151
URL: https://jira.jboss.org/jira/browse/MODCLUSTER-151
Project: mod_cluster
Issue Type: Feature Request
Affects Versions: 1.1.0.CR1
Reporter: Paul Ferraro
Assignee: Paul Ferraro
Currently, the jbossweb load metrics (i.e. ActiveSessionsLoadMetric, BusyConnectorsLoadMetric, RequestCountLoadMetric, ReceiveTrafficLoadMetric, SendTrafficLoadMetric) use jmx to generate their load values.
This is potentially fragile.
Instead, these load metrics should use org.jboss.mod_cluster.Engine as a load context.
This raises the issue of load value scope. Currently, load is scoped to a server. Really, this should be scoped to an engine. While server:engine is usually a 1:1 relationship, this is technically a 1:N relationship.
Suggested API change:
class LoadMetricSource<C extends LoadContext>
{
C createContext(Engine engine);
}
Where there exists:
class EngineLoadMetricSource<EngineLoadContext>
{
public EngineLoadContext createContext(Engine engine)
{
return new EngineLoadContext(engine);
}
}
class EngineLoadContext implements LoadContext
{
private final Engine engine;
public EngineLoadContext(Engine engine)
{
this.engine = engine;
}
public Engine getEngine()
{
return this.engine;
}
public void close()
{
// Nothing to close
}
}
The various jbossweb load metrics would use this source.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 11 months
[JBoss JIRA] Created: (MODCLUSTER-119) AdvertiseBindAddress does not default to the 23364 port
by Radoslav Husar (JIRA)
AdvertiseBindAddress does not default to the 23364 port
-------------------------------------------------------
Key: MODCLUSTER-119
URL: https://jira.jboss.org/jira/browse/MODCLUSTER-119
Project: mod_cluster
Issue Type: Bug
Affects Versions: 1.0.2.GA
Environment: Fedora 11
Reporter: Radoslav Husar
Assignee: Jean-Frederic Clere
Hello,
it looks as though 1.0.2 GA does not pick the default value for AdvertiseBindAddress and listens on random port each time whereas the documentation claims it defaults to the same setup as the AS part default setup.
The docs say: AdvertiseBindAddress IP:port: That is the address and port httpd is bind to send the multicast messages. This allow to specify an address on multi IP address boxes. Default: 0.0.0.0:23364
Here is the different starts/stops and ports, below the host config without ABA set.
[rhusar@rhusar modcluster]$ netstat -lpn | grep http
(Not all processes could be identified, non-owned process info
will not be shown, you would have to be root to see it all.)
tcp 0 0 :::8888 :::* LISTEN 19610/httpd
udp 0 0 0.0.0.0:60958 0.0.0.0:* 19610/httpd
[rhusar@rhusar modcluster]$ netstat -lpn | grep http
(Not all processes could be identified, non-owned process info
will not be shown, you would have to be root to see it all.)
tcp 0 0 :::8888 :::* LISTEN 19648/httpd
udp 0 0 0.0.0.0:34758 0.0.0.0:* 19648/httpd
[rhusar@rhusar modcluster]$ netstat -lpn | grep http
(Not all processes could be identified, non-owned process info
will not be shown, you would have to be root to see it all.)
tcp 0 0 :::8888 :::* LISTEN 19676/httpd
udp 0 0 0.0.0.0:58988 0.0.0.0:* 19676/httpd
<VirtualHost *:8888>
KeepAliveTimeout 60
MaxKeepAliveRequests 0
ManagerBalancerName mycluster
AdvertiseFrequency 5
# File a Jira - not in sync with docs
# http://www.jboss.org/mod_cluster/native/config.html
# AdvertiseBindAddress 0.0.0.0:23364
</VirtualHost>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 7 months