[JBoss JIRA] (WFCORE-402) Get core resources and operations out of the controller module
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-402?page=com.atlassian.jira.plugin... ]
Brian Stansberry updated WFCORE-402:
------------------------------------
Fix Version/s: (was: 1.0.0.Beta1)
> Get core resources and operations out of the controller module
> --------------------------------------------------------------
>
> Key: WFCORE-402
> URL: https://issues.jboss.org/browse/WFCORE-402
> Project: WildFly Core
> Issue Type: Task
> Components: Domain Management
> Reporter: Brian Stansberry
>
> The controller module has a lot of classes related to core resources (resource defs, op handlers, description providers for things like interfaces) that are only in there so they can be commonly accessible to both server and host-controller. This is unnecessary, since host-controller depends on server.
> Either move these to server or create a separate module for this stuff; restrict the controller module to the true core ModelController stuff.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 7 months
[JBoss JIRA] (WFCORE-398) Avoid running out of threads when connecting to the DC from a slave to pull down missing data
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-398?page=com.atlassian.jira.plugin... ]
Brian Stansberry resolved WFCORE-398.
-------------------------------------
Fix Version/s: (was: 1.0.0.Beta1)
Resolution: Out of Date
I don't believe this thread starvation problem still exists, as the pool used for these requests is not limited. Emmanuel, please re-open if I'm incorrect.
> Avoid running out of threads when connecting to the DC from a slave to pull down missing data
> ---------------------------------------------------------------------------------------------
>
> Key: WFCORE-398
> URL: https://issues.jboss.org/browse/WFCORE-398
> Project: WildFly Core
> Issue Type: Feature Request
> Components: Domain Management
> Reporter: Kabir Khan
> Assignee: Emanuel Muckenhuber
> Priority: Blocker
>
> For WFLY-259 when a slave connects to the DC to pull down missing data, it does this by either getting a lock for the DC, or by joining the permit of the existing DC lock if the request to update a slave's server-config was executed as part of a composite obtaining a lock on the DC.
> The way it works at present there is a thread per slave which is blocked until the transaction completes. The DC threads are a finite resource, so a large number of slaves trying to pull down dats will cause deadlock
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 7 months
[JBoss JIRA] (WFLY-3935) cluster-ha-singleton fails to deploy when the server is started with the debug flag
by Paul Ferraro (JIRA)
[ https://issues.jboss.org/browse/WFLY-3935?page=com.atlassian.jira.plugin.... ]
Paul Ferraro closed WFLY-3935.
------------------------------
Fix Version/s: 9.0.0.Beta1
Resolution: Out of Date
Closing as out-of-date, given that it does not affect master (9.x), and there are no more 8.x releases planned.
> cluster-ha-singleton fails to deploy when the server is started with the debug flag
> -----------------------------------------------------------------------------------
>
> Key: WFLY-3935
> URL: https://issues.jboss.org/browse/WFLY-3935
> Project: WildFly
> Issue Type: Bug
> Components: Clustering
> Affects Versions: 8.1.0.Final
> Reporter: Euan Mapham
> Assignee: Paul Ferraro
> Fix For: 9.0.0.Beta1
>
>
> When a clustered-ha-singleton is deployed to a wildfly server that was started using the --debug option, a org.jboss.msc.service.ServiceNotFoundException occurrs.
> I am using the quickstart/cluster-ha-singleton found on github:
> https://github.com/wildfly/quickstart/tree/master/cluster-ha-singleton
> Wildfly version 8.1.0.Final
> I start the server with this command:
> ./bin/standalone.sh --debug -server-config=standalone-ha.xml -Djboss.node.name=jb.node1
> I then deploy the wildfly-cluster-ha-singleton-service.jar.
> The exception that occurrs is:
> 15:03:31,803 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC000001: Failed to start service jboss.deployment.unit."wildfly-cluster-ha-singleton-service.jar".INSTALL: org.jboss.msc.service.StartException in service jboss.deployment.unit."wildfly-cluster-ha-singleton-service.jar".INSTALL: JBAS018733: Failed to process phase INSTALL of deployment "wildfly-cluster-ha-singleton-service.jar"
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:166) [wildfly-server-8.1.0.Final.jar:8.1.0.Final]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) [jboss-msc-1.2.2.Final.jar:1.2.2.Final]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) [jboss-msc-1.2.2.Final.jar:1.2.2.Final]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_20]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_20]
> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_20]
> Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: org.jboss.msc.service.ServiceNotFoundException: Service service jboss.clustering.singleton.builder.server.default not found
> at org.jboss.as.server.deployment.service.ServiceActivatorProcessor.deploy(ServiceActivatorProcessor.java:72) [wildfly-server-8.1.0.Final.jar:8.1.0.Final]
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:159) [wildfly-server-8.1.0.Final.jar:8.1.0.Final]
> ... 5 more
> Caused by: org.jboss.msc.service.ServiceNotFoundException: Service service jboss.clustering.singleton.builder.server.default not found
> at org.jboss.msc.service.ServiceContainerImpl.getRequiredService(ServiceContainerImpl.java:668) [jboss-msc-1.2.2.Final.jar:1.2.2.Final]
> at org.jboss.msc.service.DelegatingServiceRegistry.getRequiredService(DelegatingServiceRegistry.java:46) [jboss-msc-1.2.2.Final.jar:1.2.2.Final]
> at org.jboss.as.quickstarts.cluster.hasingleton.service.ejb.HATimerServiceActivator.install(HATimerServiceActivator.java:51)
> at org.jboss.as.quickstarts.cluster.hasingleton.service.ejb.HATimerServiceActivator.activate(HATimerServiceActivator.java:44)
> at org.jboss.as.server.deployment.service.ServiceActivatorProcessor.deploy(ServiceActivatorProcessor.java:70) [wildfly-server-8.1.0.Final.jar:8.1.0.Final]
> ... 6 more
> When I remove the "--debug" option from the command to start the server, everything works fine.
> This means we cannot debug our applications if we use this feature.
> Regards,
> Euan
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 7 months
[JBoss JIRA] (WFCORE-442) AbstractMultiTargetHandler-based handlers do not propagate failures to the top level failure-description
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-442?page=com.atlassian.jira.plugin... ]
Brian Stansberry commented on WFCORE-442:
-----------------------------------------
I haven't looked carefully, but a likely place to put this is in the ResultHandler that GlobalOperationHandlers.ModelAddressResolver passes to OperationContext.completeStep.
Note that it is *critical* in this work to make sure we don't leak resource addresses via a failure description that RBAC is trying to hide. The current stuff in that ResultHandler is about that requirement, and must not be broken. Use git annotate to understand the history and purpose of that code.
> AbstractMultiTargetHandler-based handlers do not propagate failures to the top level failure-description
> --------------------------------------------------------------------------------------------------------
>
> Key: WFCORE-442
> URL: https://issues.jboss.org/browse/WFCORE-442
> Project: WildFly Core
> Issue Type: Bug
> Components: Domain Management
> Affects Versions: 1.0.0.Alpha13
> Reporter: Brian Stansberry
>
> An example is worth a thousand words:
> {code}
> [standalone@localhost:9990 /] /path=*:query(where={read-only=1})
> {
> "outcome" => "failed",
> "result" => [
> {
> "address" => [("path" => "jboss.server.temp.dir")],
> "outcome" => "failed",
> "result" => {
> "name" => "jboss.server.temp.dir",
> "path" => "/Users/hbraun/dev/prj/wildfly-core/core-build/target/wildfly-core-1.0.0.Alpha14-SNAPSHOT/standalone/tmp",
> "read-only" => true,
> "relative-to" => undefined
> },
> "rolled-back" => true
> },
> {
> "address" => [("path" => "user.home")],
> "outcome" => "failed",
> "result" => {
> "name" => "user.home",
> "path" => "/Users/hbraun",
> "read-only" => true,
> "relative-to" => undefined
> },
> "rolled-back" => true
> },
> {
> "address" => [("path" => "jboss.server.base.dir")],
> "outcome" => "failed",
> "result" => {
> "name" => "jboss.server.base.dir",
> "path" => "/Users/hbraun/dev/prj/wildfly-core/core-build/target/wildfly-core-1.0.0.Alpha14-SNAPSHOT/standalone",
> "read-only" => true,
> "relative-to" => undefined
> },
> "rolled-back" => true
> },
> {
> "address" => [("path" => "java.home")],
> "outcome" => "failed",
> "result" => {
> "name" => "java.home",
> "path" => "/Library/Java/JavaVirtualMachines/jdk1.7.0_67.jdk/Contents/Home/jre",
> "read-only" => true,
> "relative-to" => undefined
> },
> "rolled-back" => true
> },
> {
> "address" => [("path" => "user.dir")],
> "outcome" => "failed",
> "result" => {
> "name" => "user.dir",
> "path" => "/Users/hbraun/dev/prj/wildfly-core/core-build/target/wildfly-core-1.0.0.Alpha14-SNAPSHOT",
> "read-only" => true,
> "relative-to" => undefined
> },
> "rolled-back" => true
> },
> {
> "address" => [("path" => "jboss.server.data.dir")],
> "outcome" => "failed",
> "result" => {
> "name" => "jboss.server.data.dir",
> "path" => "/Users/hbraun/dev/prj/wildfly-core/core-build/target/wildfly-core-1.0.0.Alpha14-SNAPSHOT/standalone/data",
> "read-only" => true,
> "relative-to" => undefined
> },
> "rolled-back" => true
> },
> {
> "address" => [("path" => "jboss.home.dir")],
> "outcome" => "failed",
> "result" => {
> "name" => "jboss.home.dir",
> "path" => "/Users/hbraun/dev/prj/wildfly-core/core-build/target/wildfly-core-1.0.0.Alpha14-SNAPSHOT",
> "read-only" => true,
> "relative-to" => undefined
> },
> "rolled-back" => true
> },
> {
> "address" => [("path" => "jboss.server.log.dir")],
> "outcome" => "failed",
> "result" => {
> "name" => "jboss.server.log.dir",
> "path" => "/Users/hbraun/dev/prj/wildfly-core/core-build/target/wildfly-core-1.0.0.Alpha14-SNAPSHOT/standalone/log",
> "read-only" => true,
> "relative-to" => undefined
> },
> "rolled-back" => true
> },
> {
> "address" => [("path" => "jboss.server.config.dir")],
> "outcome" => "failed",
> "result" => {
> "name" => "jboss.server.config.dir",
> "path" => "/Users/hbraun/dev/prj/wildfly-core/core-build/target/wildfly-core-1.0.0.Alpha14-SNAPSHOT/standalone/configuration",
> "read-only" => true,
> "relative-to" => undefined
> },
> "rolled-back" => true
> },
> {
> "address" => [("path" => "jboss.controller.temp.dir")],
> "outcome" => "failed",
> "result" => {
> "name" => "jboss.controller.temp.dir",
> "path" => "/Users/hbraun/dev/prj/wildfly-core/core-build/target/wildfly-core-1.0.0.Alpha14-SNAPSHOT/standalone/tmp",
> "read-only" => true,
> "relative-to" => undefined
> },
> "failure-description" => "Illegal argument for attribute 'read-only'. Expected type BOOLEAN",
> "rolled-back" => true
> }
> ],
> "rolled-back" => true
> }
> {code}
> One item in the set has a failure description but the overall response does not.
> ReadResourceDescriptionHandler handles similar things but has logic for creating an overall failure-description.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 7 months
[JBoss JIRA] (WFLY-4147) WildFly full feature pack references unresolved artifact
by Stan Silvert (JIRA)
Stan Silvert created WFLY-4147:
----------------------------------
Summary: WildFly full feature pack references unresolved artifact
Key: WFLY-4147
URL: https://issues.jboss.org/browse/WFLY-4147
Project: WildFly
Issue Type: Bug
Components: Build System
Affects Versions: 9.0.0.Alpha1
Reporter: Stan Silvert
Assignee: Stuart Douglas
I have a server-provisioning.xml outside of the WildFly build. It looks like this:
{code:xml}
<server-provisioning xmlns="urn:wildfly:server-provisioning:1.0">
<feature-packs>
<feature-pack groupId="org.wildfly" artifactId="wildfly-feature-pack" version="${project.version}"/>
</feature-packs>
</server-provisioning>
{code}
When I build, I get:
{noformat}
[ERROR] Failed to execute goal org.wildfly.build:wildfly-server-provisioning-maven-plugin:1.0.0.Alpha6:build (server-provisioning) on project wildfly-build: Execution ser
ver-provisioning of goal org.wildfly.build:wildfly-server-provisioning-maven-plugin:1.0.0.Alpha6:build failed: java.lang.RuntimeException: java.lang.RuntimeException: fai
led to resolve artifact org.wildfly:wildfly-client-all:jar:9.0.0.Alpha1: Failure to find org.wildfly:wildfly-client-all:jar:9.0.0.Alpha1 in http://repository.jboss.org/ne
xus/content/groups/public/ was cached in the local repository, resolution will not be reattempted until the update interval of jboss-public-repository-group has elapsed o
r updates are forced -> [Help 1]
{noformat}
The problem is that wildfly-client-all is not pushed to the Maven repo. This will only work if wildfly-client-all is already in your local repo.
Looks like wildfly-client-all simply should not be referenced in the feature pack.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 7 months
[JBoss JIRA] (WFCORE-442) AbstractMultiTargetHandler-based handlers do not propagate failures to the top level failure-description
by Brian Stansberry (JIRA)
Brian Stansberry created WFCORE-442:
---------------------------------------
Summary: AbstractMultiTargetHandler-based handlers do not propagate failures to the top level failure-description
Key: WFCORE-442
URL: https://issues.jboss.org/browse/WFCORE-442
Project: WildFly Core
Issue Type: Bug
Components: Domain Management
Affects Versions: 1.0.0.Alpha13
Reporter: Brian Stansberry
An example is worth a thousand words:
{code]
[standalone@localhost:9990 /] /path=*:query(where={read-only=1})
{
"outcome" => "failed",
"result" => [
{
"address" => [("path" => "jboss.server.temp.dir")],
"outcome" => "failed",
"result" => {
"name" => "jboss.server.temp.dir",
"path" => "/Users/hbraun/dev/prj/wildfly-core/core-build/target/wildfly-core-1.0.0.Alpha14-SNAPSHOT/standalone/tmp",
"read-only" => true,
"relative-to" => undefined
},
"rolled-back" => true
},
{
"address" => [("path" => "user.home")],
"outcome" => "failed",
"result" => {
"name" => "user.home",
"path" => "/Users/hbraun",
"read-only" => true,
"relative-to" => undefined
},
"rolled-back" => true
},
{
"address" => [("path" => "jboss.server.base.dir")],
"outcome" => "failed",
"result" => {
"name" => "jboss.server.base.dir",
"path" => "/Users/hbraun/dev/prj/wildfly-core/core-build/target/wildfly-core-1.0.0.Alpha14-SNAPSHOT/standalone",
"read-only" => true,
"relative-to" => undefined
},
"rolled-back" => true
},
{
"address" => [("path" => "java.home")],
"outcome" => "failed",
"result" => {
"name" => "java.home",
"path" => "/Library/Java/JavaVirtualMachines/jdk1.7.0_67.jdk/Contents/Home/jre",
"read-only" => true,
"relative-to" => undefined
},
"rolled-back" => true
},
{
"address" => [("path" => "user.dir")],
"outcome" => "failed",
"result" => {
"name" => "user.dir",
"path" => "/Users/hbraun/dev/prj/wildfly-core/core-build/target/wildfly-core-1.0.0.Alpha14-SNAPSHOT",
"read-only" => true,
"relative-to" => undefined
},
"rolled-back" => true
},
{
"address" => [("path" => "jboss.server.data.dir")],
"outcome" => "failed",
"result" => {
"name" => "jboss.server.data.dir",
"path" => "/Users/hbraun/dev/prj/wildfly-core/core-build/target/wildfly-core-1.0.0.Alpha14-SNAPSHOT/standalone/data",
"read-only" => true,
"relative-to" => undefined
},
"rolled-back" => true
},
{
"address" => [("path" => "jboss.home.dir")],
"outcome" => "failed",
"result" => {
"name" => "jboss.home.dir",
"path" => "/Users/hbraun/dev/prj/wildfly-core/core-build/target/wildfly-core-1.0.0.Alpha14-SNAPSHOT",
"read-only" => true,
"relative-to" => undefined
},
"rolled-back" => true
},
{
"address" => [("path" => "jboss.server.log.dir")],
"outcome" => "failed",
"result" => {
"name" => "jboss.server.log.dir",
"path" => "/Users/hbraun/dev/prj/wildfly-core/core-build/target/wildfly-core-1.0.0.Alpha14-SNAPSHOT/standalone/log",
"read-only" => true,
"relative-to" => undefined
},
"rolled-back" => true
},
{
"address" => [("path" => "jboss.server.config.dir")],
"outcome" => "failed",
"result" => {
"name" => "jboss.server.config.dir",
"path" => "/Users/hbraun/dev/prj/wildfly-core/core-build/target/wildfly-core-1.0.0.Alpha14-SNAPSHOT/standalone/configuration",
"read-only" => true,
"relative-to" => undefined
},
"rolled-back" => true
},
{
"address" => [("path" => "jboss.controller.temp.dir")],
"outcome" => "failed",
"result" => {
"name" => "jboss.controller.temp.dir",
"path" => "/Users/hbraun/dev/prj/wildfly-core/core-build/target/wildfly-core-1.0.0.Alpha14-SNAPSHOT/standalone/tmp",
"read-only" => true,
"relative-to" => undefined
},
"failure-description" => "Illegal argument for attribute 'read-only'. Expected type BOOLEAN",
"rolled-back" => true
}
],
"rolled-back" => true
}
{code}
One item in the set has a failure description but the overall response does not.
ReadResourceDescriptionHandler handles similar things but has logic for creating an overall failure-description.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 7 months