March 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-3696) Upgrade WildFly Elytron Tool to 1.1.4.Final

by Kabir Khan (JIRA)

Kabir Khan created WFCORE-3696: ---------------------------------- Summary: Upgrade WildFly Elytron Tool to 1.1.4.Final Key: WFCORE-3696 URL: https://issues.jboss.org/browse/WFCORE-3696 Project: WildFly Core Issue Type: Component Upgrade Components: Security Reporter: Farah Juma Assignee: Farah Juma Fix For: 5.0.0.Alpha1 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-3697) Upgrade WildFly Elytron to 1.2.4.Final

by Kabir Khan (JIRA)

Kabir Khan created WFCORE-3697: ---------------------------------- Summary: Upgrade WildFly Elytron to 1.2.4.Final Key: WFCORE-3697 URL: https://issues.jboss.org/browse/WFCORE-3697 Project: WildFly Core Issue Type: Component Upgrade Components: Security Reporter: Farah Juma Assignee: Farah Juma Fix For: 5.0.0.Alpha1 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-10046) Cannot create cluster with JGroups Gossip router

by Miroslav Novak (JIRA)

[ https://issues.jboss.org/browse/WFLY-10046?page=com.atlassian.jira.plugin... ] Miroslav Novak commented on WFLY-10046: --------------------------------------- [~pferraro] There are no error/warn/info logs which would indicated what went wrong. I've added steps to reproduce. The same config works in EAP 7.1 thus this should be considered as regression. > Cannot create cluster with JGroups Gossip router > ------------------------------------------------ > > Key: WFLY-10046 > URL: https://issues.jboss.org/browse/WFLY-10046 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 12.0.0.Final > Reporter: Miroslav Novak > Assignee: Paul Ferraro > Attachments: standalone-full-ha-gosship1.xml, standalone-full-ha-gosship2.xml > > > I've used config from EAP 7.1.0/WF11 where gossip router was configured in udp stack like: > {code} > <stack name="udp"> > <transport type="UDP" shared="false" socket-binding="jgroups-udp"/> > <protocol type="PING"/> > <protocol type="MERGE3"/> > <protocol type="FD_SOCK"/> > <protocol type="FD_ALL"/> > <protocol type="VERIFY_SUSPECT"/> > <protocol type="pbcast.NAKACK2"/> > <protocol type="UNICAST3"/> > <protocol type="pbcast.STABLE"/> > <protocol type="pbcast.GMS"/> > <protocol type="UFC"/> > <protocol type="MFC"/> > <protocol type="FRAG2"/> > <protocol type="TUNNEL"> > <property name="gossip_router_hosts"> > 0.0.0.0[12001] > </property> > </protocol> > </stack> > {code} > Gossip router was started on localhost: > {{java -cp $JBOSS_HOME//bin/client/jboss-client.jar org.jgroups.stack.GossipRouter -port 12001 -bindaddress 0.0.0.0}} > but cluster does not form up. The same configuration works in EAP 7.1. > Attaching xml config files for both of the servers. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-2400) ComparePairTest test fails on newer IBM JDK

by Tibor Zimányi (JIRA)

Tibor Zimányi created DROOLS-2400: ------------------------------------- Summary: ComparePairTest test fails on newer IBM JDK Key: DROOLS-2400 URL: https://issues.jboss.org/browse/DROOLS-2400 Project: Drools Issue Type: Bug Components: core engine Affects Versions: 7.6.0.Final Reporter: Tibor Zimányi Assignee: Tibor Zimányi Priority: Minor When running test ComparePairTest on newer versions of IBM JDK, it fails on: java.lang.AssertionError: Different collection values on ArrayList at org.junit.Assert.fail(Assert.java:88) at org.junit.Assert.assertTrue(Assert.java:41) at org.kie.test.util.compare.ComparePair.compareValues(ComparePair.java:292) at... It is caused by String class from IBM JDK containing field that is null. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-1663) Kie DMN doesn't support IMPORT decisions between DMN files

by Matteo Mortari (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1663?page=com.atlassian.jira.plugi... ] Matteo Mortari reassigned DROOLS-1663: -------------------------------------- Assignee: Matteo Mortari (was: Edson Tirelli) > Kie DMN doesn't support IMPORT decisions between DMN files > ---------------------------------------------------------- > > Key: DROOLS-1663 > URL: https://issues.jboss.org/browse/DROOLS-1663 > Project: Drools > Issue Type: Enhancement > Components: dmn engine > Reporter: Stylianos Koussouris > Assignee: Matteo Mortari > Attachments: IMG_2197.jpg, IMG_2198.jpg, IMG_2199.jpg > > > DMN Spec 1.1 > Page 40. > import: Import [*] This attribute is used to import externally defined elements and > make them available for use by elements in this Definitions. > Section 6.3.3 Import metamodel > The aim here is to be able to import one Decision defined in a separate DMN into another where it is used as a supporting decision and is referenced (RequiredDecision) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-3382) Further Enhance Elytron Permission Configuration

by Jeff Mesnil (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3382?page=com.atlassian.jira.plugi... ] Jeff Mesnil updated WFCORE-3382: -------------------------------- Fix Version/s: 5.0.0.Alpha2 (was: 5.0.0.Alpha1) > Further Enhance Elytron Permission Configuration > ------------------------------------------------ > > Key: WFCORE-3382 > URL: https://issues.jboss.org/browse/WFCORE-3382 > Project: WildFly Core > Issue Type: Feature Request > Components: Security > Reporter: Darran Lofthouse > Priority: Blocker > Fix For: 5.0.0.Alpha2 > > > This has currently been simplified to a single resource for the out of the box configuration, however this brings issues as now permissions are duplicated so modifications need to be replicated instead of to a single location. > Finding a way for the default required permissions to be defined in one location could help eliminate the duplication. > We could also consider going one step further and subsystems register the default permissions that should be granted. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-2930) Support a socket-binding-group as a child of profile

by Jeff Mesnil (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2930?page=com.atlassian.jira.plugi... ] Jeff Mesnil updated WFCORE-2930: -------------------------------- Fix Version/s: 5.0.0.Alpha2 (was: 5.0.0.Alpha1) > Support a socket-binding-group as a child of profile > ---------------------------------------------------- > > Key: WFCORE-2930 > URL: https://issues.jboss.org/browse/WFCORE-2930 > Project: WildFly Core > Issue Type: Feature Request > Components: Domain Management > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Priority: Critical > Fix For: 5.0.0.Alpha2 > > > Allow a single socket-binding-group resource as a child of profile, such that resolution of bindings from the subsystems are limited to the s-b-g associated with the profile. > A server-group that uses such a profile cannot reference a socket-binding-group. And a server in that server-group cannot reference an s-b-g to override the one from the server-group/profile. > I'm not sure how the s-b-g resource will work. Perhaps the resource would go away under 'profile' with the bindings direct children of profile. The 'default-interface' attribute then becomes an attribute of profile. Or perhaps there will be an s-b-g resource, but with a fixed name that's the same as the profile. Currently I think the latter. > This will be necessary for resolution of config elements using the upcoming provisioning tool. The tool will not be able to do correct "feature" resolution using the complex rules we currently support. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-1649) RBAC constraint config modifications will fail in a mixed domain if the modified constraint is not present in the legacy slave

by Jeff Mesnil (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1649?page=com.atlassian.jira.plugi... ] Jeff Mesnil updated WFCORE-1649: -------------------------------- Fix Version/s: 5.0.0.Alpha2 (was: 5.0.0.Alpha1) > RBAC constraint config modifications will fail in a mixed domain if the modified constraint is not present in the legacy slave > ------------------------------------------------------------------------------------------------------------------------------ > > Key: WFCORE-1649 > URL: https://issues.jboss.org/browse/WFCORE-1649 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Priority: Critical > Labels: domain-mode > Fix For: 5.0.0.Alpha2 > > > The management model for RBAC constraints is maintained using synthetic resources, with resources only existing for those items (SensitivityClassification and ApplicationClassification) that are registered in the current process. Operations that touch classifications unknown to that process will fail due to missing resource problems. > This is a big problem in the following scenarios: > 1) Mixed domain, where legacy slaves do not know about newly introduced classifications. > 2) Slimming scenarios where slaves are ignoring unrelated parts of the domain wide config and also don't have some extension installed, resulting in classifications registered by those extensions not being present. > A partial workaround to 1) is for the kernel to register transformers for newly introduced classifications (e.g. SERVER_SSL added in EAP 6.4.7 and EAP 7). But: > -- that doesn't help with problem 2) > -- only the kernel can register kernel transformers, so if extensions add new classifications there is no way for them to register the transformer. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-10047) OOM caused by jgroups objects UNICAST3$SenderEntry#1

by Paul Ferraro (JIRA)

[ https://issues.jboss.org/browse/WFLY-10047?page=com.atlassian.jira.plugin... ] Paul Ferraro commented on WFLY-10047: ------------------------------------- [~eduda] I would suggest rebasing this branch against the latest in master. There were a number of clustering related fixes made in the past week which may impact this test. > OOM caused by jgroups objects UNICAST3$SenderEntry#1 > ---------------------------------------------------- > > Key: WFLY-10047 > URL: https://issues.jboss.org/browse/WFLY-10047 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 13.0.0.Beta1 > Reporter: Erich Duda > Assignee: Paul Ferraro > Priority: Blocker > Attachments: heapdump.png > > > JGroups objects UNICAST3$SenderEntry#1 caused OOM on Wildfly server during the boot. See attached picture. !heapdump.png|thumbnail! > *User impact:* If users use JGroups for clustering, the server may get OOM what can cause undefined behavior. > The *blocker* priority was set, because this is regression against previous versions of Wildfly and the OOM is serious error which prevents server to work properly. > The issue was hit in following scenario. > # start two servers (nodes) in cluster with one queue > # producer starts to send messages to queue to node-1 > # node-2 is killed and restarted during sending messages <---- *Here the test failed, when the node-2 was started after that it had been killed.* > # start consumer on node-2 which reads messages from queue > # servers are stopped > The Wildfly was built from following source code: > repo: https://github.com/jmesnil/wildfly > branch: WFLY-9407_upgrade_artemis_2.5.0 > commit SHA: 06c878a313d3cad323889d017e60fd5533204d1a > JGroups version: 4.0.10.Final -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-10048) Deploying of malformed MDB should fail

by Romain Pelisse (JIRA)

Romain Pelisse created WFLY-10048: ------------------------------------- Summary: Deploying of malformed MDB should fail Key: WFLY-10048 URL: https://issues.jboss.org/browse/WFLY-10048 Project: WildFly Issue Type: Bug Components: EJB Affects Versions: 12.0.0.Final Reporter: Romain Pelisse Assignee: Romain Pelisse When a deployment containing malformed MDB is deployed to EAP server, the deploy operation passes. There should be a check at deploy time that MDBs meet all requirements and if there are some issues, the deploy operation should fail. Examples of malformed MDBs: class is marked as final onMessage method is marked as final -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

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 March 2018