August 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-1735) Missing https://github.com/wildfly/wildfly-capabilities entry for capability org.wildfly.network.interface

by Brian Stansberry (JIRA)

Brian Stansberry created WFCORE-1735: ---------------------------------------- Summary: Missing https://github.com/wildfly/wildfly-capabilities entry for capability org.wildfly.network.interface Key: WFCORE-1735 URL: https://issues.jboss.org/browse/WFCORE-1735 Project: WildFly Core Issue Type: Bug Components: Domain Management Reporter: Brian Stansberry Assignee: Brian Stansberry Missing are: org.wildfly.domain.socket-binding-group org.wildfly.domain.profile org.wildfly.domain.server-group org.wildfly.domain.server-config -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1734) Missing https://github.com/wildfly/wildfly-capabilities entry for managed domain capabilities

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1734?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-1734: ------------------------------------- Description: Missing are: org.wildfly.domain.socket-binding-group org.wildfly.domain.profile org.wildfly.domain.server-group org.wildfly.domain.server-config was:$subject says it all. Summary: Missing https://github.com/wildfly/wildfly-capabilities entry for managed domain capabilities (was: Missing https://github.com/wildfly/wildfly-capabilities entry for capability org.wildfly.domain.socket-binding-group) > Missing https://github.com/wildfly/wildfly-capabilities entry for managed domain capabilities > ---------------------------------------------------------------------------------------------- > > Key: WFCORE-1734 > URL: https://issues.jboss.org/browse/WFCORE-1734 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Reporter: Brian Stansberry > Assignee: Brian Stansberry > > Missing are: > org.wildfly.domain.socket-binding-group > org.wildfly.domain.profile > org.wildfly.domain.server-group > org.wildfly.domain.server-config -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1734) Missing https://github.com/wildfly/wildfly-capabilities entry for capability org.wildfly.domain.socket-binding-group

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1734?page=com.atlassian.jira.plugi... ] Brian Stansberry moved WFLY-7014 to WFCORE-1734: ------------------------------------------------ Project: WildFly Core (was: WildFly) Key: WFCORE-1734 (was: WFLY-7014) Component/s: Domain Management (was: Domain Management) > Missing https://github.com/wildfly/wildfly-capabilities entry for capability org.wildfly.domain.socket-binding-group > -------------------------------------------------------------------------------------------------------------------- > > Key: WFCORE-1734 > URL: https://issues.jboss.org/browse/WFCORE-1734 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Reporter: Brian Stansberry > Assignee: Brian Stansberry > > $subject says it all. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7014) Missing https://github.com/wildfly/wildfly-capabilities entry for capability org.wildfly.domain.socket-binding-group

by Brian Stansberry (JIRA)

Brian Stansberry created WFLY-7014: -------------------------------------- Summary: Missing https://github.com/wildfly/wildfly-capabilities entry for capability org.wildfly.domain.socket-binding-group Key: WFLY-7014 URL: https://issues.jboss.org/browse/WFLY-7014 Project: WildFly Issue Type: Bug Components: JMX Reporter: Brian Stansberry Assignee: Brian Stansberry $subject says it all. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7014) Missing https://github.com/wildfly/wildfly-capabilities entry for capability org.wildfly.domain.socket-binding-group

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-7014?page=com.atlassian.jira.plugin.... ] Brian Stansberry updated WFLY-7014: ----------------------------------- Component/s: Domain Management (was: JMX) > Missing https://github.com/wildfly/wildfly-capabilities entry for capability org.wildfly.domain.socket-binding-group > -------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-7014 > URL: https://issues.jboss.org/browse/WFLY-7014 > Project: WildFly > Issue Type: Bug > Components: Domain Management > Reporter: Brian Stansberry > Assignee: Brian Stansberry > > $subject says it all. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7013) rrd on data-source=*/statistics=pool throws NPE

by Claudio Miranda (JIRA)

Claudio Miranda created WFLY-7013: ------------------------------------- Summary: rrd on data-source=*/statistics=pool throws NPE Key: WFLY-7013 URL: https://issues.jboss.org/browse/WFLY-7013 Project: WildFly Issue Type: Bug Components: Domain Management Reporter: Claudio Miranda Assignee: Brian Stansberry Run the following command in CLI it throws a NullPointerException As it is a rrd it should not require a resolved wildcard {code} /subsystem=datasources/data-source=*/statistics=pool:read-resource-description {code} Results {code} { "outcome" => "failed", "result" => [], "failure-description" => "WFLYCTL0158: Operation handler failed: java.lang.NullPointerException", "rolled-back" => true } {code} The exception throws at server.log {code} ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 4) WFLYCTL0013: Operation ("resolve") failed - address: ([]): java.lang.NullPointerException at org.jboss.as.controller.operations.global.GlobalOperationHandlers$AbstractAddressResolver.execute(GlobalOperationHandlers.java:422) at org.jboss.as.controller.operations.global.GlobalOperationHandlers$RegistrationAddressResolver.executeSingleTargetChild(GlobalOperationHandlers.java:903) at org.jboss.as.controller.operations.global.GlobalOperationHandlers$AbstractAddressResolver.execute(GlobalOperationHandlers.java:442) at org.jboss.as.controller.operations.global.GlobalOperationHandlers$RegistrationAddressResolver.executeMultiTargetChildren(GlobalOperationHandlers.java:895) at org.jboss.as.controller.operations.global.GlobalOperationHandlers$AbstractAddressResolver.execute(GlobalOperationHandlers.java:440) at org.jboss.as.controller.operations.global.GlobalOperationHandlers$RegistrationAddressResolver.executeSingleTargetChild(GlobalOperationHandlers.java:903) at org.jboss.as.controller.operations.global.GlobalOperationHandlers$AbstractAddressResolver.execute(GlobalOperationHandlers.java:442) at org.jboss.as.controller.operations.global.GlobalOperationHandlers$AbstractAddressResolver.execute(GlobalOperationHandlers.java:337) at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:951) at org.jboss.as.controller.AbstractOperationContext.processStages(AbstractOperationContext.java:694) at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:389) at org.jboss.as.controller.OperationContextImpl.executeOperation(OperationContextImpl.java:1363) at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:410) at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:232) at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.doExecute(ModelControllerClientOperationHandler.java:213) at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.access$300(ModelControllerClientOperationHandler.java:136) at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:157) at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:153) at java.security.AccessController.doPrivileged(Native Method) at javax.security.auth.Subject.doAs(Subject.java:422) at org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:149) at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1.execute(ModelControllerClientOperationHandler.java:153) at org.jboss.as.protocol.mgmt.ManagementRequestContextImpl$1.doExecute(ManagementRequestContextImpl.java:70) at org.jboss.as.protocol.mgmt.ManagementRequestContextImpl$AsyncTaskRunner.run(ManagementRequestContextImpl.java:160) 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} This op works {code} /subsystem=datasources/data-source=*:read-resource-description {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ELY-587) SSLContext integration into DirContext supplier service

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/ELY-587?page=com.atlassian.jira.plugin.sy... ] Jan Kalina commented on ELY-587: -------------------------------- In the end ThreadLocal variable is used. I was worry about possible auto-reconnect inside of DirContext - as the ThreadLocal variable is set only during DirContext construction/reconnect() method call, auto-reconnect after TCP connection breaking would fail - variable would not be set and would not be posible to determine for which DirContext should be SSLSocketFactory provided. *This risk was disproved* by experiment - standard DirContext doesnt reconnect interrupted TCP connections - it throws *CommunicationException: connection closed* exception instead. (which is OK) > SSLContext integration into DirContext supplier service > ------------------------------------------------------- > > Key: ELY-587 > URL: https://issues.jboss.org/browse/ELY-587 > Project: WildFly Elytron > Issue Type: Task > Components: SSL > Reporter: Jan Kalina > Assignee: Jan Kalina > > * we already have a resource to define the SSLContext > * we want use it for connection to LDAP > * resource of DirContext supplier (see ELY-462) should reference SSLContext resource / capability -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ELY-587) SSLContext integration into DirContext supplier service

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/ELY-587?page=com.atlassian.jira.plugin.sy... ] Jan Kalina edited comment on ELY-587 at 8/25/16 2:05 PM: --------------------------------------------------------- *In the end ThreadLocal variable is used.* I was worry about possible auto-reconnect inside of DirContext - as the ThreadLocal variable is set only during DirContext construction/reconnect() method call, auto-reconnect after TCP connection breaking would fail - variable would not be set and would not be posible to determine for which DirContext should be SSLSocketFactory provided. *This risk was disproved* by experiment - standard DirContext doesnt reconnect interrupted TCP connections - it throws *CommunicationException: connection closed* exception instead. (which is OK) was (Author: honza889): In the end ThreadLocal variable is used. I was worry about possible auto-reconnect inside of DirContext - as the ThreadLocal variable is set only during DirContext construction/reconnect() method call, auto-reconnect after TCP connection breaking would fail - variable would not be set and would not be posible to determine for which DirContext should be SSLSocketFactory provided. *This risk was disproved* by experiment - standard DirContext doesnt reconnect interrupted TCP connections - it throws *CommunicationException: connection closed* exception instead. (which is OK) > SSLContext integration into DirContext supplier service > ------------------------------------------------------- > > Key: ELY-587 > URL: https://issues.jboss.org/browse/ELY-587 > Project: WildFly Elytron > Issue Type: Task > Components: SSL > Reporter: Jan Kalina > Assignee: Jan Kalina > > * we already have a resource to define the SSLContext > * we want use it for connection to LDAP > * resource of DirContext supplier (see ELY-462) should reference SSLContext resource / capability -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7012) Missing https://github.com/wildfly/wildfly-capabilities entry for capability org.wildfly.extension.undertow.handler

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-7012?page=com.atlassian.jira.plugin.... ] Brian Stansberry reassigned WFLY-7012: -------------------------------------- Description: The contract for this capability needs examination and recording in the registry. Note that the task here is not to just create a meaningless entry. Once the entry is published a contract is established, so the contract has to be correct. was: The contract for this capability needs examination and recording in the registry. Note that the task here is not to just create a meaningless entry. Once the entry is published a contract is established, so the contract has to be correct. ListenerService doesn't look like a good API to be exposed to external callers; it exposes details that probably should not be part of a contract. Assignee: Stuart Douglas (was: Ingo Weiss) > Missing https://github.com/wildfly/wildfly-capabilities entry for capability org.wildfly.extension.undertow.handler > ------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-7012 > URL: https://issues.jboss.org/browse/WFLY-7012 > Project: WildFly > Issue Type: Bug > Components: Security > Reporter: Brian Stansberry > Assignee: Stuart Douglas > > The contract for this capability needs examination and recording in the registry. > Note that the task here is not to just create a meaningless entry. Once the entry is published a contract is established, so the contract has to be correct. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7011) Missing https://github.com/wildfly/wildfly-capabilities entry for capability org.wildfly.undertow.listener

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-7011?page=com.atlassian.jira.plugin.... ] Brian Stansberry reassigned WFLY-7011: -------------------------------------- Assignee: Ingo Weiss (was: Brian Stansberry) [~iweiss] I'm assigning this to you as a follow up to our chat today. This is one of various JIRAs I'm opening as I examine the state of https://github.com/wildfly/wildfly-capabilities compared to the WildFly [Core] code. [~swd847] FYI. > Missing https://github.com/wildfly/wildfly-capabilities entry for capability org.wildfly.undertow.listener > ---------------------------------------------------------------------------------------------------------- > > Key: WFLY-7011 > URL: https://issues.jboss.org/browse/WFLY-7011 > Project: WildFly > Issue Type: Bug > Components: Security > Reporter: Brian Stansberry > Assignee: Ingo Weiss > > The contract for this capability needs examination and recording in the registry. > Note that the task here is not to just create a meaningless entry. Once the entry is published a contract is established, so the contract has to be correct. ListenerService doesn't look like a good API to be exposed to external callers; it exposes details that probably should not be part of a contract. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 4 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira August 2016