[JBoss JIRA] (WFLY-1736) CommandLineArgumentUsage class substring value discarded
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFLY-1736?page=com.atlassian.jira.plugin.... ]
Brian Stansberry updated WFLY-1736:
-----------------------------------
Fix Version/s: 8.0.0.CR1
> CommandLineArgumentUsage class substring value discarded
> --------------------------------------------------------
>
> Key: WFLY-1736
> URL: https://issues.jboss.org/browse/WFLY-1736
> Project: WildFly
> Issue Type: Bug
> Components: Domain Management
> Affects Versions: 8.0.0.Alpha4
> Reporter: Cheng Fang
> Assignee: Brian Stansberry
> Fix For: 8.0.0.CR1
>
>
> CommandLineArgumentUsage class has a substring call but return value discarded:
> {code}
> if( input.get(0).length() > width ){
> String tooLong = input.remove(0);
> tooLong.substring(0, width-5);
> input.add("Command removed. Too long.");
> }
> {code}
> FindBugs also finds a static field should be final:
> {code}
> protected static List<String> instructions = new ArrayList<String>();
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 3 months
[JBoss JIRA] (WFLY-1741) RBAC: Response headers don't match payload structure
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFLY-1741?page=com.atlassian.jira.plugin.... ]
Brian Stansberry commented on WFLY-1741:
----------------------------------------
I don't understand. It's looks fine to me. What do you think it should look like?
> RBAC: Response headers don't match payload structure
> ----------------------------------------------------
>
> Key: WFLY-1741
> URL: https://issues.jboss.org/browse/WFLY-1741
> Project: WildFly
> Issue Type: Bug
> Components: Domain Management
> Reporter: Heiko Braun
> Assignee: Brian Stansberry
>
> the 'relative-address' header doesn't match the response structure:
> (hint: the 'data-source' element is missing)
> {noformat}
> [standalone@localhost:9990 /] /subsystem=datasources:read-children-resources(child-type=data-source){roles=monitor}
> {
> "outcome" => "success",
> "result" => {
> "ExampleDS" => {
> "allocation-retry" => undefined,
> "allocation-retry-wait-millis" => undefined,
> [...] }
> },
> "response-headers" => {"access-control" => [ {
> "absolute-address" => [
> ("subsystem" => "datasources"),
> ("data-source" => "ExampleDS")
> ],
> "relative-address" => [("data-source" => "ExampleDS")],
> "filtered-attributes" => [
> "user-name",
> "security-domain",
> "password"
> ]
> }
> ]}
> }
> {noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 3 months
[JBoss JIRA] (WFLY-2003) Failed handling operation rollback -- null
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFLY-2003?page=com.atlassian.jira.plugin.... ]
Brian Stansberry resolved WFLY-2003.
------------------------------------
Fix Version/s: 8.0.0.Beta1
(was: 8.0.0.CR1)
Resolution: Done
I haven't seen these and the QE testing of EAP isn't finding them either, so I'm going to assume a change in Beta1 took care of this. Please reopen if you find it's still happening.
> Failed handling operation rollback -- null
> ------------------------------------------
>
> Key: WFLY-2003
> URL: https://issues.jboss.org/browse/WFLY-2003
> Project: WildFly
> Issue Type: Sub-task
> Components: Domain Management
> Reporter: Heiko Braun
> Assignee: Brian Stansberry
> Fix For: 8.0.0.Beta1
>
>
> Not sure what's causing these, but when operating the web console in domain mode I see planty of these on the console:
> {noformat}
> [Host Controller] 09:29:23,565 ERROR [org.jboss.as.controller.client] (XNIO-1 task-1) JBAS014781: Step handler org.jboss.as.domain.controller.operations.coordination.DomainFinalResultHandler@59f61bf9 for operation composite at address [] failed handling operation rollback -- null
> {noformat}
> The strange thing is that the management operations return successfully.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 3 months
[JBoss JIRA] (WFLY-2138) Cannot add security realm child resources in a domain
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFLY-2138?page=com.atlassian.jira.plugin.... ]
Brian Stansberry resolved WFLY-2138.
------------------------------------
Fix Version/s: 8.0.0.Beta1
(was: 8.0.0.CR1)
Resolution: Done
Fixed in https://github.com/wildfly/wildfly/commit/5a663d4513ff3fd1d187cf47cbbaf1d...
> Cannot add security realm child resources in a domain
> -----------------------------------------------------
>
> Key: WFLY-2138
> URL: https://issues.jboss.org/browse/WFLY-2138
> Project: WildFly
> Issue Type: Bug
> Components: Domain Management
> Reporter: Brian Stansberry
> Assignee: Brian Stansberry
> Priority: Critical
> Fix For: 8.0.0.Beta1
>
>
> /] /host=master/core-service=management/security-realm=JBossTest:add
> {
> "outcome" => "success",
> "result" => undefined,
> "server-groups" => undefined
> }
> [domain@localhost:9990 /] /host=master/core-service=management/security-realm=JBossTest/authentication=properties:add(path=application-users.properties, relative-to=jboss.server.config.dir)
> {
> "outcome" => "failed",
> "result" => undefined,
> "failure-description" => "JBAS010839: Operation failed or was rolled back on all servers.",
> "rolled-back" => true,
> "server-groups" => {"main-server-group" => {"host" => {"master" => {
> "server-one" => {"response" => {
> "outcome" => "failed",
> "failure-description" => "JBAS014883: No resource definition is registered for address [
> (\"host\" => \"master\"),
> (\"core-service\" => \"management\"),
> (\"security-realm\" => \"JBossTest\"),
> (\"authentication\" => \"properties\")
> ]",
> "rolled-back" => true
> }},
> "server-two" => {"response" => {
> "outcome" => "failed",
> "failure-description" => "JBAS014883: No resource definition is registered for address [
> (\"host\" => \"master\"),
> (\"core-service\" => \"management\"),
> (\"security-realm\" => \"JBossTest\"),
> (\"authentication\" => \"properties\")
> ]",
> "rolled-back" => true
> }}
> }}}}
> }
> Note the addresses in the server level failure messages. It appears the /host=master level is not being stripped from the request to the server.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 3 months
[JBoss JIRA] (WFLY-2254) Allow restart of management interface services via allow-resource-restart header
by Brian Stansberry (JIRA)
Brian Stansberry created WFLY-2254:
--------------------------------------
Summary: Allow restart of management interface services via allow-resource-restart header
Key: WFLY-2254
URL: https://issues.jboss.org/browse/WFLY-2254
Project: WildFly
Issue Type: Enhancement
Components: Domain Management
Reporter: Brian Stansberry
Priority: Minor
The management interface resources seem like good candidates for allow-resource-restart handling. A restart of the services should not propagate through a broad range of dependent services, while an admin could quite reasonably want to update these without taking a server outage.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 3 months
[JBoss JIRA] (WFLY-2134) Changing management http-interface with CLI doesn't work.
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFLY-2134?page=com.atlassian.jira.plugin.... ]
Brian Stansberry commented on WFLY-2134:
----------------------------------------
This is the same problem as WFLY-2194.
> Changing management http-interface with CLI doesn't work.
> ---------------------------------------------------------
>
> Key: WFLY-2134
> URL: https://issues.jboss.org/browse/WFLY-2134
> Project: WildFly
> Issue Type: Bug
> Components: Domain Management
> Affects Versions: 8.0.0.Alpha4
> Reporter: Filip Bogyai
> Assignee: Darran Lofthouse
> Fix For: 8.0.0.CR1
>
>
> When you try to change http-interface with CLI you get: Communication error: java.util.concurrent.ExecutionException: Operation failed: Operation failed: Channel closed
> On server side: JBAS014626: Operation was interrupted before stability could be reached
> For example try to add secure-socket-binding attribute:
> /core-service=management/management-interface=http-interface:write-attribute(name=secure-socket-binding, value=management-https)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 3 months