[JBoss JIRA] (WFCORE-1020) NPE in GlobalAddressHandlers
by Brian Stansberry (JIRA)
Brian Stansberry created WFCORE-1020:
----------------------------------------
Summary: NPE in GlobalAddressHandlers
Key: WFCORE-1020
URL: https://issues.jboss.org/browse/WFCORE-1020
Project: WildFly Core
Issue Type: Bug
Components: Domain Management
Affects Versions: 2.0.0.CR5, 1.0.1.Final, 1.0.0.Final
Reporter: Brian Stansberry
Assignee: Brian Stansberry
Fix For: 2.0.0.CR6
I've seen stack traces like the following pop up in testsuite logs:
{code}
2015-09-29 08:11:50,515 ERROR [org.jboss.as.controller.management-operation] (Host Controller Service Threads - 88) WFLYCTL0190: Step handler org.jboss.as.controller.operations.global.GlobalOperationHandlers$ModelAddressResolver$4@b4ea88 for operation {"operation" => "read-resource","address" => [("host" => "slave"),("server" => "main-three")],"operation-headers" => {"caller-type" => "user","access-mechanism" => "NATIVE","domain-uuid" => "5352863e-b467-4d70-b0b1-fa640cc022a1"}} at address [
("host" => "slave"),
("server" => "main-three")
] failed handling operation rollback -- java.lang.NullPointerException: java.lang.NullPointerException
at org.jboss.as.controller.operations.global.GlobalOperationHandlers$ModelAddressResolver$4$1.handleResult(GlobalOperationHandlers.java:708)
at org.jboss.as.controller.AbstractOperationContext$Step.invokeResultHandler(AbstractOperationContext.java:1384)
at org.jboss.as.controller.AbstractOperationContext$Step.handleResult(AbstractOperationContext.java:1366)
at org.jboss.as.controller.AbstractOperationContext$Step.finalizeInternal(AbstractOperationContext.java:1328)
at org.jboss.as.controller.AbstractOperationContext$Step.finalizeStep(AbstractOperationContext.java:1311)
at org.jboss.as.controller.AbstractOperationContext$Step.access$300(AbstractOperationContext.java:1185)
at org.jboss.as.controller.AbstractOperationContext.executeResultHandlerPhase(AbstractOperationContext.java:767)
at org.jboss.as.controller.AbstractOperationContext.executeDoneStage(AbstractOperationContext.java:753)
at org.jboss.as.controller.AbstractOperationContext.processStages(AbstractOperationContext.java:680)
at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:370)
at org.jboss.as.controller.OperationContextImpl.executeOperation(OperationContextImpl.java:1336)
at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:391)
at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:217)
at org.jboss.as.controller.remote.TransactionalProtocolOperationHandler.internalExecute(TransactionalProtocolOperationHandler.java:233)
at org.jboss.as.controller.remote.TransactionalProtocolOperationHandler$ExecuteRequestHandler.doExecute(TransactionalProtocolOperationHandler.java:173)
at org.jboss.as.controller.remote.TransactionalProtocolOperationHandler$ExecuteRequestHandler$1.run(TransactionalProtocolOperationHandler.java:136)
at org.jboss.as.controller.remote.TransactionalProtocolOperationHandler$ExecuteRequestHandler$1.run(TransactionalProtocolOperationHandler.java:132)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAs(Subject.java:360)
at org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:81)
at org.jboss.as.controller.remote.TransactionalProtocolOperationHandler$ExecuteRequestHandler$2$1.run(TransactionalProtocolOperationHandler.java:152)
at org.jboss.as.controller.remote.TransactionalProtocolOperationHandler$ExecuteRequestHandler$2$1.run(TransactionalProtocolOperationHandler.java:148)
at java.security.AccessController.doPrivileged(Native Method)
at org.jboss.as.controller.remote.TransactionalProtocolOperationHandler$ExecuteRequestHandler$2.execute(TransactionalProtocolOperationHandler.java:148)
at org.jboss.as.protocol.mgmt.AbstractMessageHandler$2$1.doExecute(AbstractMessageHandler.java:299)
at org.jboss.as.protocol.mgmt.AbstractMessageHandler$AsyncTaskRunner.run(AbstractMessageHandler.java:519)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
at org.jboss.threads.JBossThread.run(JBossThread.java:320)
{code}
There's a call to ModelNode.remove("access-control") and then the return value is dereferenced without a null check. The "remove" method may return null.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 9 months
[JBoss JIRA] (WFCORE-832) Access control exceptions missing for non-existent resources
by Kabir Khan (JIRA)
[ https://issues.jboss.org/browse/WFCORE-832?page=com.atlassian.jira.plugin... ]
Kabir Khan commented on WFCORE-832:
-----------------------------------
They are each listed when there are several deployments. The following sequence of CLI commands starts with no deployments:
{code}
[domain@localhost:9990 /] /server-group=*/deployment=*:read-resource-description(access-control=trim-descriptions,operations=true){roles=[main-maintainer,other-monitor]}
{
"outcome" => "success",
"result" => [{
"address" => [
("server-group" => "*"),
("deployment" => "*")
],
"outcome" => "success",
"result" => {
"description" => undefined,
"access-constraints" => {"application" => {"deployment" => {"type" => "core"}}},
"attributes" => undefined,
"operations" => undefined,
"notifications" => undefined,
"children" => {},
"access-control" => {
"default" => {
"read" => true,
"write" => false,
"attributes" => {
"enabled" => {
"read" => true,
"write" => false
},
"name" => {
"read" => true,
"write" => false
},
"runtime-name" => {
"read" => true,
"write" => false
}
},
"operations" => {
"read-children-types" => {"execute" => true},
"whoami" => {"execute" => true},
"map-clear" => {"execute" => false},
"list-get" => {"execute" => true},
"write-attribute" => {"execute" => false},
"remove" => {"execute" => false},
"deploy" => {"execute" => false},
"list-add" => {"execute" => false},
"map-put" => {"execute" => false},
"read-attribute-group-names" => {"execute" => true},
"redeploy" => {"execute" => false},
"read-resource-description" => {"execute" => true},
"read-resource" => {"execute" => true},
"add" => {"execute" => false},
"query" => {"execute" => true},
"read-operation-description" => {"execute" => true},
"map-get" => {"execute" => true},
"list-clear" => {"execute" => false},
"read-attribute" => {"execute" => true},
"map-remove" => {"execute" => false},
"read-attribute-group" => {"execute" => true},
"undefine-attribute" => {"execute" => false},
"read-children-names" => {"execute" => true},
"read-operation-names" => {"execute" => true},
"list-remove" => {"execute" => false},
"read-children-resources" => {"execute" => true},
"undeploy" => {"execute" => false}
}
},
"exceptions" => {"[(\"server-group\" => \"main-server-group\"),(\"deployment\" => \"*\")]" => {
"read" => true,
"write" => true,
"attributes" => {
"enabled" => {
"read" => true,
"write" => true
},
"name" => {
"read" => true,
"write" => true
},
"runtime-name" => {
"read" => true,
"write" => true
}
},
"operations" => {
"read-children-types" => {"execute" => true},
"whoami" => {"execute" => true},
"map-clear" => {"execute" => true},
"list-get" => {"execute" => true},
"write-attribute" => {"execute" => true},
"remove" => {"execute" => true},
"deploy" => {"execute" => true},
"list-add" => {"execute" => true},
"map-put" => {"execute" => true},
"read-attribute-group-names" => {"execute" => true},
"redeploy" => {"execute" => true},
"read-resource-description" => {"execute" => true},
"read-resource" => {"execute" => true},
"add" => {"execute" => true},
"query" => {"execute" => true},
"read-operation-description" => {"execute" => true},
"map-get" => {"execute" => true},
"list-clear" => {"execute" => true},
"read-attribute" => {"execute" => true},
"map-remove" => {"execute" => true},
"read-attribute-group" => {"execute" => true},
"undefine-attribute" => {"execute" => true},
"read-children-names" => {"execute" => true},
"read-operation-names" => {"execute" => true},
"list-remove" => {"execute" => true},
"read-children-resources" => {"execute" => true},
"undeploy" => {"execute" => true}
},
"address" => [
("server-group" => "main-server-group"),
("deployment" => "*")
]
}}
}
}
}]
}
[domain@localhost:9990 /] deploy ~/temp/Calendar.war
One of --disabled, --all-server-groups or --server-groups is missing.
[domain@localhost:9990 /] deploy ~/temp/Calendar.war --all-server-groups
[domain@localhost:9990 /] /server-group=*/deployment=*:read-resource-description(access-control=trim-descriptions,operations=true){roles=[main-maintainer,other-monitor]}
{
"outcome" => "success",
"result" => [{
"address" => [
("server-group" => "*"),
("deployment" => "*")
],
"outcome" => "success",
"result" => {
"description" => undefined,
"access-constraints" => {"application" => {"deployment" => {"type" => "core"}}},
"attributes" => undefined,
"operations" => undefined,
"notifications" => undefined,
"children" => {},
"access-control" => {
"default" => {
"read" => true,
"write" => false,
"attributes" => {
"enabled" => {
"read" => true,
"write" => false
},
"name" => {
"read" => true,
"write" => false
},
"runtime-name" => {
"read" => true,
"write" => false
}
},
"operations" => {
"read-children-types" => {"execute" => true},
"whoami" => {"execute" => true},
"map-clear" => {"execute" => false},
"list-get" => {"execute" => true},
"write-attribute" => {"execute" => false},
"remove" => {"execute" => false},
"deploy" => {"execute" => false},
"list-add" => {"execute" => false},
"map-put" => {"execute" => false},
"read-attribute-group-names" => {"execute" => true},
"redeploy" => {"execute" => false},
"read-resource-description" => {"execute" => true},
"read-resource" => {"execute" => true},
"add" => {"execute" => false},
"query" => {"execute" => true},
"read-operation-description" => {"execute" => true},
"map-get" => {"execute" => true},
"list-clear" => {"execute" => false},
"read-attribute" => {"execute" => true},
"map-remove" => {"execute" => false},
"read-attribute-group" => {"execute" => true},
"undefine-attribute" => {"execute" => false},
"read-children-names" => {"execute" => true},
"read-operation-names" => {"execute" => true},
"list-remove" => {"execute" => false},
"read-children-resources" => {"execute" => true},
"undeploy" => {"execute" => false}
}
},
"exceptions" => {"[(\"server-group\" => \"main-server-group\"),(\"deployment\" => \"Calendar.war\")]" => {
"read" => true,
"write" => true,
"attributes" => {
"enabled" => {
"read" => true,
"write" => true
},
"name" => {
"read" => true,
"write" => true
},
"runtime-name" => {
"read" => true,
"write" => true
}
},
"operations" => {
"read-children-types" => {"execute" => true},
"whoami" => {"execute" => true},
"map-clear" => {"execute" => true},
"list-get" => {"execute" => true},
"write-attribute" => {"execute" => true},
"remove" => {"execute" => true},
"deploy" => {"execute" => true},
"list-add" => {"execute" => true},
"map-put" => {"execute" => true},
"read-attribute-group-names" => {"execute" => true},
"redeploy" => {"execute" => true},
"read-resource-description" => {"execute" => true},
"read-resource" => {"execute" => true},
"add" => {"execute" => true},
"query" => {"execute" => true},
"read-operation-description" => {"execute" => true},
"map-get" => {"execute" => true},
"list-clear" => {"execute" => true},
"read-attribute" => {"execute" => true},
"map-remove" => {"execute" => true},
"read-attribute-group" => {"execute" => true},
"undefine-attribute" => {"execute" => true},
"read-children-names" => {"execute" => true},
"read-operation-names" => {"execute" => true},
"list-remove" => {"execute" => true},
"read-children-resources" => {"execute" => true},
"undeploy" => {"execute" => true}
},
"address" => [
("server-group" => "main-server-group"),
("deployment" => "Calendar.war")
]
}}
}
}
}]
}
[domain@localhost:9990 /] deploy ~/temp/Calendar2.war --all-server-groups
[domain@localhost:9990 /] /server-group=*/deployment=*:read-resource-description(access-control=trim-descriptions,operations=true){roles=[main-maintainer,other-monitor]}
{
"outcome" => "success",
"result" => [{
"address" => [
("server-group" => "*"),
("deployment" => "*")
],
"outcome" => "success",
"result" => {
"description" => undefined,
"access-constraints" => {"application" => {"deployment" => {"type" => "core"}}},
"attributes" => undefined,
"operations" => undefined,
"notifications" => undefined,
"children" => {},
"access-control" => {
"default" => {
"read" => true,
"write" => false,
"attributes" => {
"enabled" => {
"read" => true,
"write" => false
},
"name" => {
"read" => true,
"write" => false
},
"runtime-name" => {
"read" => true,
"write" => false
}
},
"operations" => {
"read-children-types" => {"execute" => true},
"whoami" => {"execute" => true},
"map-clear" => {"execute" => false},
"list-get" => {"execute" => true},
"write-attribute" => {"execute" => false},
"remove" => {"execute" => false},
"deploy" => {"execute" => false},
"list-add" => {"execute" => false},
"map-put" => {"execute" => false},
"read-attribute-group-names" => {"execute" => true},
"redeploy" => {"execute" => false},
"read-resource-description" => {"execute" => true},
"read-resource" => {"execute" => true},
"add" => {"execute" => false},
"query" => {"execute" => true},
"read-operation-description" => {"execute" => true},
"map-get" => {"execute" => true},
"list-clear" => {"execute" => false},
"read-attribute" => {"execute" => true},
"map-remove" => {"execute" => false},
"read-attribute-group" => {"execute" => true},
"undefine-attribute" => {"execute" => false},
"read-children-names" => {"execute" => true},
"read-operation-names" => {"execute" => true},
"list-remove" => {"execute" => false},
"read-children-resources" => {"execute" => true},
"undeploy" => {"execute" => false}
}
},
"exceptions" => {
"[(\"server-group\" => \"main-server-group\"),(\"deployment\" => \"Calendar2.war\")]" => {
"read" => true,
"write" => true,
"attributes" => {
"enabled" => {
"read" => true,
"write" => true
},
"name" => {
"read" => true,
"write" => true
},
"runtime-name" => {
"read" => true,
"write" => true
}
},
"operations" => {
"read-children-types" => {"execute" => true},
"whoami" => {"execute" => true},
"map-clear" => {"execute" => true},
"list-get" => {"execute" => true},
"write-attribute" => {"execute" => true},
"remove" => {"execute" => true},
"deploy" => {"execute" => true},
"list-add" => {"execute" => true},
"map-put" => {"execute" => true},
"read-attribute-group-names" => {"execute" => true},
"redeploy" => {"execute" => true},
"read-resource-description" => {"execute" => true},
"read-resource" => {"execute" => true},
"add" => {"execute" => true},
"query" => {"execute" => true},
"read-operation-description" => {"execute" => true},
"map-get" => {"execute" => true},
"list-clear" => {"execute" => true},
"read-attribute" => {"execute" => true},
"map-remove" => {"execute" => true},
"read-attribute-group" => {"execute" => true},
"undefine-attribute" => {"execute" => true},
"read-children-names" => {"execute" => true},
"read-operation-names" => {"execute" => true},
"list-remove" => {"execute" => true},
"read-children-resources" => {"execute" => true},
"undeploy" => {"execute" => true}
},
"address" => [
("server-group" => "main-server-group"),
("deployment" => "Calendar2.war")
]
},
"[(\"server-group\" => \"main-server-group\"),(\"deployment\" => \"Calendar.war\")]" => {
"read" => true,
"write" => true,
"attributes" => {
"enabled" => {
"read" => true,
"write" => true
},
"name" => {
"read" => true,
"write" => true
},
"runtime-name" => {
"read" => true,
"write" => true
}
},
"operations" => {
"read-children-types" => {"execute" => true},
"whoami" => {"execute" => true},
"map-clear" => {"execute" => true},
"list-get" => {"execute" => true},
"write-attribute" => {"execute" => true},
"remove" => {"execute" => true},
"deploy" => {"execute" => true},
"list-add" => {"execute" => true},
"map-put" => {"execute" => true},
"read-attribute-group-names" => {"execute" => true},
"redeploy" => {"execute" => true},
"read-resource-description" => {"execute" => true},
"read-resource" => {"execute" => true},
"add" => {"execute" => true},
"query" => {"execute" => true},
"read-operation-description" => {"execute" => true},
"map-get" => {"execute" => true},
"list-clear" => {"execute" => true},
"read-attribute" => {"execute" => true},
"map-remove" => {"execute" => true},
"read-attribute-group" => {"execute" => true},
"undefine-attribute" => {"execute" => true},
"read-children-names" => {"execute" => true},
"read-operation-names" => {"execute" => true},
"list-remove" => {"execute" => true},
"read-children-resources" => {"execute" => true},
"undeploy" => {"execute" => true}
},
"address" => [
("server-group" => "main-server-group"),
("deployment" => "Calendar.war")
]
}
}
}
}
}]
}
[domain@localhost:9990 /]
{code}
The following is a bit half-digested.... While I see what you are saying regarding folding Calendar.war and Calendar2.war together into deployment=x, I am also not sure if that is feasible when there are actual children. The main worry is if we have say 4 deployments, if three of them have the same exception and the fourth not, do we roll 3 of them together as deployment=x, and the last as deployment=unique? Also this could affect other things in other places? At the same time, it seems that things under server-group are slightly special due to the server scoped roles.
> Access control exceptions missing for non-existent resources
> ------------------------------------------------------------
>
> Key: WFCORE-832
> URL: https://issues.jboss.org/browse/WFCORE-832
> Project: WildFly Core
> Issue Type: Bug
> Components: Domain Management
> Reporter: Harald Pehl
> Assignee: Kabir Khan
>
> When asking for the access control metadata using (r-r-d) on *existing* resources I get an exceptions block:
> {code}
> /server-group=*:read-resource-description(access-control=trim-descriptions,operations=true){roles=[main-maintainer,other-monitor]}
> {
> "outcome" => "success",
> "result" => [{
> "address" => [("server-group" => "*")],
> "outcome" => "success",
> "result" => {
> "description" => undefined,
> "attributes" => undefined,
> "operations" => undefined,
> "notifications" => undefined,
> "children" => {
> "deployment" => {"model-description" => undefined},
> "jvm" => {"model-description" => undefined},
> "deployment-overlay" => {"model-description" => undefined},
> "system-property" => {"model-description" => undefined}
> },
> "access-control" => {
> "default" => {
> "read" => true,
> "write" => false,
> "attributes" => {
> "management-subsystem-endpoint" => {
> "read" => true,
> "write" => false
> },
> "profile" => {
> "read" => true,
> "write" => false
> },
> "socket-binding-default-interface" => {
> "read" => true,
> "write" => false
> },
> "socket-binding-group" => {
> "read" => true,
> "write" => false
> },
> "socket-binding-port-offset" => {
> "read" => true,
> "write" => false
> }
> },
> "operations" => {
> "read-children-types" => {"execute" => true},
> "whoami" => {"execute" => true},
> "map-clear" => {"execute" => false},
> "list-get" => {"execute" => true},
> "write-attribute" => {"execute" => false},
> "replace-deployment" => {"execute" => false},
> "stop-servers" => {"execute" => false},
> "remove" => {"execute" => false},
> "list-add" => {"execute" => false},
> "map-put" => {"execute" => false},
> "read-attribute-group-names" => {"execute" => true},
> "restart-servers" => {"execute" => false},
> "resume-servers" => {"execute" => false},
> "read-resource-description" => {"execute" => true},
> "read-resource" => {"execute" => true},
> "add" => {"execute" => false},
> "suspend-servers" => {"execute" => false},
> "reload-servers" => {"execute" => false},
> "query" => {"execute" => true},
> "read-operation-description" => {"execute" => true},
> "map-get" => {"execute" => true},
> "list-clear" => {"execute" => false},
> "read-attribute" => {"execute" => true},
> "map-remove" => {"execute" => false},
> "read-attribute-group" => {"execute" => true},
> "undefine-attribute" => {"execute" => false},
> "read-children-names" => {"execute" => true},
> "start-servers" => {"execute" => false},
> "read-operation-names" => {"execute" => true},
> "list-remove" => {"execute" => false},
> "read-children-resources" => {"execute" => true}
> }
> },
> "exceptions" => {"[(\"server-group\" => \"main-server-group\")]" => {
> "read" => true,
> "write" => true,
> "attributes" => {
> "management-subsystem-endpoint" => {
> "read" => true,
> "write" => false
> },
> "profile" => {
> "read" => true,
> "write" => true
> },
> "socket-binding-default-interface" => {
> "read" => true,
> "write" => false
> },
> "socket-binding-group" => {
> "read" => true,
> "write" => true
> },
> "socket-binding-port-offset" => {
> "read" => true,
> "write" => false
> }
> },
> "operations" => {
> "read-children-types" => {"execute" => true},
> "whoami" => {"execute" => true},
> "map-clear" => {"execute" => true},
> "list-get" => {"execute" => true},
> "write-attribute" => {"execute" => true},
> "replace-deployment" => {"execute" => true},
> "stop-servers" => {"execute" => true},
> "remove" => {"execute" => false},
> "list-add" => {"execute" => true},
> "map-put" => {"execute" => true},
> "read-attribute-group-names" => {"execute" => true},
> "restart-servers" => {"execute" => true},
> "resume-servers" => {"execute" => true},
> "read-resource-description" => {"execute" => true},
> "read-resource" => {"execute" => true},
> "add" => {"execute" => false},
> "suspend-servers" => {"execute" => true},
> "reload-servers" => {"execute" => true},
> "query" => {"execute" => true},
> "read-operation-description" => {"execute" => true},
> "map-get" => {"execute" => true},
> "list-clear" => {"execute" => true},
> "read-attribute" => {"execute" => true},
> "map-remove" => {"execute" => true},
> "read-attribute-group" => {"execute" => true},
> "undefine-attribute" => {"execute" => true},
> "read-children-names" => {"execute" => true},
> "start-servers" => {"execute" => true},
> "read-operation-names" => {"execute" => true},
> "list-remove" => {"execute" => true},
> "read-children-resources" => {"execute" => true}
> },
> "address" => [("server-group" => "main-server-group")]
> }}
> }
> }
> }]
> }
> {code}
> However when using the same operation on *non-existng* resources I don't see an exception block:
> {code}
> /server-group=*/deployment=*:read-resource-description(access-control=trim-descriptions,operations=true){roles=[main-maintainer,other-monitor]}
> {
> "outcome" => "success",
> "result" => [{
> "address" => [
> ("server-group" => "*"),
> ("deployment" => "*")
> ],
> "outcome" => "success",
> "result" => {
> "description" => undefined,
> "access-constraints" => {"application" => {"deployment" => {"type" => "core"}}},
> "attributes" => undefined,
> "operations" => undefined,
> "notifications" => undefined,
> "children" => {},
> "access-control" => {
> "default" => {
> "read" => true,
> "write" => false,
> "attributes" => {
> "enabled" => {
> "read" => true,
> "write" => false
> },
> "name" => {
> "read" => true,
> "write" => false
> },
> "runtime-name" => {
> "read" => true,
> "write" => false
> }
> },
> "operations" => {
> "read-children-types" => {"execute" => true},
> "whoami" => {"execute" => true},
> "map-clear" => {"execute" => false},
> "list-get" => {"execute" => true},
> "write-attribute" => {"execute" => false},
> "remove" => {"execute" => false},
> "deploy" => {"execute" => false},
> "list-add" => {"execute" => false},
> "map-put" => {"execute" => false},
> "read-attribute-group-names" => {"execute" => true},
> "redeploy" => {"execute" => false},
> "read-resource-description" => {"execute" => true},
> "read-resource" => {"execute" => true},
> "add" => {"execute" => false},
> "query" => {"execute" => true},
> "read-operation-description" => {"execute" => true},
> "map-get" => {"execute" => true},
> "list-clear" => {"execute" => false},
> "read-attribute" => {"execute" => true},
> "map-remove" => {"execute" => false},
> "read-attribute-group" => {"execute" => true},
> "undefine-attribute" => {"execute" => false},
> "read-children-names" => {"execute" => true},
> "read-operation-names" => {"execute" => true},
> "list-remove" => {"execute" => false},
> "read-children-resources" => {"execute" => true},
> "undeploy" => {"execute" => false}
> }
> },
> "exceptions" => {}
> }
> }
> }]
> }
> {code}
> Some notes on the domain:
> - Built from WildFly 10 master
> - No deployments present
> - Role {{main-maintainer}} is a server group scoped role based on Maintainer and scoped to main-server-group
> - Role {{other-monitor}} is a server group scoped role based on Monitor and scoped to other-server-group
> What we would need is a way to *always* get the exceptions no matter whether the resource exists. In the console we create a so-called security context which uses wildcard r-r-d operations like the ones above. This security context is used later on to show / hide UI controls.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 9 months
[JBoss JIRA] (WFLY-5340) Unable to specify module when specifying custom JACC policy class.
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/WFLY-5340?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration updated WFLY-5340:
------------------------------------------
Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1263336, https://bugzilla.redhat.com/show_bug.cgi?id=1267355 (was: https://bugzilla.redhat.com/show_bug.cgi?id=1263336)
> Unable to specify module when specifying custom JACC policy class.
> ------------------------------------------------------------------
>
> Key: WFLY-5340
> URL: https://issues.jboss.org/browse/WFLY-5340
> Project: WildFly
> Issue Type: Bug
> Components: Security
> Affects Versions: 10.0.0.Beta2
> Reporter: Darran Lofthouse
> Assignee: Darran Lofthouse
> Fix For: 10.0.0.CR1
>
>
> It is currently possible to specify the 'javax.security.jacc.policy.provider' system property, however it is not possible to specify a module.
> From the JACC specification: -
> _For each JRE of a J2EE 1.4 or later version Java EE application server, if the
> system property
> “javax.security.jacc.policy.provider
> ” is defined,
> the application server must construct an
> instance of the class identified by the
> system property, confirm that the
> resulting object is an instance of
> java.security.Policy,
> and set, by calling the
> java.security.Policy.setPolicy
> method, the resulting object as the
> corresponding Policy object u
> sed by the JRE. _
> The specification only specifies that the system property identifies the class, it does not specify how.
> In it's simplest form we should assume this is just a class name, in a more complex form we should allow the module to be specified.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 9 months
[JBoss JIRA] (WFLY-4465) Update PicketLink Capabilities
by Pedro Igor (JIRA)
[ https://issues.jboss.org/browse/WFLY-4465?page=com.atlassian.jira.plugin.... ]
Pedro Igor updated WFLY-4465:
-----------------------------
Description: Update PicketLink modules and subsystem in order to support currently capabilities provided in EAP 6 / JBossWeb. (was: Update PicketLink modules in order to support currently capabilities provided in EAP 6 / JBossWeb.)
> Update PicketLink Capabilities
> ------------------------------
>
> Key: WFLY-4465
> URL: https://issues.jboss.org/browse/WFLY-4465
> Project: WildFly
> Issue Type: Enhancement
> Components: Security
> Affects Versions: 10.0.0.CR2
> Reporter: Pedro Igor
> Assignee: Pedro Igor
>
> Update PicketLink modules and subsystem in order to support currently capabilities provided in EAP 6 / JBossWeb.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 9 months
[JBoss JIRA] (WFLY-5426) Data sources other than h2 cannot be added to domain servers
by James Perkins (JIRA)
[ https://issues.jboss.org/browse/WFLY-5426?page=com.atlassian.jira.plugin.... ]
James Perkins updated WFLY-5426:
--------------------------------
Priority: Blocker (was: Critical)
> Data sources other than h2 cannot be added to domain servers
> ------------------------------------------------------------
>
> Key: WFLY-5426
> URL: https://issues.jboss.org/browse/WFLY-5426
> Project: WildFly
> Issue Type: Bug
> Components: JCA
> Affects Versions: 9.0.0.Final
> Reporter: James Perkins
> Assignee: Stefano Maestri
> Priority: Blocker
> Fix For: 10.0.0.Final
>
>
> This seems to work okay with the h2 driver, but adding a postgres driver add operations fail.
> The driver is deployed and is on the {{main-server-group}} which defaults to the {{full}} profile.
> {code}
> [domain@localhost:9990 /] /server-group=main-server-group:read-children-resources(child-type=deployment,recursive=true,include-runtime=true)
> {
> "outcome" => "success",
> "result" => {"postgresql-9.4-1201.jdbc41.jar" => {
> "enabled" => true,
> "name" => "postgresql-9.4-1201.jdbc41.jar",
> "runtime-name" => "postgresql-9.4-1201.jdbc41.jar"
> }}
> }
> {code}
> Attempting to add the data source results in the following error:
> {code}
> [domain@localhost:9990 /] /profile=full/subsystem=datasources/data-source=test-pg:add(driver-name=postgresql-9.4-1201.jdbc41.jar, connection-url=jdbc:postgresql://localhost:test,user-name=user,password=password, jndi-name=java:jboss/datasources/test-pg)
> {
> "outcome" => "failed",
> "result" => undefined,
> "failure-description" => {"WFLYDC0074: Operation failed or was rolled back on all servers. Server failures:" => {"server-group" => {"main-server-group" => {"host" => {"master" => {
> "server-one" => {"WFLYCTL0080: Failed services" => {"jboss.data-source.java:jboss/datasources/test-pg" => "org.jboss.msc.service.StartException in service jboss.data-source.java:jboss/datasources/test-pg: WFLYJCA0033: Error during the deployment of test-pg
> Caused by: org.jboss.msc.service.StartException in anonymous service: WFLYJCA0032: Unable to start the ds because it generated more than one cf"}},
> "server-two" => {"WFLYCTL0080: Failed services" => {"jboss.data-source.java:jboss/datasources/test-pg" => "org.jboss.msc.service.StartException in service jboss.data-source.java:jboss/datasources/test-pg: WFLYJCA0033: Error during the deployment of test-pg
> Caused by: org.jboss.msc.service.StartException in anonymous service: WFLYJCA0032: Unable to start the ds because it generated more than one cf"}}
> }}}}}},
> "rolled-back" => true,
> "server-groups" => {"main-server-group" => {"host" => {"master" => {
> "server-one" => {"response" => {
> "outcome" => "failed",
> "failure-description" => {"WFLYCTL0080: Failed services" => {"jboss.data-source.java:jboss/datasources/test-pg" => "org.jboss.msc.service.StartException in service jboss.data-source.java:jboss/datasources/test-pg: WFLYJCA0033: Error during the deployment of test-pg
> Caused by: org.jboss.msc.service.StartException in anonymous service: WFLYJCA0032: Unable to start the ds because it generated more than one cf"}},
> "rolled-back" => true
> }},
> "server-two" => {"response" => {
> "outcome" => "failed",
> "failure-description" => {"WFLYCTL0080: Failed services" => {"jboss.data-source.java:jboss/datasources/test-pg" => "org.jboss.msc.service.StartException in service jboss.data-source.java:jboss/datasources/test-pg: WFLYJCA0033: Error during the deployment of test-pg
> Caused by: org.jboss.msc.service.StartException in anonymous service: WFLYJCA0032: Unable to start the ds because it generated more than one cf"}},
> "rolled-back" => true
> }}
> }}}}
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 9 months
[JBoss JIRA] (WFLY-5426) Data sources other than h2 cannot be added to domain servers
by James Perkins (JIRA)
James Perkins created WFLY-5426:
-----------------------------------
Summary: Data sources other than h2 cannot be added to domain servers
Key: WFLY-5426
URL: https://issues.jboss.org/browse/WFLY-5426
Project: WildFly
Issue Type: Bug
Components: JCA
Affects Versions: 9.0.0.Final
Reporter: James Perkins
Assignee: Stefano Maestri
Priority: Critical
Fix For: 10.0.0.Final
This seems to work okay with the h2 driver, but adding a postgres driver add operations fail.
The driver is deployed and is on the {{main-server-group}} which defaults to the {{full}} profile.
{code}
[domain@localhost:9990 /] /server-group=main-server-group:read-children-resources(child-type=deployment,recursive=true,include-runtime=true)
{
"outcome" => "success",
"result" => {"postgresql-9.4-1201.jdbc41.jar" => {
"enabled" => true,
"name" => "postgresql-9.4-1201.jdbc41.jar",
"runtime-name" => "postgresql-9.4-1201.jdbc41.jar"
}}
}
{code}
Attempting to add the data source results in the following error:
{code}
[domain@localhost:9990 /] /profile=full/subsystem=datasources/data-source=test-pg:add(driver-name=postgresql-9.4-1201.jdbc41.jar, connection-url=jdbc:postgresql://localhost:test,user-name=user,password=password, jndi-name=java:jboss/datasources/test-pg)
{
"outcome" => "failed",
"result" => undefined,
"failure-description" => {"WFLYDC0074: Operation failed or was rolled back on all servers. Server failures:" => {"server-group" => {"main-server-group" => {"host" => {"master" => {
"server-one" => {"WFLYCTL0080: Failed services" => {"jboss.data-source.java:jboss/datasources/test-pg" => "org.jboss.msc.service.StartException in service jboss.data-source.java:jboss/datasources/test-pg: WFLYJCA0033: Error during the deployment of test-pg
Caused by: org.jboss.msc.service.StartException in anonymous service: WFLYJCA0032: Unable to start the ds because it generated more than one cf"}},
"server-two" => {"WFLYCTL0080: Failed services" => {"jboss.data-source.java:jboss/datasources/test-pg" => "org.jboss.msc.service.StartException in service jboss.data-source.java:jboss/datasources/test-pg: WFLYJCA0033: Error during the deployment of test-pg
Caused by: org.jboss.msc.service.StartException in anonymous service: WFLYJCA0032: Unable to start the ds because it generated more than one cf"}}
}}}}}},
"rolled-back" => true,
"server-groups" => {"main-server-group" => {"host" => {"master" => {
"server-one" => {"response" => {
"outcome" => "failed",
"failure-description" => {"WFLYCTL0080: Failed services" => {"jboss.data-source.java:jboss/datasources/test-pg" => "org.jboss.msc.service.StartException in service jboss.data-source.java:jboss/datasources/test-pg: WFLYJCA0033: Error during the deployment of test-pg
Caused by: org.jboss.msc.service.StartException in anonymous service: WFLYJCA0032: Unable to start the ds because it generated more than one cf"}},
"rolled-back" => true
}},
"server-two" => {"response" => {
"outcome" => "failed",
"failure-description" => {"WFLYCTL0080: Failed services" => {"jboss.data-source.java:jboss/datasources/test-pg" => "org.jboss.msc.service.StartException in service jboss.data-source.java:jboss/datasources/test-pg: WFLYJCA0033: Error during the deployment of test-pg
Caused by: org.jboss.msc.service.StartException in anonymous service: WFLYJCA0032: Unable to start the ds because it generated more than one cf"}},
"rolled-back" => true
}}
}}}}
}
{code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 9 months
[JBoss JIRA] (WFCORE-1019) History browsing in CLI (using the up arrow) works strangely
by Alexey Loubyansky (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1019?page=com.atlassian.jira.plugi... ]
Alexey Loubyansky updated WFCORE-1019:
--------------------------------------
Issue Type: Enhancement (was: Bug)
> History browsing in CLI (using the up arrow) works strangely
> ------------------------------------------------------------
>
> Key: WFCORE-1019
> URL: https://issues.jboss.org/browse/WFCORE-1019
> Project: WildFly Core
> Issue Type: Enhancement
> Components: CLI
> Affects Versions: 2.0.0.CR1, 2.0.0.CR5
> Reporter: Ladislav Thon
> Assignee: Alexey Loubyansky
>
> I tend to rely on history browsing in the CLI a lot, but it got broken in WildFly 10.0.0.CR1 / WildFly Core 2.0.0.CR1 (I'd guess that the cause is the AESH upgrade). Let's see:
> {code}
> rm ~/.jboss-cli-history # let's start with clean slate
> ./wildfly-10.0.0.Beta2/bin/standalone.sh
> # the following is in second console
> ./wildfly-10.0.0.Beta2/bin/jboss-cli.sh -c
> :read-resource
> :whoami
> [up arrow shows :whoami, so press Enter to run it]
> [and repeat, up arrow shows :whoami]
> {code}
> OK, that's expected. Repeat the process with WildFly 10.0.0.CR1 or CR2 and you'll find out that the second \[up arrow\] shows {{:read-resource}}. This is IMHO highly wrong and it confused me _a lot_ when I first encoutered this bad behavior.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 9 months
[JBoss JIRA] (WFCORE-1001) Starting embedded server overwrites standalone/config/logging.properties with a mostly blank config
by Ken Wills (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1001?page=com.atlassian.jira.plugi... ]
Ken Wills closed WFCORE-1001.
-----------------------------
Resolution: Done
> Starting embedded server overwrites standalone/config/logging.properties with a mostly blank config
> ---------------------------------------------------------------------------------------------------
>
> Key: WFCORE-1001
> URL: https://issues.jboss.org/browse/WFCORE-1001
> Project: WildFly Core
> Issue Type: Bug
> Reporter: Ken Wills
> Assignee: Ken Wills
> Fix For: 2.0.0.CR6
>
>
> Note the contents of build/target/wildfly-core-2.0.0.CR4-SNAPSHOT/standalone/configuration/logging.properties
> $ ./build/target/wildfly-core-2.0.0.CR4-SNAPSHOT/bin/jboss-cli.sh
> You are disconnected at the moment. Type 'connect' to connect to the server or 'help' for the list of supported commands.
> [disconnected /] embed-server --std-out=echo
> Check the contents of build/target/wildfly-core-2.0.0.CR4-SNAPSHOT/standalone/configuration/logging.properties, the file is empty.
> Starting standalone will restore the default contents.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 9 months
[JBoss JIRA] (DROOLS-931) Drools 4.0.7
by Mario Fusco (JIRA)
[ https://issues.jboss.org/browse/DROOLS-931?page=com.atlassian.jira.plugin... ]
Mario Fusco closed DROOLS-931.
------------------------------
Resolution: Rejected
First of all be advised that Drools 4.x and 5.x is no longer supported. Please open another ticket if you believe there's a related issue on Drools 6.x
What you're saying is that you want determinstic behaviour on arbitrary salience. Unfortunately that is never guaranteed and it can change between JVMs and between Drools versions. With Drools 6.x we partially fixed this ambiguity because rules in the same DRL file have an implicit relative salience (if no explicit salience is given). This means that rules that appear first in the file have an higher salience than the ones that comes later. However we still don't have a similar mechanism for rules in different DRL files so in that case it can go arbitrary again.
> Drools 4.0.7
> ------------
>
> Key: DROOLS-931
> URL: https://issues.jboss.org/browse/DROOLS-931
> Project: Drools
> Issue Type: Bug
> Environment: WAS 6.1(JDK 1.5) & WAS 8.5.5(JDK 1.7)
> Reporter: raj S
> Assignee: Mario Fusco
>
> We have around 10,000+ rules running on a legacy system which is using jdk 1.5. those rules doesn't have salience set for all the rules , but have been tested to work fine with older jdk.
> Now are trying to upgrade the system to later version of JDK, rules execution order seems to be difference ,because they don't have salience set. in the process we have identified that few rules were having coding issues and corrected them.
> Issue: is there a way to grantee the same execution order between the jdk 1.5 & JDK 1.7. we haven't updated the drools version just the JDK. can you please give us some insight in to the natural order of rules execution in drools engine so we can put in a fix outside the engine to ensure the same order. any help is appreciated.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 9 months