June 2015 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-3681) General Schema Sync with EAP

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-3681?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-3681: ------------------------------- Fix Version/s: 10.0.0.Alpha5 (was: 10.0.0.Alpha4) > General Schema Sync with EAP > ---------------------------- > > Key: WFLY-3681 > URL: https://issues.jboss.org/browse/WFLY-3681 > Project: WildFly > Issue Type: Sub-task > Components: Domain Management > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Critical > Fix For: 10.0.0.Alpha5 > > > This may actually be more about pushing some changes to EAP, new schemas are being tracked by individual issues but for the remaining schemas where cosmetic changes have been made or corrections to default values and min/max occurs we need to sync with EAP. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (WFLY-3573) Adding incorrect JGroups protocol should provide better error description than CNFE

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-3573?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-3573: ------------------------------- Fix Version/s: 10.0.0.Alpha5 (was: 10.0.0.Alpha4) > Adding incorrect JGroups protocol should provide better error description than CNFE > ----------------------------------------------------------------------------------- > > Key: WFLY-3573 > URL: https://issues.jboss.org/browse/WFLY-3573 > Project: WildFly > Issue Type: Feature Request > Components: Clustering > Affects Versions: JBoss AS7 7.2.0.Final, 8.1.0.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Minor > Fix For: 10.0.0.Alpha5 > > > As reported by the community user: > {noformat} > [standalone@localhost:9990 / #] list-batch > #1 /subsystem=jgroups/stack=test:add() > #2 /subsystem=jgroups/stack=test/transport=TRANSPORT:add(type="udp",socket-binding=jgroups-udp) > #3 /subsystem=jgroups/stack=test:add-protocol(type=FD_SOCK,socket-binding=jgroups-udp-fd) > [standalone@localhost:9990 / #] run-batch > The batch failed with the following error (you are remaining in the batch editing mode to have a chance to correct the error): {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-1" => "WFLYCTL0158: Operation handler failed: java.lang.ClassNotFoundException: org.jgroups.protocols.udp from [Module \"org.jboss.as.clustering.jgroups:main\" from local module loader @4d9f6ce5 (finder: local module finder @1da65633 (roots: /home/rhusar/as/build/target/wildfly-9.0.0.Alpha1-SNAPSHOT/modules,/home/rhusar/as/build/target/wildfly-9.0.0.Alpha1-SNAPSHOT/modules/system/layers/base))]"}} > [standalone@localhost:9990 / #] > {noformat} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (WFLY-3582) Redesign mod_cluster xml subsystem parsers

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-3582?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-3582: ------------------------------- Fix Version/s: 10.0.0.Alpha5 (was: 10.0.0.Alpha4) > Redesign mod_cluster xml subsystem parsers > ------------------------------------------ > > Key: WFLY-3582 > URL: https://issues.jboss.org/browse/WFLY-3582 > Project: WildFly > Issue Type: Feature Request > Components: Clustering > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Fix For: 10.0.0.Alpha5 > > > As per https://github.com/wildfly/wildfly/pull/6449 -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (WFLY-4408) WFLY-2160 fix did not include transformation

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-4408?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-4408: ------------------------------- Fix Version/s: 10.0.0.Alpha5 (was: 10.0.0.Alpha4) > WFLY-2160 fix did not include transformation > -------------------------------------------- > > Key: WFLY-4408 > URL: https://issues.jboss.org/browse/WFLY-4408 > Project: WildFly > Issue Type: Bug > Components: JCA > Reporter: Brian Stansberry > Assignee: Stefano Maestri > Fix For: 10.0.0.Alpha5 > > > The WFLY-2160 patch (https://github.com/wildfly/wildfly/pull/6976/files) made the "enabled" attribute support expressions but did not add transformers to reject that setting if a legacy host controller is using the profile. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (WFLY-4379) Always expose <transaction-support> for resource adapters

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-4379?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-4379: ------------------------------- Fix Version/s: 10.0.0.Alpha5 (was: 10.0.0.Alpha4) > Always expose <transaction-support> for resource adapters > --------------------------------------------------------- > > Key: WFLY-4379 > URL: https://issues.jboss.org/browse/WFLY-4379 > Project: WildFly > Issue Type: Task > Components: JCA > Reporter: Jesper Pedersen > Assignee: Stefano Maestri > Priority: Critical > Fix For: 10.0.0.Alpha5 > > > The <transaction-support> setting for resource adapters should always be exposed in the DMR model - e.g. no "undefined". > If the value isn't explicit defined by the deployment, then it will be obtained from the metadata repository of the archive in question. > This also makes it clear that <xa-pool> is used for XATransaction deployments. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (WFLY-4340) use-try-lock exposed for <connection-definition>

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-4340?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-4340: ------------------------------- Fix Version/s: 10.0.0.Alpha5 (was: 10.0.0.Alpha4) > use-try-lock exposed for <connection-definition> > ------------------------------------------------ > > Key: WFLY-4340 > URL: https://issues.jboss.org/browse/WFLY-4340 > Project: WildFly > Issue Type: Bug > Components: JCA > Affects Versions: 8.2.0.Final > Reporter: Jesper Pedersen > Assignee: Stefano Maestri > Fix For: 10.0.0.Alpha5 > > > <connection-definition> DMR: > {noformat} > use-try-lock undefined LONG > {noformat} > which should be removed -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (WFLY-4304) Servlet authentication kicked off when *not* a part of any security-constraint

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-4304?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-4304: ------------------------------- Fix Version/s: 10.0.0.Alpha5 (was: 10.0.0.Alpha4) > Servlet authentication kicked off when *not* a part of any security-constraint > ------------------------------------------------------------------------------ > > Key: WFLY-4304 > URL: https://issues.jboss.org/browse/WFLY-4304 > Project: WildFly > Issue Type: Bug > Affects Versions: 8.2.0.Final > Reporter: Brett Meyer > Assignee: Darran Lofthouse > Fix For: 10.0.0.Alpha5 > > > Artificer runs on Wildfly 8.2 and uses Keycloak for auth. If our WAR contains a servlet that is *not* protected by a security-constraint in web.xml, Wildfly still attempts to authenticate the call (using Wireshark, I see the GET/POST get funneled through the Keycloak realm redirection) if basic auth credentials are in the header. In a keycloak-dev thread this past Dec., [~bill.burke] suggested this was most likely an issue within Wildfly auth itself. > A credentialed call on an un-protected servlet does sound like an edge case. However, this came up possibly due to a secondary symptom: > If I protect the servlet in web.xml, the call's Authorization header is stripped. I'm not currently able to figure out exactly where that's occurring... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (WFLY-4528) Product to Project Schema and Model Sync

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-4528?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-4528: ------------------------------- Fix Version/s: 10.0.0.Alpha5 (was: 10.0.0.Alpha4) > Product to Project Schema and Model Sync > ---------------------------------------- > > Key: WFLY-4528 > URL: https://issues.jboss.org/browse/WFLY-4528 > Project: WildFly > Issue Type: Task > Components: Domain Management > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 10.0.0.Alpha5 > > > Periodic sync of EAP schemas with WildFly. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (WFLY-4515) Fix clustering transformers and reenable in mixed-domain tests

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-4515?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-4515: ------------------------------- Fix Version/s: 10.0.0.Alpha5 (was: 10.0.0.Alpha4) > Fix clustering transformers and reenable in mixed-domain tests > -------------------------------------------------------------- > > Key: WFLY-4515 > URL: https://issues.jboss.org/browse/WFLY-4515 > Project: WildFly > Issue Type: Feature Request > Components: Clustering > Affects Versions: 9.0.0.Beta2 > Reporter: Kabir Khan > Assignee: Radoslav Husar > Priority: Critical > Fix For: 10.0.0.Alpha5 > > > When running the jgroups and infinispan subsystem tests with -Djboss.test.transformers.eap there are some failures in the transformers tests. > Also, in the mixed domain tests it is not possible to enable these subsystems, so I have removed them from DomainAdjuster620 in https://github.com/wildfly/wildfly/pull/7350. They should be reenabled again as part of this Jira. > Some info from private mail: > {quote} > However, when transforming that to 7.2.0 by running: > mvn clean install -DallTests -Djboss.test.mixed.domain.dir=/Users/kabir/old-as7-releases/ -pl testsuite/mixed-domain/ -Dtest=MixedDomain_7_2_0_Final_TestSuite > I get the following error: > 11:59:43,682 ERROR [org.jboss.as.host.controller] (Controller Boot Thread) JBAS010901: Could not connect to master. Aborting. Error was: java.io.IOException: 1-$-WFLYCTL0300: Transforming resource [ > ("profile" => "full-ha"), > ("subsystem" => "infinispan"), > ("cache-container" => "server"), > ("transport" => "TRANSPORT") > ] for host controller 'slave' to subsystem 'infinispan' model version '1.4.0' --there were problems with some of the attributes and this resource will need to be ignored on that host. Details of problems: [WFLYCLINF0027: Could not determine 'stack' attribute from JGroups subsystem] > I am not totally sure if this is the right solution, but I attempted to add a stack attribute to the transport, but it does not seem to get persisted so it goes away after reloading the DC (out of admin-only to normal mode). I also tried in standalone mode, and executing > /subsystem=infinispan/cache-container=server/transport=TRANSPORT:write-attribute(name=stack, value=udp) > and the stack does not get persisted. > It is probably a simple fix, but since I am not sure if it is the right fix or not, especially since adding this to the writer it also seems to be ignored by the parser. Perhaps this is a candidate for something along the lines of https://github.com/wildfly/wildfly/blob/master/clustering/jgroups/extensi... so that we can support old configs, but not actually use it on a server using the current version? > {quote} > Note that the above is when I was working on this, the 7.2.0 test has been removed. We now test EAP 6.2.0 and 6.3.0 compatibility. I believe the problem is similar there although I have not dug in very deeply. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (WFLY-4452) Use Flag.RESTART_RESOURCE_SERVICES for child resources of cache

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-4452?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-4452: ------------------------------- Fix Version/s: 10.0.0.Alpha5 (was: 10.0.0.Alpha4) > Use Flag.RESTART_RESOURCE_SERVICES for child resources of cache > --------------------------------------------------------------- > > Key: WFLY-4452 > URL: https://issues.jboss.org/browse/WFLY-4452 > Project: WildFly > Issue Type: Enhancement > Components: Clustering > Affects Versions: 9.0.0.Alpha1 > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Fix For: 10.0.0.Alpha5 > > > Currently, the attributes for each child resource of a cache use RESTART_ALL_SERVICES, thus any change to one of these attributes requires all services to restart. This is overkill, since only the services of the parent resource (i.e. cache) actually require restarting. > Ideally, each child resource should create a runtime service for its corresponding sub-configuration. e.g. the transaction resource would create a Service<TransactionConfiguration>. Thus the cache resource's add handler becomes much less complex - and the corresponding Service<Configuration> need only depend on the sub-configuration services for each child resource. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

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 June 2015