[1.2.x] Revise MODCLUSTER-332 fix. #40
Conversation
|
This is what our documentation for Tomcat says to configure the status interval! If we can't change BackgroundProcessorDelay then we should be using our own thread. |
|
"This is what our documentation for Tomcat says to configure the status interval!" Where I need to fix that. |
Remove unused Engine.getBackgroundProcessorDelay() method. Replace ambiguous org.jboss.modcluster.container.catalina.WAITSTATUS system property with more intuitive org.jboss.modcluster.container.catalina.status-frequency property which indicates the frequency with switch to perform STATUS processing with respect to the backgroundProcessorDelay.. Convert tab indentation to spaces.
|
OK - I've reimplemented this to use a "org.jboss.modcluster.container.catalina.status-frequency" system property which will perform STATUS processing every Nth interval, where N defaults to 1. This is similar to the logic used in the old HAModClusterService. |
|
@jfclere I guess this isn't in our main documentation, but rather is documented the comments of the the configuration file we ship for AS5/6 integration: https://github.com/modcluster/mod_cluster/blob/master/src/main/resources/mod_cluster-jboss-beans.xml We should probably remove this file altogether at some point... |
|
OK I will merge that later and adjust the JIRA. |
[1.2.x] Revise MODCLUSTER-332 fix.
Remove unused Engine.getBackgroundProcessorDelay() method.
Replace ambiguous org.jboss.modcluster.container.catalina.WAITSTATUS system property with more intuitive org.jboss.modcluster.container.catalina.status-interval property.
Convert tab indentation to spaces.