January 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-9706) Newly added InfiniteOrPositiveValidators to messaging attributes should just print warning if negative values is not -1

by Erich Duda (JIRA)

Erich Duda created WFLY-9706: -------------------------------- Summary: Newly added InfiniteOrPositiveValidators to messaging attributes should just print warning if negative values is not -1 Key: WFLY-9706 URL: https://issues.jboss.org/browse/WFLY-9706 Project: WildFly Issue Type: Bug Components: JMS Affects Versions: 12.0.0.Alpha1 Reporter: Erich Duda Assignee: Jeff Mesnil Priority: Blocker This Jira is reaction to WFLY-9433. The WFLY-9433 makes validator rules more strict for some attributes in messaging subsystem. Although there is no reason to use these values (which are newly considered as invalid), it was possible to configure them and they worked with Wildfly 11 and previous releases. As it is proposed in JBEAP-14110, this change should be done in 2 steps: * only WARN the user if the parameter is not valid (a negative value other than -1) * in next release, reject the parameter I am setting priority as Blocker, because this fix must be included in Wildfly 12 release. It makes no sense to do it later. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3518) principal-query attribute of jdbc-realm is required but description says false

by Yeray Borges (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3518?page=com.atlassian.jira.plugi... ] Yeray Borges moved ELY-1279 to WFCORE-3518: ------------------------------------------- Project: WildFly Core (was: WildFly Elytron) Key: WFCORE-3518 (was: ELY-1279) > principal-query attribute of jdbc-realm is required but description says false > ------------------------------------------------------------------------------ > > Key: WFCORE-3518 > URL: https://issues.jboss.org/browse/WFCORE-3518 > Project: WildFly Core > Issue Type: Bug > Reporter: Claudio Miranda > Assignee: Yeray Borges > > jdbc-realm description, for principal-query attribute says it is required=false, nillable=true, but that is false, because a jdbc-realm cannot be added without a principal-query. > {code} > /profile=full/subsystem=elytron/jdbc-realm=*:read-resource-description > { > "outcome" => "success", > "result" => [{ > "address" => [ > ("profile" => "full"), > ("subsystem" => "elytron"), > ("jdbc-realm" => "*") > ], > "outcome" => "success", > "result" => { > "description" => "A security realm definition backed by database using JDBC.", > "capabilities" => [{ > "name" => "org.wildfly.security.security-realm", > "dynamic" => true > }], > "access-constraints" => { > "sensitive" => {"elytron-security" => {"type" => "elytron"}}, > "application" => {"elytron-security" => {"type" => "elytron"}} > }, > "attributes" => {"principal-query" => { > "type" => LIST, > "description" => "The authentication query used to authenticate users based on specific key types.", > "expressions-allowed" => false, > "required" => false, > "nillable" => true, > "value-type" => { > {code} > The add operation with no principal-query > {code} > /profile=full/subsystem=elytron/jdbc-realm=jdbc2:add > { > "outcome" => "failed", > "failure-description" => {"domain-failure-description" => "WFLYCTL0155: 'principal-query' may not be null"}, > "rolled-back" => true > } > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ELY-1279) principal-query attribute of jdbc-realm is required but description says false

by Yeray Borges (JIRA)

[ https://issues.jboss.org/browse/ELY-1279?page=com.atlassian.jira.plugin.s... ] Yeray Borges reassigned ELY-1279: --------------------------------- Assignee: Yeray Borges > principal-query attribute of jdbc-realm is required but description says false > ------------------------------------------------------------------------------ > > Key: ELY-1279 > URL: https://issues.jboss.org/browse/ELY-1279 > Project: WildFly Elytron > Issue Type: Bug > Reporter: Claudio Miranda > Assignee: Yeray Borges > > jdbc-realm description, for principal-query attribute says it is required=false, nillable=true, but that is false, because a jdbc-realm cannot be added without a principal-query. > {code} > /profile=full/subsystem=elytron/jdbc-realm=*:read-resource-description > { > "outcome" => "success", > "result" => [{ > "address" => [ > ("profile" => "full"), > ("subsystem" => "elytron"), > ("jdbc-realm" => "*") > ], > "outcome" => "success", > "result" => { > "description" => "A security realm definition backed by database using JDBC.", > "capabilities" => [{ > "name" => "org.wildfly.security.security-realm", > "dynamic" => true > }], > "access-constraints" => { > "sensitive" => {"elytron-security" => {"type" => "elytron"}}, > "application" => {"elytron-security" => {"type" => "elytron"}} > }, > "attributes" => {"principal-query" => { > "type" => LIST, > "description" => "The authentication query used to authenticate users based on specific key types.", > "expressions-allowed" => false, > "required" => false, > "nillable" => true, > "value-type" => { > {code} > The add operation with no principal-query > {code} > /profile=full/subsystem=elytron/jdbc-realm=jdbc2:add > { > "outcome" => "failed", > "failure-description" => {"domain-failure-description" => "WFLYCTL0155: 'principal-query' may not be null"}, > "rolled-back" => true > } > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9128) Upgrade to JAXB 2.3 / JBossWS 5.2 / CXF 3.2

by Ivo Studensky (JIRA)

[ https://issues.jboss.org/browse/WFLY-9128?page=com.atlassian.jira.plugin.... ] Ivo Studensky updated WFLY-9128: -------------------------------- Git Pull Request: https://github.com/wildfly/wildfly/pull/10604 (was: https://github.com/wildfly/wildfly/pull/10751) > Upgrade to JAXB 2.3 / JBossWS 5.2 / CXF 3.2 > ------------------------------------------- > > Key: WFLY-9128 > URL: https://issues.jboss.org/browse/WFLY-9128 > Project: WildFly > Issue Type: Component Upgrade > Components: Web Services > Reporter: Ivo Studensky > Assignee: Alessio Soldano > Labels: downstream_dependency > > Upgrade Apache CXF to 3.1.13. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9128) Upgrade Apache CXF to 3.2

by Ivo Studensky (JIRA)

[ https://issues.jboss.org/browse/WFLY-9128?page=com.atlassian.jira.plugin.... ] Ivo Studensky updated WFLY-9128: -------------------------------- Summary: Upgrade Apache CXF to 3.2 (was: Upgrade Apache CXF to 3.1.13) > Upgrade Apache CXF to 3.2 > ------------------------- > > Key: WFLY-9128 > URL: https://issues.jboss.org/browse/WFLY-9128 > Project: WildFly > Issue Type: Component Upgrade > Components: Web Services > Reporter: Ivo Studensky > Assignee: Alessio Soldano > Labels: downstream_dependency > > Upgrade Apache CXF to 3.1.13. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9128) Upgrade to JAXB 2.3 / JBossWS 5.2 / CXF 3.2

by Ivo Studensky (JIRA)

[ https://issues.jboss.org/browse/WFLY-9128?page=com.atlassian.jira.plugin.... ] Ivo Studensky updated WFLY-9128: -------------------------------- Summary: Upgrade to JAXB 2.3 / JBossWS 5.2 / CXF 3.2 (was: Upgrade Apache CXF to 3.2) > Upgrade to JAXB 2.3 / JBossWS 5.2 / CXF 3.2 > ------------------------------------------- > > Key: WFLY-9128 > URL: https://issues.jboss.org/browse/WFLY-9128 > Project: WildFly > Issue Type: Component Upgrade > Components: Web Services > Reporter: Ivo Studensky > Assignee: Alessio Soldano > Labels: downstream_dependency > > Upgrade Apache CXF to 3.1.13. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6661) Bean level lock type not applied

by Yeray Borges (JIRA)

[ https://issues.jboss.org/browse/WFLY-6661?page=com.atlassian.jira.plugin.... ] Yeray Borges resolved WFLY-6661. -------------------------------- Fix Version/s: 12.0.0.Alpha1 Resolution: Duplicate Issue > Bean level lock type not applied > -------------------------------- > > Key: WFLY-6661 > URL: https://issues.jboss.org/browse/WFLY-6661 > Project: WildFly > Issue Type: Bug > Components: EJB > Affects Versions: 10.0.0.Final > Reporter: Keio Kraaner > Fix For: 12.0.0.Alpha1 > > > A singleton EJB has @Lock(LockType.READ) annotation declared on the class level. > The bean is accessed using a local (defined by @Local annotation) or remote (defined by @Remote annotation) EJB interface. > SingletonComponent::getLockType returns wrong value (LockType.WRITE) because the beanLevelLockType map does not contain a key equal to the local or remote interface class name. It contains a key equal to the EJB class name that implements those interfaces. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9272) Support clustered CDI events

by Matej Novotny (JIRA)

[ https://issues.jboss.org/browse/WFLY-9272?page=com.atlassian.jira.plugin.... ] Matej Novotny commented on WFLY-9272: ------------------------------------- If case you need a hand from Weld-side of things while implementing this, me or [~mkouba] can help out. > Support clustered CDI events > ---------------------------- > > Key: WFLY-9272 > URL: https://issues.jboss.org/browse/WFLY-9272 > Project: WildFly > Issue Type: Feature Request > Components: CDI / Weld, Clustering > Affects Versions: 10.1.0.Final > Reporter: Giovanni Lovato > Assignee: Radoslav Husar > > When an EAR is deployed on a server group in full-ha profile, CDI events ({{javax.enterprise.event.Event}}) fired from a node are notified only to observer threads in the same node. > This limits the use of CDI events in distributed application, when events fired by users balanced on one node are missed by users balanced on other nodes. > In Payara this is already possibile for {{Serializable}} paylaods using annotations (see https://payara.gitbooks.io/payara-server/content/documentation/extended-d...). > It would be really useful to have this in WildFly too. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2244) Use of TP.internal_pool can result in classloader leaks

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-2244?page=com.atlassian.jira.plugin.... ] Bela Ban updated JGRP-2244: --------------------------- Fix Version/s: 4.0.10 > Use of TP.internal_pool can result in classloader leaks > ------------------------------------------------------- > > Key: JGRP-2244 > URL: https://issues.jboss.org/browse/JGRP-2244 > Project: JGroups > Issue Type: Bug > Affects Versions: 4.0 > Reporter: Paul Ferraro > Assignee: Bela Ban > Fix For: 4.0.10 > > > As of JGroups 4.0, the ThreadFactory of the internal thread pool cannot be overridden. Consequently, there is no mechanism to associate newly spawned threads with a specific classloader. If an application thread results in the spawning of an thread in this internal pool [1], the application class loader can leak to other threads used the the JGroups channel. > [1] https://github.com/belaban/JGroups/blob/master/src/org/jgroups/protocols/... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3517) Remove unnecessary Attribute and Element enums from JXM subsystem

by Stuart Douglas (JIRA)

Stuart Douglas created WFCORE-3517: -------------------------------------- Summary: Remove unnecessary Attribute and Element enums from JXM subsystem Key: WFCORE-3517 URL: https://issues.jboss.org/browse/WFCORE-3517 Project: WildFly Core Issue Type: Task Components: JMX Reporter: Stuart Douglas Assignee: Stuart Douglas Priority: Minor -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 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 January 2018