April 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-8514) Default profiles reference deprecated mod_cluster module extension org.jboss.as.modcluster

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-8514?page=com.atlassian.jira.plugin.... ] Radoslav Husar updated WFLY-8514: --------------------------------- Description: The correct module to reference is {{org.wildfly.extension.mod_cluster}}. (was: We want to reference {{org.wildfly.extension.mod_cluster}}.) > Default profiles reference deprecated mod_cluster module extension org.jboss.as.modcluster > ------------------------------------------------------------------------------------------ > > Key: WFLY-8514 > URL: https://issues.jboss.org/browse/WFLY-8514 > Project: WildFly > Issue Type: Bug > Components: mod_cluster > Affects Versions: 11.0.0.Alpha1 > Reporter: Radoslav Husar > Assignee: Radoslav Husar > > The correct module to reference is {{org.wildfly.extension.mod_cluster}}. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8514) Default profiles reference deprecated mod_cluster module extension org.jboss.as.modcluster

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-8514?page=com.atlassian.jira.plugin.... ] Radoslav Husar updated WFLY-8514: --------------------------------- Issue Type: Bug (was: Feature Request) > Default profiles reference deprecated mod_cluster module extension org.jboss.as.modcluster > ------------------------------------------------------------------------------------------ > > Key: WFLY-8514 > URL: https://issues.jboss.org/browse/WFLY-8514 > Project: WildFly > Issue Type: Bug > Components: mod_cluster > Affects Versions: 11.0.0.Alpha1 > Reporter: Radoslav Husar > Assignee: Radoslav Husar > > We want to reference {{org.wildfly.extension.mod_cluster}}. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8514) Default profiles reference deprecated mod_cluster module extension org.jboss.as.modcluster

by Radoslav Husar (JIRA)

Radoslav Husar created WFLY-8514: ------------------------------------ Summary: Default profiles reference deprecated mod_cluster module extension org.jboss.as.modcluster Key: WFLY-8514 URL: https://issues.jboss.org/browse/WFLY-8514 Project: WildFly Issue Type: Feature Request Components: mod_cluster Affects Versions: 11.0.0.Alpha1 Reporter: Radoslav Husar Assignee: Radoslav Husar We want to reference {{org.wildfly.extension.mod_cluster}}. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (HAWKULARQE-1) [QE] - JMAN4-111 - Immutability of JBoss Middleware services running in containers

by Hayk Hovsepyan (JIRA)

[ https://issues.jboss.org/browse/HAWKULARQE-1?page=com.atlassian.jira.plug... ] Hayk Hovsepyan commented on HAWKULARQE-1: ----------------------------------------- tested downstream on DR4, for standalone mode the container is immutable, checking for domain mode > [QE] - JMAN4-111 - Immutability of JBoss Middleware services running in containers > ---------------------------------------------------------------------------------- > > Key: HAWKULARQE-1 > URL: https://issues.jboss.org/browse/HAWKULARQE-1 > Project: Hawkular QE > Issue Type: Task > Reporter: Hayk Hovsepyan > Assignee: Hayk Hovsepyan > Priority: Blocker > Labels: mm-integration-hawkular-qe > > See [JMAN4-111|https://issues.jboss.org/browse/JMAN4-111] -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8512) Private undertow capability service values expose org.jboss.msc.service.Service methods

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-8512?page=com.atlassian.jira.plugin.... ] Brian Stansberry commented on WFLY-8512: ---------------------------------------- Thanks for the JIRA though; we need a tracker to clean this up and get contracts that we can make public. The current capabilities are private but are used externally. This is no worse than what we had before where the services were used externally directly, which is why I was ok with what's been done so far. Beyond not implementing Service, the types exposed by the capabilities need to be scrubbed of methods that are not needed externally. > Private undertow capability service values expose org.jboss.msc.service.Service methods > --------------------------------------------------------------------------------------- > > Key: WFLY-8512 > URL: https://issues.jboss.org/browse/WFLY-8512 > Project: WildFly > Issue Type: Enhancement > Components: Web (Undertow) > Affects Versions: 11.0.0.Alpha1 > Reporter: Paul Ferraro > Assignee: Tomaz Cerar > Priority: Minor > > Undertow new exposes UndertowService, Server, Host, etc. to other subsystems as service values of public capabilities. However, these objects all implement Service, and thus expose start/stop methods to their dependents. This is poor encapsulation. Ideally, we should extract interfaces from these objects such that the corresponding capabilities only expose methods in explicitly in their contract. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2615) Attribute allow-sasl-mechanisms is ignored in Elytron Authentication Configuration

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2615?page=com.atlassian.jira.plugi... ] David Lloyd commented on WFCORE-2615: ------------------------------------- The mechanisms are selected by starting with the list of all known mechanisms. Then, for each mechanism, the authentication-configuration is examined to answer questions like: what kind of Principal is there? What kinds of Credential are available? If a mechanism is not supported by the configuration (for example, to use PLAIN you must have a user name and password, so if there is no password then the configuration does not support the mechanism), then it is only attempted if it was explicitly allowed. The allow-all-mechanisms option maps to removing all mechanisms from the forbidden set (which already defaults to empty so normally you don't need this unless you're overriding another configuration). > Attribute allow-sasl-mechanisms is ignored in Elytron Authentication Configuration > ---------------------------------------------------------------------------------- > > Key: WFCORE-2615 > URL: https://issues.jboss.org/browse/WFCORE-2615 > Project: WildFly Core > Issue Type: Bug > Components: Security > Affects Versions: 3.0.0.Beta10 > Reporter: Ondrej Lukas > Assignee: Darran Lofthouse > Priority: Blocker > Attachments: dep.war, wireshark.pcapng > > > In case when attribute allow-sasl-mechanisms from Elytron Authentication Configuration includes some SASL mechanisms then this attribute (and mechanisms configured there) is not taken into account during choosing SASL mechanism. It means that client tries to use all of mechanisms allowed on server side even if client does not allow them. e.g. in case when server side allowed DIGEST-MD5 and JBOSS-LOCAL-USER and client side allows PLAIN, then it tries to use DIGEST-MD5 and JBOSS-LOCAL-USER mechanisms. > See log from wireshark in attachments. This is log for server configured through "Steps to Reproduce". > This happens also for using allow-sasl-mechanisms from wildfly config and also for programatically configured client. > We request blocker since it allows to use some SASL mechanisms even if they are not allowed on client side. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8513) Fix parsers in mails subsystem to have proper namespace

by Tomaz Cerar (JIRA)

Tomaz Cerar created WFLY-8513: --------------------------------- Summary: Fix parsers in mails subsystem to have proper namespace Key: WFLY-8513 URL: https://issues.jboss.org/browse/WFLY-8513 Project: WildFly Issue Type: Bug Components: Mail Reporter: Tomaz Cerar Assignee: Tomaz Cerar Version of mail subsystem xsd & model must be 3.0 in wildfly 11 not 2.1 as is currently -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2157) Full-replace rollback is failing with java.util.NoSuchElementException: No child 'name' exists: java.util.NoSuchElementException: No child > 'name' exists

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2157?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration commented on WFCORE-2157: ------------------------------------------------- Radovan Netuka <rnetuka(a)redhat.com> changed the Status of [bug 1434597|https://bugzilla.redhat.com/show_bug.cgi?id=1434597] from POST to MODIFIED > Full-replace rollback is failing with java.util.NoSuchElementException: No child 'name' exists: java.util.NoSuchElementException: No child > 'name' exists > ---------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: WFCORE-2157 > URL: https://issues.jboss.org/browse/WFCORE-2157 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Affects Versions: 3.0.0.Alpha16 > Reporter: ehsavoie Hugonnet > Assignee: ehsavoie Hugonnet > Labels: downstream_dependency > Fix For: 3.0.0.Alpha18 > > > 21:24:18,013 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 56) WFLYCTL0190: Step > > handler org.jboss.as.server.deployment.DeploymentHandlerUtil$4@6f678cd for operation {"operation" => "full-replace-deployment","name" => > > "drmk22.ear","enabled" => true,"content" => [{"hash" => bytes { 0x40, 0xde, 0xe4, 0x1d, 0xdd, 0xd0, 0xa7, 0x9f, 0xa9, 0x7a, 0x92, 0x84, > > 0xee, 0x92, 0x81, 0xea, 0x5d, 0x7b, 0xa3, 0x2a }}],"operation-headers" => {"access-mechanism" => "NATIVE","domain-uuid" => > > "cf11aeb2-70b8-4f64-aa64-67fffd9c8080"},"address" => [],"runtime-name" => undefined,"persistent" => true,"owner" => undefined} at address [] > > failed handling operation rollback -- java.util.NoSuchElementException: No child 'name' exists: java.util.NoSuchElementException: No child > > 'name' exists > > at org.jboss.dmr.ModelValue.requireChild(ModelValue.java:387) > > at org.jboss.dmr.ObjectModelValue.requireChild(ObjectModelValue.java:302) > > at org.jboss.dmr.ModelNode.require(ModelNode.java:875) > > at org.jboss.as.server.deployment.DeploymentHandlerUtil$4$1.handleResult(DeploymentHandlerUtil.java:331) > > at org.jboss.as.controller.AbstractOperationContext$Step.invokeResultHandler(AbstractOperationContext.java:1435) > > at org.jboss.as.controller.AbstractOperationContext$Step.handleResult(AbstractOperationContext.java:1417) > > at org.jboss.as.controller.AbstractOperationContext$Step.finalizeInternal(AbstractOperationContext.java:1379) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8512) Private undertow capability service values expose org.jboss.msc.service.Service methods

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-8512?page=com.atlassian.jira.plugin.... ] Tomaz Cerar commented on WFLY-8512: ----------------------------------- [~pferraro] see https://github.com/wildfly/wildfly-capabilities/pull/13 for docs about capability, all that you mentioned are private. > Private undertow capability service values expose org.jboss.msc.service.Service methods > --------------------------------------------------------------------------------------- > > Key: WFLY-8512 > URL: https://issues.jboss.org/browse/WFLY-8512 > Project: WildFly > Issue Type: Enhancement > Components: Web (Undertow) > Affects Versions: 11.0.0.Alpha1 > Reporter: Paul Ferraro > Assignee: Tomaz Cerar > Priority: Minor > > Undertow new exposes UndertowService, Server, Host, etc. to other subsystems as service values of public capabilities. However, these objects all implement Service, and thus expose start/stop methods to their dependents. This is poor encapsulation. Ideally, we should extract interfaces from these objects such that the corresponding capabilities only expose methods in explicitly in their contract. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8512) Private undertow capability service values expose org.jboss.msc.service.Service methods

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-8512?page=com.atlassian.jira.plugin.... ] Tomaz Cerar updated WFLY-8512: ------------------------------ Priority: Minor (was: Major) > Private undertow capability service values expose org.jboss.msc.service.Service methods > --------------------------------------------------------------------------------------- > > Key: WFLY-8512 > URL: https://issues.jboss.org/browse/WFLY-8512 > Project: WildFly > Issue Type: Enhancement > Components: Web (Undertow) > Affects Versions: 11.0.0.Alpha1 > Reporter: Paul Ferraro > Assignee: Tomaz Cerar > Priority: Minor > > Undertow new exposes UndertowService, Server, Host, etc. to other subsystems as service values of public capabilities. However, these objects all implement Service, and thus expose start/stop methods to their dependents. This is poor encapsulation. Ideally, we should extract interfaces from these objects such that the corresponding capabilities only expose methods in explicitly in their contract. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 7 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira April 2017