[JBoss JIRA] (WFLY-7443) Capability org.wildfly.undertow.listener needs a well defined contract
by Stuart Douglas (JIRA)
Stuart Douglas created WFLY-7443:
------------------------------------
Summary: Capability org.wildfly.undertow.listener needs a well defined contract
Key: WFLY-7443
URL: https://issues.jboss.org/browse/WFLY-7443
Project: WildFly
Issue Type: Bug
Components: Security
Reporter: Brian Stansberry
Assignee: Ingo Weiss
The contract for this capability needs examination and recording in the registry.
Note that the task here is not to just create a meaningless entry. Once the entry is published a contract is established, so the contract has to be correct. ListenerService doesn't look like a good API to be exposed to external callers; it exposes details that probably should not be part of a contract.
--
This message was sent by Atlassian JIRA
(v7.2.2#72004)
9 years, 6 months
[JBoss JIRA] (WFLY-7440) Deployments using multiple singleton services can hang when using non-ha profiles
by Paul Ferraro (JIRA)
Paul Ferraro created WFLY-7440:
----------------------------------
Summary: Deployments using multiple singleton services can hang when using non-ha profiles
Key: WFLY-7440
URL: https://issues.jboss.org/browse/WFLY-7440
Project: WildFly
Issue Type: Bug
Components: Clustering
Affects Versions: 10.1.0.Final
Reporter: Paul Ferraro
Assignee: Paul Ferraro
Since we don't know what a user may do in their Service.start(...), stop(...) methods, we should always install these asynchronously so that we don't block MSC threads. The service exposed to the ServiceController for these asynchronously started services must still implement Singleton.
--
This message was sent by Atlassian JIRA
(v7.2.2#72004)
9 years, 6 months
[JBoss JIRA] (WFLY-7441) Deployments using multiple singleton services can hang when using non-ha profiles
by Paul Ferraro (JIRA)
Paul Ferraro created WFLY-7441:
----------------------------------
Summary: Deployments using multiple singleton services can hang when using non-ha profiles
Key: WFLY-7441
URL: https://issues.jboss.org/browse/WFLY-7441
Project: WildFly
Issue Type: Bug
Components: Clustering
Affects Versions: 10.1.0.Final
Reporter: Paul Ferraro
Assignee: Paul Ferraro
Since we don't know what a user may do in their Service.start(...), stop(...) methods, we should always install these asynchronously so that we don't block MSC threads. The service exposed to the ServiceController for these asynchronously started services must still implement Singleton.
--
This message was sent by Atlassian JIRA
(v7.2.2#72004)
9 years, 6 months
[JBoss JIRA] (WFCORE-1917) Deprecate "reload", "suspend" and "resume" ops on the server-config resource
by Brian Stansberry (JIRA)
Brian Stansberry created WFCORE-1917:
----------------------------------------
Summary: Deprecate "reload", "suspend" and "resume" ops on the server-config resource
Key: WFCORE-1917
URL: https://issues.jboss.org/browse/WFCORE-1917
Project: WildFly Core
Issue Type: Task
Components: Domain Management
Reporter: Brian Stansberry
The /host=x/server-config=y resource is a configuration chunk meant to describe how the HC should set up a server, not an actual runtime resource that represents the server. The runtime resource is /host=x/server=y. But in the early days of AS7 we hadn't worked out how to have a resource for /host=x/server=y when y wasn't actually started, so as a workaround we stuck 'runtime' ops like start/stop/restart on server-config. But that was never conceptually right; it was just a workaround.
But then we mistakenly expanded on that by sticking ops like 'reload', 'resume' and 'suspend' on the server-config resource as well. We should deprecate these so we can get rid of them in a future release (EAP 8).
Right now they don't work very well; e.g. you can reload, suspend or resume a 'server-config' that isn't even started and the op will succeed. But that's not something this JIRA is meant to address; I'm just pointing it out as evidence of why having these ops on this resource type is conceptually a mess.
--
This message was sent by Atlassian JIRA
(v7.2.2#72004)
9 years, 6 months