February 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-2286) GenericSubsystemDescribeHandler generates duplicates operations for override models

by Paul Ferraro (JIRA)

Paul Ferraro created WFCORE-2286: ------------------------------------ Summary: GenericSubsystemDescribeHandler generates duplicates operations for override models Key: WFCORE-2286 URL: https://issues.jboss.org/browse/WFCORE-2286 Project: WildFly Core Issue Type: Bug Components: Domain Management Affects Versions: 3.0.0.Alpha24 Reporter: Paul Ferraro Assignee: Paul Ferraro Currently, GenericSubsystemDescribeHandler relies on ImmutableManagementResourceRegistration.getChildAddresses(...) to find child resources. When processing a wildcard address, all resource children are matched. Thus any non-wildcard paths returned by getChildAddresses(...) for the same child type will end up being described twice. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ELY-53) GSSAPI Make Delegated Credential Available

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-53?page=com.atlassian.jira.plugin.sys... ] Darran Lofthouse reassigned ELY-53: ----------------------------------- Assignee: Darran Lofthouse > GSSAPI Make Delegated Credential Available > ------------------------------------------ > > Key: ELY-53 > URL: https://issues.jboss.org/browse/ELY-53 > Project: WildFly Elytron > Issue Type: Feature Request > Components: SASL > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.1.0.Beta25 > > > The server side of the mechanism can receive a delegated credential but there is no way to obtain it, we should provide a way for it to be obtained or provided. > _Note: This may be an Elytron integration point rather than something supported in the pure SASL mechanism._ -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1435) Runtime Exception while validating a file with Knowlge source

by Mélanie Gauthier (JIRA)

Mélanie Gauthier created DROOLS-1435: ---------------------------------------- Summary: Runtime Exception while validating a file with Knowlge source Key: DROOLS-1435 URL: https://issues.jboss.org/browse/DROOLS-1435 Project: Drools Issue Type: Bug Components: dmn engine Reporter: Mélanie Gauthier Assignee: Edson Tirelli Attachments: Cardamage_ks.dmn When validating the attached file, the following exception is raised: java.lang.RuntimeException: Error evaluating constraint 'id == rightOfHash( $oc.href )' in [Rule "REQAUTH_NOT_KNOWLEDGESOURCE" in rules.drl] If I remove the Knowledge Sources, the validation runs fine. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (HAWKULARQE-32) Cassandra/Hawkular Schema Test

by Matt Mahoney (JIRA)

[ https://issues.jboss.org/browse/HAWKULARQE-32?page=com.atlassian.jira.plu... ] Matt Mahoney updated HAWKULARQE-32: ----------------------------------- Summary: Cassandra/Hawkular Schema Test (was: Cassandra and Metrics Serice Restarts During Initialization) > Cassandra/Hawkular Schema Test > ------------------------------ > > Key: HAWKULARQE-32 > URL: https://issues.jboss.org/browse/HAWKULARQE-32 > Project: Hawkular QE > Issue Type: Task > Reporter: Matt Mahoney > Assignee: Sunil kondkar > > Test case request from Heiko (verbatim): > Start C*,wait until up. Start metrics/h-services > and once it starts schema creation (watch the logs), kill C*. Stop > h-services. Start C* again and then h-services,it should continue Schema > creation > While I was talking about h-services here, this applies foremost to > h-metrics (which is also used inside > of h-services). > Also I think Juca had a variation of this yesterday: > deploy h-metrics + C* into Openshift and then scale h-metrics up and > down at will. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (HAWKULARQE-32) Cassandra and Metrics Serice Restarts During Initialization

by Matt Mahoney (JIRA)

Matt Mahoney created HAWKULARQE-32: -------------------------------------- Summary: Cassandra and Metrics Serice Restarts During Initialization Key: HAWKULARQE-32 URL: https://issues.jboss.org/browse/HAWKULARQE-32 Project: Hawkular QE Issue Type: Task Reporter: Matt Mahoney Assignee: Sunil kondkar Test case request from Heiko (verbatim): Start C*,wait until up. Start metrics/h-services and once it starts schema creation (watch the logs), kill C*. Stop h-services. Start C* again and then h-services,it should continue Schema creation While I was talking about h-services here, this applies foremost to h-metrics (which is also used inside of h-services). Also I think Juca had a variation of this yesterday: deploy h-metrics + C* into Openshift and then scale h-metrics up and down at will. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ELY-37) Audit Logging Integration

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-37?page=com.atlassian.jira.plugin.sys... ] Darran Lofthouse updated ELY-37: -------------------------------- Fix Version/s: 1.1.0.Beta24 (was: 1.1.0.CR1) > Audit Logging Integration > ------------------------- > > Key: ELY-37 > URL: https://issues.jboss.org/browse/ELY-37 > Project: WildFly Elytron > Issue Type: Task > Components: API / SPI, Audit > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.1.0.Beta24 > > > Implement into Elytron samething like: > https://github.com/picketbox/picketbox/tree/master/security-spi/spi/src/m... > or > https://github.com/wildfly/wildfly-core/tree/master/controller/src/main/j... > or > https://github.com/kabir/tamper-detecting-audit-log > UPDATE: > By discussion should be based on currently not implemented processing of **security events** - depends on it from now. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ELY-37) Audit Logging Integration

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-37?page=com.atlassian.jira.plugin.sys... ] Darran Lofthouse reassigned ELY-37: ----------------------------------- Assignee: Darran Lofthouse (was: Jan Kalina) > Audit Logging Integration > ------------------------- > > Key: ELY-37 > URL: https://issues.jboss.org/browse/ELY-37 > Project: WildFly Elytron > Issue Type: Task > Components: API / SPI, Audit > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.1.0.Beta24 > > > Implement into Elytron samething like: > https://github.com/picketbox/picketbox/tree/master/security-spi/spi/src/m... > or > https://github.com/wildfly/wildfly-core/tree/master/controller/src/main/j... > or > https://github.com/kabir/tamper-detecting-audit-log > UPDATE: > By discussion should be based on currently not implemented processing of **security events** - depends on it from now. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ELY-37) Audit Logging Integration

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-37?page=com.atlassian.jira.plugin.sys... ] Darran Lofthouse updated ELY-37: -------------------------------- Priority: Critical (was: Major) > Audit Logging Integration > ------------------------- > > Key: ELY-37 > URL: https://issues.jboss.org/browse/ELY-37 > Project: WildFly Elytron > Issue Type: Task > Components: API / SPI, Audit > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Critical > Fix For: 1.1.0.Beta24 > > > Implement into Elytron samething like: > https://github.com/picketbox/picketbox/tree/master/security-spi/spi/src/m... > or > https://github.com/wildfly/wildfly-core/tree/master/controller/src/main/j... > or > https://github.com/kabir/tamper-detecting-audit-log > UPDATE: > By discussion should be based on currently not implemented processing of **security events** - depends on it from now. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8078) Add ability to use an XA data source from many distributed JTA nodes

by David Lloyd (JIRA)

David Lloyd created WFLY-8078: --------------------------------- Summary: Add ability to use an XA data source from many distributed JTA nodes Key: WFLY-8078 URL: https://issues.jboss.org/browse/WFLY-8078 Project: WildFly Issue Type: Enhancement Components: Transactions Reporter: David Lloyd Priority: Optional *Note* that this issue is not scheduled and is low priority. To start, it is just a point to conjecture implementation possibilities. Provide the ability for a data source (or other XA resource) to be utilized from multiple nodes in the distributed JTA node graph. This may allow multiple nodes to operate within the same transaction on these resources. The requirements are: # The XA resource in question must support multiple connections # A way is needed to ensure that all nodes are using the same branch qualifier for the given resource # A way is needed to decide which node is the "master" for the given resource Requirement #2 is necessary because otherwise the node in question may not be able to correlate the incoming connections. Requirement #3 is necessary to avoid multiple nodes preparing the transaction. The usual JTA technique of using isSameRM does not work because every node has their own partial view of the complete set of XA resources involved in the distributed transaction. Some possible ideas (not complete and not mutually inclusive or exclusive): * Allow hard-coding a branch qualifier for a resource in some way, so all nodes always use the same branch ID for a given resource * Somehow communicate all resource enlistments to the root node during prepare so the root node can determine which ones need to be prepared via isSameRM checks (this would require serializing the XA resources, which in turn requires (more or less) all nodes to have all classes for all resources present and loadable) * Revisit idea of hierarchical branch qualifiers * ...(add your idea here!) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (HAWKULARQE-28) hawkular-qe-manual

by Matt Mahoney (JIRA)

[ https://issues.jboss.org/browse/HAWKULARQE-28?page=com.atlassian.jira.plu... ] Matt Mahoney updated HAWKULARQE-28: ----------------------------------- Description: https://polarion.engineering.redhat.com/polarion/#/project/JBossON4/worki... https://polarion.engineering.redhat.com/polarion/#/project/JBossON4/worki... https://polarion.engineering.redhat.com/polarion/#/project/JBossON4/worki... https://polarion.engineering.redhat.com/polarion/#/project/JBossON4/worki... > hawkular-qe-manual > ------------------ > > Key: HAWKULARQE-28 > URL: https://issues.jboss.org/browse/HAWKULARQE-28 > Project: Hawkular QE > Issue Type: Sub-task > Reporter: Matt Mahoney > Assignee: mfoley user > > https://polarion.engineering.redhat.com/polarion/#/project/JBossON4/worki... > https://polarion.engineering.redhat.com/polarion/#/project/JBossON4/worki... > https://polarion.engineering.redhat.com/polarion/#/project/JBossON4/worki... > https://polarion.engineering.redhat.com/polarion/#/project/JBossON4/worki... -- 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