[JBoss JIRA] (WFLY-5688) mod_cluster subsystem remains silent if connector set to http
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFLY-5688?page=com.atlassian.jira.plugin.... ]
Brian Stansberry commented on WFLY-5688:
----------------------------------------
This sounds like a referential integrity issue to be solved via a capability published by the undertow subsystem and required by the modcluster subsystem.
> mod_cluster subsystem remains silent if connector set to http
> -------------------------------------------------------------
>
> Key: WFLY-5688
> URL: https://issues.jboss.org/browse/WFLY-5688
> Project: WildFly
> Issue Type: Feature Request
> Components: Clustering, Web (Undertow)
> Affects Versions: 10.0.0.CR4
> Reporter: Michal Karm Babacek
> Assignee: Radoslav Husar
> Labels: ux
>
> If one sets mod_cluster subsystem {{connector="http"}} there is nothing in the log about any mod_cluster subsystem being initialized, no warning, nothing. It appears to be dead silent even with log level DEBUG.
> When switched back to {{connector="ajp"}}, there are the well known comforting messages:
> {noformat}
> INFO [org.jboss.modcluster] (ServerService Thread Pool -- 62) MODCLUSTER000001: Initializing mod_cluster version 1.3.1.Final
> INFO [org.jboss.modcluster] (ServerService Thread Pool -- 62) MODCLUSTER000032: Listening to proxy advertisements on /224.0.1.105:23364
> {noformat}
> Weird. Any obvious misconfiguration or explanation? The config is the default standalone-ha.xml otherwise.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 7 months
[JBoss JIRA] (WFLY-5688) mod_cluster subsystem remains silent if connector set to http
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFLY-5688?page=com.atlassian.jira.plugin.... ]
Brian Stansberry updated WFLY-5688:
-----------------------------------
Component/s: Clustering
Web (Undertow)
> mod_cluster subsystem remains silent if connector set to http
> -------------------------------------------------------------
>
> Key: WFLY-5688
> URL: https://issues.jboss.org/browse/WFLY-5688
> Project: WildFly
> Issue Type: Feature Request
> Components: Clustering, Web (Undertow)
> Affects Versions: 10.0.0.CR4
> Reporter: Michal Karm Babacek
> Assignee: Radoslav Husar
> Labels: ux
>
> If one sets mod_cluster subsystem {{connector="http"}} there is nothing in the log about any mod_cluster subsystem being initialized, no warning, nothing. It appears to be dead silent even with log level DEBUG.
> When switched back to {{connector="ajp"}}, there are the well known comforting messages:
> {noformat}
> INFO [org.jboss.modcluster] (ServerService Thread Pool -- 62) MODCLUSTER000001: Initializing mod_cluster version 1.3.1.Final
> INFO [org.jboss.modcluster] (ServerService Thread Pool -- 62) MODCLUSTER000032: Listening to proxy advertisements on /224.0.1.105:23364
> {noformat}
> Weird. Any obvious misconfiguration or explanation? The config is the default standalone-ha.xml otherwise.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 7 months
[JBoss JIRA] (WFCORE-1253) Flag modules to be loaded in a distinct classloader context
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1253?page=com.atlassian.jira.plugi... ]
Brian Stansberry moved WFLY-3670 to WFCORE-1253:
------------------------------------------------
Project: WildFly Core (was: WildFly)
Key: WFCORE-1253 (was: WFLY-3670)
> Flag modules to be loaded in a distinct classloader context
> -----------------------------------------------------------
>
> Key: WFCORE-1253
> URL: https://issues.jboss.org/browse/WFCORE-1253
> Project: WildFly Core
> Issue Type: Feature Request
> Reporter: Wolf-Dieter Fink
> Assignee: Jason Greene
>
> For some use-cases it will be helpful to have a module in a separate classloader (as copy) if it is used from different applications.
> An example is if the module includes classes which follow the singleton pattern but the singleton should be per application instead of instance wide.
> There are two possiblities to flag that
> - within the module.xml
> - within the module reference MAIFEST or jboss-deployment-structure.xml
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 7 months