[ https://jira.jboss.org/jira/browse/MODCLUSTER-21?page=com.atlassian.jira.... ]
Paul Ferraro commented on MODCLUSTER-21:
----------------------------------------
The idea was to invert the dependency chain such that mod_cluster either depends on the WebServer bean, or declares itself as a dependent of the WebServer bean. The latter is not possible (according to Ales). The former causes mod_cluster to miss lifecycle events. Brian's suggest won't work since this behavior was deprecated in the microcontainer. I think the approach we use now is probably the best way forward.
> Adding a dependency on ModClusterService/HAModClusterService to the WebServer MC bean.
> --------------------------------------------------------------------------------------
>
> Key: MODCLUSTER-21
> URL: https://jira.jboss.org/jira/browse/MODCLUSTER-21
> Project: mod_cluster
> Issue Type: Feature Request
> Reporter: Jean-Frederic Clere
> Assignee: Jean-Frederic Clere
>
--
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
[ https://jira.jboss.org/jira/browse/MODCLUSTER-20?page=com.atlassian.jira.... ]
Paul Ferraro commented on MODCLUSTER-20:
----------------------------------------
For the AS, yes - to avoid the WARN in the log.
However, org.jboss.web.tomcat.service.deployers.MicrocontainerIntegrationLifecycleListener doesn't exist in JBW-standalone, so this jira issue is stll relevant - albeit less important.
> Adding the lifecycle listener dynamically
> -----------------------------------------
>
> Key: MODCLUSTER-20
> URL: https://jira.jboss.org/jira/browse/MODCLUSTER-20
> Project: mod_cluster
> Issue Type: Feature Request
> Reporter: Jean-Frederic Clere
> Assignee: Paul Ferraro
>
--
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
[ https://jira.jboss.org/jira/browse/MODCLUSTER-20?page=com.atlassian.jira.... ]
Jean-Frederic Clere reassigned MODCLUSTER-20:
---------------------------------------------
Assignee: Paul Ferraro (was: Jean-Frederic Clere)
<Listener className="org.jboss.web.tomcat.service.deployers.MicrocontainerIntegrationLifecycleListener"
delegateBeanName="ModClusterListener" failIfBeanMissing="false" warnIfBeanMissing="false"/>
Is the answer, no?
> Adding the lifecycle listener dynamically
> -----------------------------------------
>
> Key: MODCLUSTER-20
> URL: https://jira.jboss.org/jira/browse/MODCLUSTER-20
> Project: mod_cluster
> Issue Type: Feature Request
> Reporter: Jean-Frederic Clere
> Assignee: Paul Ferraro
>
--
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
[ https://jira.jboss.org/jira/browse/MODCLUSTER-21?page=com.atlassian.jira.... ]
Jean-Frederic Clere closed MODCLUSTER-21.
-----------------------------------------
Resolution: Done
The way is to have something like:
<Listener className="org.jboss.web.tomcat.service.deployers.MicrocontainerIntegrationLifecycleListener"
delegateBeanName="ModClusterListener" failIfBeanMissing="false" warnIfBeanMissing="false"/>
in the server.xml
and adding the depend in META-INF/jboss-beans.xml
<depends>ModClusterListener</depends>
> Adding a dependency on ModClusterService/HAModClusterService to the WebServer MC bean.
> --------------------------------------------------------------------------------------
>
> Key: MODCLUSTER-21
> URL: https://jira.jboss.org/jira/browse/MODCLUSTER-21
> Project: mod_cluster
> Issue Type: Feature Request
> Reporter: Jean-Frederic Clere
> Assignee: Jean-Frederic Clere
>
--
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
advertise doesn't use new AdvertiseSecurityKey on graceful restarts.
--------------------------------------------------------------------
Key: MODCLUSTER-129
URL: https://jira.jboss.org/jira/browse/MODCLUSTER-129
Project: mod_cluster
Issue Type: Bug
Affects Versions: 1.1.0.Beta1, 1.0.3.GA, 1.0.2.GA, 1.0.1.GA, 1.0.0.GA, 1.0.0.CR2, 1.0.0.CR1, 1.0.0.Beta4, 1.0.0.Beta3, 1.0.0.Beta2, 1.0.0.Beta1
Environment: any
Reporter: Jean-Frederic Clere
Assignee: Jean-Frederic Clere
Priority: Minor
Fix For: 1.1.0.CR1
change the AdvertiseSecurityKey in httpd.conf do apachectl graceful .... Advertise still use the old secret.
--
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
move the web site to magnolia
-----------------------------
Key: MODCLUSTER-114
URL: https://jira.jboss.org/jira/browse/MODCLUSTER-114
Project: mod_cluster
Issue Type: Feature Request
Environment: The web site needs to be migrated.
Reporter: Jean-Frederic Clere
Assignee: Jean-Frederic Clere
Fix For: 1.1.0.CR1
shell scripts will be used for downloads and docs. Docs will be reviewed and edited by hands.
--
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
Disabling contexts does not work
--------------------------------
Key: MODCLUSTER-123
URL: https://jira.jboss.org/jira/browse/MODCLUSTER-123
Project: mod_cluster
Issue Type: Bug
Affects Versions: 1.0.2.GA
Environment: RHEL 5.4
Reporter: Radoslav Husar
Assignee: Jean-Frederic Clere
Disabling contexts does not work and it keeps connecting on disabled contexts on the specified node (neither does 'disable all contexts' option).
Note that in mod_cluster-manager it displays correctly that its disabled.
--
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
Microcontainer does not choose the right constructor when creating RequestCountLoadMetric
-----------------------------------------------------------------------------------------
Key: MODCLUSTER-126
URL: https://jira.jboss.org/jira/browse/MODCLUSTER-126
Project: mod_cluster
Issue Type: Bug
Affects Versions: 1.1.0.Beta1
Reporter: Takayoshi Kimura
Assignee: Paul Ferraro
Fix For: 1.1.0.CR1
The MODCLUSTER-116 problem also applies to RequestCountLoadMetric, ReceiveTrafficLoadMetric and SendTrafficLoadMetric.
DEPLOYMENTS IN ERROR:
Deployment "RequestCountLoadMetric" is in error due to the following reason(s): **ERROR**, java.lang.IllegalArgumentException: Wrong arguments. new for target java.lang.reflect.Constructor expected=[org.jboss.modcluster.load.metric.DeterministicLoadState] actual=[org.jboss.modcluster.load.metric.impl.RequestProcessorLoadMetricSource]
--
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