-
1. Re: mod_cluster 1.1.0 and tomcat 6.0.29 issues and questions
jfclere Aug 30, 2010 9:14 AM (in response to huksley)1) if not configured it goes to NullLoggerPlugin. May be that should be in docs.
2) docs too.
3) Not sure why you think it is wrong... The Allow from xxx.xxx.xxx.xx should be a subnet (usually the intranet) additionally it should be in a VirtualHost and you can use proxyURL to use another URL than /
4) yes that 2 independant things.
5) yes but see 3.
6) hm what have you done exactly?
-
2. Re: mod_cluster 1.1.0 and tomcat 6.0.29 issues and questions
huksley Aug 30, 2010 9:28 AM (in response to jfclere)Thanks for quick response!
1. Logging configured incorrectly.
In ModClusterListener.java there is some attempts to actually initialize logging, but somehow it does not work.
if (Logger.getPluginClassName() == null) {
String pluginClass = "org.jboss.logging.jdk.JDK14LoggerPlugin";
ModClusterListener.class.getClassLoader().loadClass(pluginClass);
// We can load it, so let's use it
Logger.setPluginClassName(pluginClass);
}Maybe we should file a bug?
2. ROOT context is actually not excluded.
Docs states ROOT excluded by default, however it is not. I have to manually specify excludedContexts="ROOT,manager,host-manager"
3. Apache httpd permissions not compatible with production systems, IMHO.
If looking into perspective of potentiallly large clusters and networks it is not known beforehand
which subnet to use.
Also, proxyURL is not in the current docs.
6. It is not clear when context mounting information is reloaded.
> hm what have you done exactly?
I have not specified excludedContexts on the first run. After that /
got overrun by tomcat and other web applications (non java, php based) were not working. -
3. Re: mod_cluster 1.1.0 and tomcat 6.0.29 issues and questions
jfclere Aug 31, 2010 2:56 AM (in response to huksley)1) ok fill a JIRA.
2) ok the default doesn't seem to be applied to Tomcat, fill a JIRA.
3) proxyURL See http://docs.jboss.org/mod_cluster/1.1.0/html/java.properties.html
6) that looks like a bug (the contexts of the previous CONFIG seem to be reused) fill a JIRA.
-
4. Re: mod_cluster 1.1.0 and tomcat 6.0.29 issues and questions
huksley Aug 31, 2010 7:38 AM (in response to jfclere)1) https://jira.jboss.org/browse/MODCLUSTER-185
2) https://jira.jboss.org/browse/MODCLUSTER-186
6) I am unable to provide any details or exact steps to reproduce this problem now, so
I don`t think it is good to add vague bug report.
-
5. Re: mod_cluster 1.1.0 and tomcat 6.0.29 issues and questions
pferraro Aug 31, 2010 12:15 PM (in response to jfclere)Regarding #2, there is no hard coded default value for excludedContexts.
The default value for excludedContexts as identified in the documentation actually refers to the default JBoss AS configuration that we ship with mod_cluster. Several of the configuration properties in the docs use the default values from the mod_cluster-jboss-beans.xml file. However, since we don't ship a default Tomcat server.xml, these default values do not apply. Perhaps we should?
In summary, I don't think this is a bug (i.e. it would be inappropriate to hard code defaults value that are specific to Tomcat), but rather a documentation issue.
In fact, now that JBoss AS includes mod_cluster by default, we should consider eventually dropping the mod_cluster.sar packaging (which contains mod_cluster-jboss-beans.xml) entirely.
Thoughts?