September 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-5970) Plain JMS clients don't fallback

by Jeff Mesnil (JIRA)

[ https://issues.jboss.org/browse/WFLY-5970?page=com.atlassian.jira.plugin.... ] Jeff Mesnil reopened WFLY-5970: ------------------------------- > Plain JMS clients don't fallback > -------------------------------- > > Key: WFLY-5970 > URL: https://issues.jboss.org/browse/WFLY-5970 > Project: WildFly > Issue Type: Bug > Components: EE > Affects Versions: 9.0.2.Final, 10.0.0.Final > Environment: all > Reporter: Yong Hao Gao > Assignee: Yong Hao Gao > > Plain JMS clients don't fallback when the Live server takes over > Version-Release number of selected component > messaging subsystem 1.4 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5970) Plain JMS clients don't fallback

by Jeff Mesnil (JIRA)

[ https://issues.jboss.org/browse/WFLY-5970?page=com.atlassian.jira.plugin.... ] Jeff Mesnil closed WFLY-5970. ----------------------------- Resolution: Duplicate Issue > Plain JMS clients don't fallback > -------------------------------- > > Key: WFLY-5970 > URL: https://issues.jboss.org/browse/WFLY-5970 > Project: WildFly > Issue Type: Bug > Components: EE > Affects Versions: 9.0.2.Final, 10.0.0.Final > Environment: all > Reporter: Yong Hao Gao > Assignee: Yong Hao Gao > > Plain JMS clients don't fallback when the Live server takes over > Version-Release number of selected component > messaging subsystem 1.4 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6602) Expose JGroups channels and channel factories as capabilities

by Paul Ferraro (JIRA)

[ https://issues.jboss.org/browse/WFLY-6602?page=com.atlassian.jira.plugin.... ] Paul Ferraro updated WFLY-6602: ------------------------------- Issue Type: Bug (was: Enhancement) > Expose JGroups channels and channel factories as capabilities > ------------------------------------------------------------- > > Key: WFLY-6602 > URL: https://issues.jboss.org/browse/WFLY-6602 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 10.0.0.Final > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Fix For: 11.0.0.Alpha1 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6603) Expose Infinispan caches and containers as capabilities

by Paul Ferraro (JIRA)

[ https://issues.jboss.org/browse/WFLY-6603?page=com.atlassian.jira.plugin.... ] Paul Ferraro updated WFLY-6603: ------------------------------- Issue Type: Bug (was: Enhancement) > Expose Infinispan caches and containers as capabilities > ------------------------------------------------------- > > Key: WFLY-6603 > URL: https://issues.jboss.org/browse/WFLY-6603 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 10.0.0.Final > Reporter: Paul Ferraro > Assignee: Paul Ferraro > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6604) Expose clustering API abstractions as capabilities

by Paul Ferraro (JIRA)

[ https://issues.jboss.org/browse/WFLY-6604?page=com.atlassian.jira.plugin.... ] Paul Ferraro updated WFLY-6604: ------------------------------- Issue Type: Bug (was: Enhancement) > Expose clustering API abstractions as capabilities > -------------------------------------------------- > > Key: WFLY-6604 > URL: https://issues.jboss.org/browse/WFLY-6604 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 10.0.0.Final > Reporter: Paul Ferraro > Assignee: Paul Ferraro > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7113) Naming subsystem does not expose a proper capability contract

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-7113?page=com.atlassian.jira.plugin.... ] Brian Stansberry updated WFLY-7113: ----------------------------------- Issue Type: Bug (was: Feature Request) Summary: Naming subsystem does not expose a proper capability contract (was: Expose capabilities for naming subsystem) > Naming subsystem does not expose a proper capability contract > ------------------------------------------------------------- > > Key: WFLY-7113 > URL: https://issues.jboss.org/browse/WFLY-7113 > Project: WildFly > Issue Type: Bug > Components: Naming > Affects Versions: 10.1.0.Final > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Fix For: 11.0.0.Alpha1 > > > Subsystems that currently use JNDI bindings require that the naming subsystem be present. The naming subsystem should expose capabilities for which other subsystems can test for the presence, so they can function in the absence of the naming subsystem. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7113) Expose capabilities for naming subsystem

by Paul Ferraro (JIRA)

[ https://issues.jboss.org/browse/WFLY-7113?page=com.atlassian.jira.plugin.... ] Paul Ferraro reassigned WFLY-7113: ---------------------------------- Assignee: Paul Ferraro > Expose capabilities for naming subsystem > ---------------------------------------- > > Key: WFLY-7113 > URL: https://issues.jboss.org/browse/WFLY-7113 > Project: WildFly > Issue Type: Feature Request > Components: Naming > Affects Versions: 10.1.0.Final > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Fix For: 11.0.0.Alpha1 > > > Subsystems that currently use JNDI bindings require that the naming subsystem be present. The naming subsystem should expose capabilities for which other subsystems can test for the presence, so they can function in the absence of the naming subsystem. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7113) Expose capabilities for naming subsystem

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-7113?page=com.atlassian.jira.plugin.... ] Darran Lofthouse commented on WFLY-7113: ---------------------------------------- [~fjuma] FYI not assigned yet but I know you are looking at this subsystem as well. > Expose capabilities for naming subsystem > ---------------------------------------- > > Key: WFLY-7113 > URL: https://issues.jboss.org/browse/WFLY-7113 > Project: WildFly > Issue Type: Feature Request > Components: Naming > Affects Versions: 10.1.0.Final > Reporter: Paul Ferraro > Fix For: 11.0.0.Alpha1 > > > Subsystems that currently use JNDI bindings require that the naming subsystem be present. The naming subsystem should expose capabilities for which other subsystems can test for the presence, so they can function in the absence of the naming subsystem. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7103) In elytron security domain add operation the realms attribute is not marked as required even though it is not nillable and has no default value with no default value

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/WFLY-7103?page=com.atlassian.jira.plugin.... ] Jan Kalina commented on WFLY-7103: ---------------------------------- Item of the list should allow null if and only if the list should not be required. Will check it. > In elytron security domain add operation the realms attribute is not marked as required even though it is not nillable and has no default value with no default value > --------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-7103 > URL: https://issues.jboss.org/browse/WFLY-7103 > Project: WildFly > Issue Type: Bug > Components: Domain Management, Security > Reporter: Radim Hatlapatka > Assignee: Jan Kalina > > When reading description of the {{add}} operation for elytron security domain => {{/subsystem=elytron/security-domain=test-domain:read-operation-description(name=add)}}, the realms attribute has set required to false. Still it needs to be defined as part of {{add}} operation as it is not nillable. > If it is really mandatory, it should be marked as required. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-338) Auto-promotion of slave HC to master

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-338?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFCORE-338: ------------------------------------ Description: Implement an option for a properly configured slave HC to promote itself to master after acquiring in some controlled manner an exclusive right to act as such. (was: Implement an option for a properly configured slave HC to promote itself to master after acquiring an exclusive lock mediated via some persistent store shared between all HCs that are possibly master.) > Auto-promotion of slave HC to master > ------------------------------------ > > Key: WFCORE-338 > URL: https://issues.jboss.org/browse/WFCORE-338 > Project: WildFly Core > Issue Type: Feature Request > Components: Domain Management > Reporter: Brian Stansberry > Assignee: Ken Wills > > Implement an option for a properly configured slave HC to promote itself to master after acquiring in some controlled manner an exclusive right to act as such. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 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 September 2016