December 2014 - jboss-jira - Jboss List Archives

[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 updated WFCORE-442: ------------------------------------ Description: 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. was: 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. > 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

1
0
0 / 0

[JBoss JIRA] (WFCORE-441) Strange address handling in ReadResourceDescriptionHandler

by Brian Stansberry (JIRA)

Brian Stansberry created WFCORE-441: --------------------------------------- Summary: Strange address handling in ReadResourceDescriptionHandler Key: WFCORE-441 URL: https://issues.jboss.org/browse/WFCORE-441 Project: WildFly Core Issue Type: Bug Components: Domain Management Reporter: Brian Stansberry Priority: Minor https://github.com/wildfly/wildfly-core/blob/master/controller/src/main/j... is suspect. AFAICT that operation variable will be from the original op that triggered the multi-part request. So its address is not the address of the bit that had the failure, but the use of that address implies the intent is that it is the bit that had the failure. Perhaps it should be resultItem.get(OP_ADDR) ? -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-439) Wrong format of IPv6 addresses in log entries

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-439?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on WFCORE-439: ------------------------------------------------ Emmanuel Hugonnet (ehsavoie) <ehugonne(a)redhat.com> changed the Status of [bug 900564|https://bugzilla.redhat.com/show_bug.cgi?id=900564] from ASSIGNED to POST > Wrong format of IPv6 addresses in log entries > --------------------------------------------- > > Key: WFCORE-439 > URL: https://issues.jboss.org/browse/WFCORE-439 > Project: WildFly Core > Issue Type: Bug > Affects Versions: 1.0.0.Alpha13 > Reporter: Emmanuel Hugonnet > Assignee: Emmanuel Hugonnet > Priority: Minor > > IPv6 addresses in log files are in a wrong format, the [ ] are missing: > {noformat} > 09:18:44,203 INFO [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http://2620:52:0:105f::ffff:2:9990 > {noformat} > It should be: > {noformat} > http://[2620:52:0:105f::ffff:2]:9990 {noformat} -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2850) AJP connector with external authentication

by Sylvain Brouillat (JIRA)

[ https://issues.jboss.org/browse/WFLY-2850?page=com.atlassian.jira.plugin.... ] Sylvain Brouillat commented on WFLY-2850: ----------------------------------------- Here are the full steps to be able to retreive the remote_user from front end server (like apache). Hope this will help someone. In my case, I don't want to use JAAS on wildfly side, and let apache take care of all the authentication. Indeed, if you just put in web.xml : <login-config> <auth-method>EXTERNAL</auth-method> </login-config> You'll get forbidden message from undertow. This is because ExternalAuthenticationMechanism use the default wildfly LoginModule that try to authenticate to default Realm. All you need to do is using the ClientLoginModule (see https://docs.jboss.org/author/display/WFLY8/Security+subsystem+configuration) specifying your own security domain. Add the following to standalone.xml to add a security domain using ClientLoginModule : <security-domain name="mySecurityDomain" cache-type="default"> <authentication> <login-module code="Client" flag="optional"> </login-module> </authentication> </security-domain> Then, tell your war file to use mySecurityDomain as security-domain adding a jboss-web.xml file to the WEB-INF/ directory. jboss-web.xml looks like : <?xml version="1.0" encoding="UTF-8"?> <jboss-web> <security-domain>mySecurityDomain</security-domain> </jboss-web> Actually, ClientLoginModule just put your principal and credential into securityContext without authenticating the user to any realm, so that HttpServletRequest impl (io.undertow.servlet.spec.HttpServletRequestImpl) can retreive the remote user from the security context when you call HttpServletRequest.getRemoteUser(). > AJP connector with external authentication > ------------------------------------------ > > Key: WFLY-2850 > URL: https://issues.jboss.org/browse/WFLY-2850 > Project: WildFly > Issue Type: Feature Request > Components: Web (Undertow) > Affects Versions: 8.0.0.CR1 > Reporter: Geert Coelmont > Assignee: Stuart Douglas > Priority: Critical > Fix For: 8.1.0.CR2, 8.1.0.Final > > > Tomcat allows to set the tomcatAuthentication attribute of the AJP connector to false to allow external web servers (e.g. apache httpd) to handle the authentication and pass that along. > A similar option was added recently to JBossWeb as well (see WFLY-254), but JBossWeb has been replaced by Undertow. With Undertow this option isn't available as far as I can see. > For me this is a critical problem as there is currently no way I can do negotiated (SPNEGO) authentication from within WildFly+Undertow. (See also WFLY-2404). -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JGRP-1899) Discovery returns after 16 responses even if there are no coord responses

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JGRP-1899?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on JGRP-1899: ----------------------------------------------- Dave Stahl <dstahl(a)redhat.com> changed the Status of [bug 1168329|https://bugzilla.redhat.com/show_bug.cgi?id=1168329] from NEW to POST > Discovery returns after 16 responses even if there are no coord responses > ------------------------------------------------------------------------- > > Key: JGRP-1899 > URL: https://issues.jboss.org/browse/JGRP-1899 > Project: JGroups > Issue Type: Bug > Reporter: Bela Ban > Assignee: Bela Ban > Fix For: 3.5.2, 3.6.1 > > > Discovery sets {{Responses.num_expected_rsps}} to 16 if no member list is defined. This makes discovery return after 16 responses even if no response from a coordinator has been received. > This is a problem if we have a cluster of size > 16 and the coordinator doesn't respond imediately, e.g. because it is busy processing other requests. > h5. Solution > * Set {{num_expected_rsps}} to 0 (= wait until at least 1 coord rsp has been received -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4146) Cache add operation should automatically create its child resources

by Paul Ferraro (JIRA)

Paul Ferraro created WFLY-4146: ---------------------------------- Summary: Cache add operation should automatically create its child resources Key: WFLY-4146 URL: https://issues.jboss.org/browse/WFLY-4146 Project: WildFly Issue Type: Enhancement Components: Clustering Affects Versions: 9.0.0.Alpha1 Reporter: Paul Ferraro Assignee: Paul Ferraro There is effectively no difference between the behavior of a cache that does not contain a given child resource (e.g. transaction, locking, etc) and one that contains the child resource, but with default attribute values. Consequently, the cache add operation should automatically create these resources (and the cache remove operation should automatically remove them). We can treat the child add operations as no-ops, and the child remove operations as a series of undefine-attribute operations. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-439) Wrong format of IPv6 addresses in log entries

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-439?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated WFCORE-439: ------------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=900564 > Wrong format of IPv6 addresses in log entries > --------------------------------------------- > > Key: WFCORE-439 > URL: https://issues.jboss.org/browse/WFCORE-439 > Project: WildFly Core > Issue Type: Bug > Affects Versions: 1.0.0.Alpha13 > Reporter: Emmanuel Hugonnet > Assignee: Emmanuel Hugonnet > Priority: Minor > > IPv6 addresses in log files are in a wrong format, the [ ] are missing: > {noformat} > 09:18:44,203 INFO [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http://2620:52:0:105f::ffff:2:9990 > {noformat} > It should be: > {noformat} > http://[2620:52:0:105f::ffff:2]:9990 {noformat} -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-360) HTTP management API section in the Admin Guide

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-360?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated WFCORE-360: ------------------------------------------- Bugzilla Update: (was: Perform) Bugzilla References: (was: https://bugzilla.redhat.com/show_bug.cgi?id=900564) > HTTP management API section in the Admin Guide > ---------------------------------------------- > > Key: WFCORE-360 > URL: https://issues.jboss.org/browse/WFCORE-360 > Project: WildFly Core > Issue Type: Task > Components: Domain Management > Reporter: Brian Stansberry > Assignee: Emmanuel Hugonnet > > We need a technical guide to the HTTP management API. > The "Management clients" section gives a basic overview. But it should reference a separate section that documents the usage of GET and POST, the URL patterns, the JSON representation of DMR etc. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-440) Upgrade JBoss AESH from 0.33.12.redhat-1 to 0.33.13.redhat-1

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-440?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated WFCORE-440: ------------------------------------------- Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1169858, https://bugzilla.redhat.com/show_bug.cgi?id=1169868 (was: https://bugzilla.redhat.com/show_bug.cgi?id=1169858) > Upgrade JBoss AESH from 0.33.12.redhat-1 to 0.33.13.redhat-1 > ------------------------------------------------------------ > > Key: WFCORE-440 > URL: https://issues.jboss.org/browse/WFCORE-440 > Project: WildFly Core > Issue Type: Component Upgrade > Components: CLI > Affects Versions: 1.0.0.Alpha13 > Reporter: Tomas Hofman > Assignee: Alexey Loubyansky > > AESH needs to be upgraded due to https://issues.jboss.org/browse/WFCORE-438 -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-438) The CLI freezes in phase of requesting username/password

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-438?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on WFCORE-438: ------------------------------------------------ Tomas Hofman <thofman(a)redhat.com> changed the Status of [bug 1169300|https://bugzilla.redhat.com/show_bug.cgi?id=1169300] from ASSIGNED to POST > The CLI freezes in phase of requesting username/password > -------------------------------------------------------- > > Key: WFCORE-438 > URL: https://issues.jboss.org/browse/WFCORE-438 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Affects Versions: 1.0.0.Alpha13 > Reporter: Tomas Hofman > Assignee: Tomas Hofman > > CLI doesn't terminate -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 7 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira December 2014