July 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-6876) Unessesary allocation in JACCContextIdHandler

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-6876?page=com.atlassian.jira.plugin.... ] Brian Stansberry reassigned WFLY-6876: -------------------------------------- Fix Version/s: 10.1.0.CR1 Assignee: Stuart Douglas (was: Jason Greene) Resolution: Done > Unessesary allocation in JACCContextIdHandler > --------------------------------------------- > > Key: WFLY-6876 > URL: https://issues.jboss.org/browse/WFLY-6876 > Project: WildFly > Issue Type: Bug > Reporter: Stuart Douglas > Assignee: Stuart Douglas > Fix For: 10.1.0.CR1 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6879) Parsing logic in EJB3Subsystem30Parser#parseRemotingReceiver ignores unparseable attributes instead of throwing an exception

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-6879?page=com.atlassian.jira.plugin.... ] Radoslav Husar updated WFLY-6879: --------------------------------- Summary: Parsing logic in EJB3Subsystem30Parser#parseRemotingReceiver ignores unparseable attributes instead of throwing an exception (was: Parsing logic for EJB3Subsystem30Parser#parseRemotingReceiver ignores erroneous attributes instead of throwing exception) > Parsing logic in EJB3Subsystem30Parser#parseRemotingReceiver ignores unparseable attributes instead of throwing an exception > ---------------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-6879 > URL: https://issues.jboss.org/browse/WFLY-6879 > Project: WildFly > Issue Type: Bug > Components: EJB > Affects Versions: 10.0.0.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Fix For: 10.1.0.CR1 > > > We do throw exception when unparseable data is found. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6879) Parsing logic in EJB3Subsystem30Parser#parseRemotingReceiver ignores unparseable attributes instead of exception

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-6879?page=com.atlassian.jira.plugin.... ] Radoslav Husar updated WFLY-6879: --------------------------------- Summary: Parsing logic in EJB3Subsystem30Parser#parseRemotingReceiver ignores unparseable attributes instead of exception (was: Parsing logic in EJB3Subsystem30Parser#parseRemotingReceiver ignores unparseable attributes instead of throwing an exception) > Parsing logic in EJB3Subsystem30Parser#parseRemotingReceiver ignores unparseable attributes instead of exception > ---------------------------------------------------------------------------------------------------------------- > > Key: WFLY-6879 > URL: https://issues.jboss.org/browse/WFLY-6879 > Project: WildFly > Issue Type: Bug > Components: EJB > Affects Versions: 10.0.0.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Fix For: 10.1.0.CR1 > > > We do throw exception when unparseable data is found. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6879) Parsing logic for EJB3Subsystem30Parser#parseRemotingReceiver ignores erroneous attributes instead of throwing exception

by Radoslav Husar (JIRA)

Radoslav Husar created WFLY-6879: ------------------------------------ Summary: Parsing logic for EJB3Subsystem30Parser#parseRemotingReceiver ignores erroneous attributes instead of throwing exception Key: WFLY-6879 URL: https://issues.jboss.org/browse/WFLY-6879 Project: WildFly Issue Type: Feature Request Components: EJB Affects Versions: 10.0.0.Final Reporter: Radoslav Husar Assignee: Radoslav Husar Fix For: 10.1.0.CR1 We do throw exception when unparseable data is found. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6879) Parsing logic for EJB3Subsystem30Parser#parseRemotingReceiver ignores erroneous attributes instead of throwing exception

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-6879?page=com.atlassian.jira.plugin.... ] Radoslav Husar updated WFLY-6879: --------------------------------- Issue Type: Bug (was: Feature Request) > Parsing logic for EJB3Subsystem30Parser#parseRemotingReceiver ignores erroneous attributes instead of throwing exception > ------------------------------------------------------------------------------------------------------------------------ > > Key: WFLY-6879 > URL: https://issues.jboss.org/browse/WFLY-6879 > Project: WildFly > Issue Type: Bug > Components: EJB > Affects Versions: 10.0.0.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Fix For: 10.1.0.CR1 > > > We do throw exception when unparseable data is found. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6778) Each Undertow server should expose a distinct SessionIdentifierCodec

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-6778?page=com.atlassian.jira.plugin.... ] Radoslav Husar updated WFLY-6778: --------------------------------- Fix Version/s: 11.0.0.Alpha1 > Each Undertow server should expose a distinct SessionIdentifierCodec > -------------------------------------------------------------------- > > Key: WFLY-6778 > URL: https://issues.jboss.org/browse/WFLY-6778 > Project: WildFly > Issue Type: Bug > Components: Clustering, Web (Undertow) > Affects Versions: 10.0.0.Final > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Fix For: 11.0.0.Alpha1 > > > Undertow exposes a single instance-id for the whole subsystem. This id is used by a load balancer to uniquely identify the node among other nodes in the load balancing group. However, this granularity is not correct. > Undertow can define multiple servers, each with a unique set of listeners. From the perspective of the load balancer, these servers are distinct and thus must use distinct names. Thus, rather than installing a single SessionIdentifierCodec for the subsystem, we should install one instance per server. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1640) Intermittent failure in DeploymentScannerUnitTestCase

by ehsavoie Hugonnet (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1640?page=com.atlassian.jira.plugi... ] ehsavoie Hugonnet commented on WFCORE-1640: ------------------------------------------- This seems related to not closing the controller client when restarting the server. > Intermittent failure in DeploymentScannerUnitTestCase > ----------------------------------------------------- > > Key: WFCORE-1640 > URL: https://issues.jboss.org/browse/WFCORE-1640 > Project: WildFly Core > Issue Type: Bug > Components: Deployment Scanner, Test Suite > Affects Versions: 2.2.0.CR5 > Reporter: Brian Stansberry > Assignee: ehsavoie Hugonnet > > DeploymentScannerUnitTestCase.testStartup() has been failing intermittently since May: > https://ci.wildfly.org/project.html?projectId=WildFlyCore&buildTypeId=&ta... > The May 4 failure is the first that was not associated with some large scale failure; i.e. is more likely to be relevant to the test itself. > I'll send up a PR to @Ignore this test. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ELY-599) Add support for mechanism properties in client side configuration.

by Darran Lofthouse (JIRA)

Darran Lofthouse created ELY-599: ------------------------------------ Summary: Add support for mechanism properties in client side configuration. Key: ELY-599 URL: https://issues.jboss.org/browse/ELY-599 Project: WildFly Elytron Issue Type: Enhancement Components: Authentication Client Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 1.1.0.Beta7 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ELY-598) Rename use-mechanism-realm to set-mechanism-realm in schema

by Darran Lofthouse (JIRA)

Darran Lofthouse created ELY-598: ------------------------------------ Summary: Rename use-mechanism-realm to set-mechanism-realm in schema Key: ELY-598 URL: https://issues.jboss.org/browse/ELY-598 Project: WildFly Elytron Issue Type: Task Components: Authentication Client Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 1.1.0.Beta7 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1670) Upgrade to JBoss DMR 1.4.0.Beta1

by Brian Stansberry (JIRA)

Brian Stansberry created WFCORE-1670: ---------------------------------------- Summary: Upgrade to JBoss DMR 1.4.0.Beta1 Key: WFCORE-1670 URL: https://issues.jboss.org/browse/WFCORE-1670 Project: WildFly Core Issue Type: Component Upgrade Components: Domain Management Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: 3.0.0.Alpha4 Pick up DMR-9. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

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