February 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-1492) The read-attribute result for platform mbean properties that throw UnsupportedOperationException should be 'undefined'

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1492?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-1492: ------------------------------------- Fix Version/s: (was: 3.0.0.Beta1) > The read-attribute result for platform mbean properties that throw UnsupportedOperationException should be 'undefined' > ---------------------------------------------------------------------------------------------------------------------- > > Key: WFCORE-1492 > URL: https://issues.jboss.org/browse/WFCORE-1492 > Project: WildFly Core > Issue Type: Enhancement > Components: Domain Management > Affects Versions: 2.1.0.Final > Reporter: Brian Stansberry > > Some platform mbean getters are documented to throw a UOE on some VMs. The read-resource handler will catch the UOE and leave the attribute undefined, but the read-attribute handler will convert the UOE to an OperationFailedException. This JIRA is to change that read-attribute behavior to return undefined as well. > There was a rationale for the different behavior. Basically, the read-attribute behavior is consistent with what the underlying java.lang.management.XXXMBean does -- it fails. Typically (probably always) there is another boolean getter on the mbean that will tell you if xxx is supported, with the assumption you won't call the unsupported method if not. But for read-resource, we are reading all the attributes, and we guarantee a response value. So we catch the exception and return undefined. > One minor downside to this is if JMX clients read these attributes, they'll get a null response instead of a failure. But I think that's ok; the MBeanAttributeInfo for these is created by us; these are not the real platform mbeans, they are our wrappers around them really intended for exposure over DMR, not JMX. If a JMX client wants the standard platform mbean semantics, they can access the real underlying platform mbeans. > This should be done in conjunction with WFCORE-406, which deals with ensuring our management metadata is correct. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1806) Split DomainModelControllerService into separate services for initializing as a master versus as a slave

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1806?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-1806: ------------------------------------- Fix Version/s: 4.0.0.Beta1 (was: 3.0.0.Beta1) > Split DomainModelControllerService into separate services for initializing as a master versus as a slave > -------------------------------------------------------------------------------------------------------- > > Key: WFCORE-1806 > URL: https://issues.jboss.org/browse/WFCORE-1806 > Project: WildFly Core > Issue Type: Task > Components: Domain Management > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Fix For: 4.0.0.Beta1 > > > This is an aspect of WFCORE-338, although it's valid in its own right as a conceptually cleaner approach to host controller boot. > Using different services is a prerequisite to WFCORE-338 as it allows those elements of HC behavior to be started/stopped as a DC candidate is elected or unelected. It also makes it feasible to wire in the service that performs the election. > The method that installs the service with MSC will return a Future<Boolean>, with the service setting the future's value at the completion of start(). DMCS during boot can block reading the future, from that confirm that the service completed successfully, and then proceed with the rest of boot. The boolean is basically an ok/not ok signal. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (AG-7) Migrate pool module from existent POC repo

by Luis Barreiro (JIRA)

Luis Barreiro created AG-7: ------------------------------ Summary: Migrate pool module from existent POC repo Key: AG-7 URL: https://issues.jboss.org/browse/AG-7 Project: Agroal Issue Type: Task Components: pool Reporter: Luis Barreiro Assignee: Luis Barreiro Move the connection pool code (integrated-object-pool) currently on https://github.com/barreiro/datasource-subsystem-poc/ to Agroal's git repo. Rename packages and classes to io.agroal.pool.* -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (AG-6) Migrate API module from existent POC repo

by Luis Barreiro (JIRA)

[ https://issues.jboss.org/browse/AG-6?page=com.atlassian.jira.plugin.syste... ] Luis Barreiro updated AG-6: --------------------------- Fix Version/s: 0.0.1 > Migrate API module from existent POC repo > ----------------------------------------- > > Key: AG-6 > URL: https://issues.jboss.org/browse/AG-6 > Project: Agroal > Issue Type: Task > Components: api > Reporter: Luis Barreiro > Assignee: Luis Barreiro > Fix For: 0.0.1 > > > Move the API code currently on https://github.com/barreiro/datasource-subsystem-poc/ to Agroal's git repo. > Rename packages and classes to io.agroal.api.* -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (AG-6) Migrate API module from existent POC repo

by Luis Barreiro (JIRA)

[ https://issues.jboss.org/browse/AG-6?page=com.atlassian.jira.plugin.syste... ] Luis Barreiro resolved AG-6. ---------------------------- Resolution: Done > Migrate API module from existent POC repo > ----------------------------------------- > > Key: AG-6 > URL: https://issues.jboss.org/browse/AG-6 > Project: Agroal > Issue Type: Task > Components: api > Reporter: Luis Barreiro > Assignee: Luis Barreiro > Fix For: 0.0.1 > > > Move the API code currently on https://github.com/barreiro/datasource-subsystem-poc/ to Agroal's git repo. > Rename packages and classes to io.agroal.api.* -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8068) Credential-store attribute relative-to doesn't reference path as required

by Josef Cacek (JIRA)

Josef Cacek created WFLY-8068: --------------------------------- Summary: Credential-store attribute relative-to doesn't reference path as required Key: WFLY-8068 URL: https://issues.jboss.org/browse/WFLY-8068 Project: WildFly Issue Type: Bug Components: Security Reporter: Josef Cacek Assignee: Darran Lofthouse Combination of {{path}} and {{relative-to}} attributes is common across all the elytron subsystem. All but one {{relative-to}} attributes list the "path" as required: {code} "relative-to" => { "type" => STRING, ... "requires" => ["path"], ... } {code} The credential-store configuration doesn't define this dependency. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ELY-935) Change case of aliased in beetles.keystore to match vase used in value of CN

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-935?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse resolved ELY-935. ---------------------------------- Resolution: Rejected Alias case wasn't the problem > Change case of aliased in beetles.keystore to match vase used in value of CN > ---------------------------------------------------------------------------- > > Key: ELY-935 > URL: https://issues.jboss.org/browse/ELY-935 > Project: WildFly Elytron > Issue Type: Task > Components: Testsuite > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.1.0.Beta24 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8067) Session scope resolver is not properly resolving sessions associated with the request

by Pedro Igor (JIRA)

Pedro Igor created WFLY-8067: -------------------------------- Summary: Session scope resolver is not properly resolving sessions associated with the request Key: WFLY-8067 URL: https://issues.jboss.org/browse/WFLY-8067 Project: WildFly Issue Type: Bug Components: Security, Web (Undertow) Reporter: Pedro Igor Assignee: Pedro Igor This issue impacts log in when using any stateful mechanism. It is basically a fix to WFLY-7111. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ELY-935) Change case of aliased in beetles.keystore to match vase used in value of CN

by Darran Lofthouse (JIRA)

Darran Lofthouse created ELY-935: ------------------------------------ Summary: Change case of aliased in beetles.keystore to match vase used in value of CN Key: ELY-935 URL: https://issues.jboss.org/browse/ELY-935 Project: WildFly Elytron Issue Type: Task Components: Testsuite Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 1.1.0.Beta24 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1432) Improve error messages when compiling modes with errors

by Edson Tirelli (JIRA)

Edson Tirelli created DROOLS-1432: ------------------------------------- Summary: Improve error messages when compiling modes with errors Key: DROOLS-1432 URL: https://issues.jboss.org/browse/DROOLS-1432 Project: Drools Issue Type: Bug Components: dmn engine Affects Versions: 7.0.0.Beta6 Reporter: Edson Tirelli Assignee: Edson Tirelli Fix For: 7.0.0.Final Attachments: car_damage_responsibility2.dmn When a model contains errors that prevent compilation, the engine should provide a better error message pointing to the specific error. At the moment, the attached model fails with a NPE and a message: {quote}Message [id=1, kieBase=defaultKieBase, level=ERROR, path=car_damage_responsibility2.dmn, line=-1, column=0 text=Unable to compile DMN model for the resource]{quote} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 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 February 2017