[mod_cluster-issues] [JBoss JIRA] (MODCLUSTER-467) ExcludedContexts are ignored if modcluster subsystem initialize before default-host
Radoslav Husar (JIRA)
issues at jboss.org
Mon Apr 16 11:02:00 EDT 2018
[ https://issues.jboss.org/browse/MODCLUSTER-467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Radoslav Husar closed MODCLUSTER-467.
-------------------------------------
Assignee: Radoslav Husar (was: Jean-Frederic Clere)
Resolution: Duplicate Issue
Labels: (was: jboss)
This is a duplicate of MODCLUSTER-566 and the related integration issues (WFLY-6863) – if this is not the case, please reopen.
> ExcludedContexts are ignored if modcluster subsystem initialize before default-host
> -----------------------------------------------------------------------------------
>
> Key: MODCLUSTER-467
> URL: https://issues.jboss.org/browse/MODCLUSTER-467
> Project: mod_cluster
> Issue Type: Bug
> Components: Core & Container Integration (Java)
> Affects Versions: 1.2.11.Final
> Reporter: Pierre-Luc Gregoire
> Assignee: Radoslav Husar
> Attachments: MODCLUSTER-467-patch.diff
>
>
> With JBoss 7.2.0.Final, modcluster will ignore excludedContexts defined in modcluster subsystem (ie jmx-console, ROOT). This is caused by engine.getHosts() not yet available when org.jboss.modcluster.ModClusterService.init(Server) try to setup his list of excludedContexts.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
More information about the mod_cluster-issues
mailing list