March 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (ELY-988) Methods 'replacing' and 'replacingSslContext' in AuthenticationContext work incorrectly

by Ondrej Lukas (JIRA)

Ondrej Lukas created ELY-988: -------------------------------- Summary: Methods 'replacing' and 'replacingSslContext' in AuthenticationContext work incorrectly Key: ELY-988 URL: https://issues.jboss.org/browse/ELY-988 Project: WildFly Elytron Issue Type: Bug Reporter: Ondrej Lukas Assignee: Darran Lofthouse Priority: Critical According to their javadoc, these methods should replace the rule and configuration (or SSL context) at the given index with the given rule and configuration. In case when AuthenticationContext is defined with RuleNode - RuleA, RuleB, RuleC and RuleNode {{replacing}} method is called for index1 and RuleD, then: * correct behavior should be - new AuthenticationContext with rule ordered - RuleA, RuleD, RuleC is created * current behavior is - new AuthenticationContext with rule ordered - RuleD, RuleD, RuleB RuleC is created Behavior of these methods is correct only in case when they are called with index 0. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1461) In operator doesn't work with variable

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1461?page=com.atlassian.jira.plugi... ] Mario Fusco resolved DROOLS-1461. --------------------------------- Resolution: Rejected > In operator doesn't work with variable > -------------------------------------- > > Key: DROOLS-1461 > URL: https://issues.jboss.org/browse/DROOLS-1461 > Project: Drools > Issue Type: Bug > Components: core engine > Reporter: Anton Giertli > Assignee: Mario Fusco > Attachments: operators.zip, screenshot-1.png > > > This works just fine: > {code:java} > rule "checkFirstName" > dialect "mvel" > when > Message( message in ( "anton","giertli") ) > then > System.out.println("LHS OK"); > end > {code} > But rule like this, won't fire: > {code:java} > global java.util.List $myGlobal; > rule "checkFirstName" > dialect "mvel" > when > Message( message in ( $myGlobal) ) > then > System.out.println("LHS OK"); > end > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1461) In operator doesn't work with variable

by Matteo Mortari (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1461?page=com.atlassian.jira.plugi... ] Matteo Mortari commented on DROOLS-1461: ---------------------------------------- I'm also voting for close/reject this issue, as the second rule in the description has a different semantic than what intended by the reporter, I think. The second rule semantic means, check {{message}} is contained {{in}} the elements within the round parenthesis. Now the message property (String) is NOT contained in the set of elements contaning 1 element, the global {{$myGlobal}} which is in itself a list. In other words and pseudocode it's checking if: {code:java} "anton" ⊆ { ["anton", "giertli"] } {code} which is false. Please notice the set on the right (marked by the { } parenthesis) contains 1 element, the list represented by the [ ] parenthesis ---- This can be demonstrated also by changing the test for message to contain an arbitrary Object, as: !screenshot-1.png|thumbnail! which would realize the check {code:java} ["anton", "giertli"] ⊆ { ["anton", "giertli"] } {code} which is then true, and making {{testInOperator()}} pass. ---- Please notice only the *_first_* rule in the description is doing semantically what I expect is actually desired by the reporter which is: {code:java} "anton" ⊆ { "anton", "giertli" } {code} (you can notice now the set on the right marked by the { } parenthesis contains 2 elements) > In operator doesn't work with variable > -------------------------------------- > > Key: DROOLS-1461 > URL: https://issues.jboss.org/browse/DROOLS-1461 > Project: Drools > Issue Type: Bug > Components: core engine > Reporter: Anton Giertli > Assignee: Mario Fusco > Attachments: operators.zip, screenshot-1.png > > > This works just fine: > {code:java} > rule "checkFirstName" > dialect "mvel" > when > Message( message in ( "anton","giertli") ) > then > System.out.println("LHS OK"); > end > {code} > But rule like this, won't fire: > {code:java} > global java.util.List $myGlobal; > rule "checkFirstName" > dialect "mvel" > when > Message( message in ( $myGlobal) ) > then > System.out.println("LHS OK"); > end > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1461) In operator doesn't work with variable

by Matteo Mortari (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1461?page=com.atlassian.jira.plugi... ] Matteo Mortari updated DROOLS-1461: ----------------------------------- Attachment: screenshot-1.png > In operator doesn't work with variable > -------------------------------------- > > Key: DROOLS-1461 > URL: https://issues.jboss.org/browse/DROOLS-1461 > Project: Drools > Issue Type: Bug > Components: core engine > Reporter: Anton Giertli > Assignee: Mario Fusco > Attachments: operators.zip, screenshot-1.png > > > This works just fine: > {code:java} > rule "checkFirstName" > dialect "mvel" > when > Message( message in ( "anton","giertli") ) > then > System.out.println("LHS OK"); > end > {code} > But rule like this, won't fire: > {code:java} > global java.util.List $myGlobal; > rule "checkFirstName" > dialect "mvel" > when > Message( message in ( $myGlobal) ) > then > System.out.println("LHS OK"); > end > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2352) Migrate the WildFly Elytron subsystem to WildFly Core

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2352?page=com.atlassian.jira.plugi... ] Darran Lofthouse updated WFCORE-2352: ------------------------------------- Priority: Critical (was: Major) > Migrate the WildFly Elytron subsystem to WildFly Core > ----------------------------------------------------- > > Key: WFCORE-2352 > URL: https://issues.jboss.org/browse/WFCORE-2352 > Project: WildFly Core > Issue Type: Task > Components: Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Critical > Fix For: 3.0.0.Beta7 > > > This task is to move the subsystem to WildFly Core. This task is not to add the subsystem to any additional feature packs. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (HAWKULARQE-55) CFME Tests: Adjust environment and smoke tests to JMAN4-111

by Hayk Hovsepyan (JIRA)

Hayk Hovsepyan created HAWKULARQE-55: ---------------------------------------- Summary: CFME Tests: Adjust environment and smoke tests to JMAN4-111 Key: HAWKULARQE-55 URL: https://issues.jboss.org/browse/HAWKULARQE-55 Project: Hawkular QE Issue Type: Task Reporter: Hayk Hovsepyan Assignee: Hayk Hovsepyan Priority: Blocker Once [JMAN4-111|https://issues.jboss.org/browse/JMAN4-111] feature is done, EAP servers on Containers will become immutable, but our CFME Testing environment runs on Containers. * switch EAP7 Containers to VMs * and for container EAP7 make smoke tests -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2358) deployment-overlay link action help is not accurate

by Jean-Francois Denise (JIRA)

Jean-Francois Denise created WFCORE-2358: -------------------------------------------- Summary: deployment-overlay link action help is not accurate Key: WFCORE-2358 URL: https://issues.jboss.org/browse/WFCORE-2358 Project: WildFly Core Issue Type: Bug Components: CLI Reporter: Jean-Francois Denise Assignee: Jean-Francois Denise Priority: Minor Deployment can be created after being linked to the overlay. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (HAWKULARQE-54) JDG integration into CFME

by Hayk Hovsepyan (JIRA)

Hayk Hovsepyan created HAWKULARQE-54: ---------------------------------------- Summary: JDG integration into CFME Key: HAWKULARQE-54 URL: https://issues.jboss.org/browse/HAWKULARQE-54 Project: Hawkular QE Issue Type: Task Environment: From Heiko's status email 02/02. Reporter: Hayk Hovsepyan Assignee: Hayk Hovsepyan Currently work is in progress for MiQ upstream. Further information about including in downstream later. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8160) Webservice response File Descriptor leak

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-8160?page=com.atlassian.jira.plugin.... ] Tomaz Cerar commented on WFLY-8160: ----------------------------------- Could you provide file leak track with help of http://file-leak-detector.kohsuke.org/ This will provide you with list of stacktraces where the file leaks are occuring and please paste that back here. > Webservice response File Descriptor leak > ---------------------------------------- > > Key: WFLY-8160 > URL: https://issues.jboss.org/browse/WFLY-8160 > Project: WildFly > Issue Type: Bug > Components: Web Services > Affects Versions: 9.0.0.Final, 9.0.2.Final, 10.1.0.Final > Environment: JDK: jdk1.8.0_121, jdk1.8.0_66 > WilfFly : wildfly-10.1.0.Final, wildfly-9.0.2.Final , wildfly-9.0.0.Final > OS: Red Hat Enterprise Linux Server release 7.1 (Maipo) > Hardware: 64 bit 4 core > Reporter: Mahesh Reddy > Assignee: Alessio Soldano > Priority: Blocker > Attachments: BioMatcherWebserviceImpl.java, SOAP_REQUEST.txt, SOAP_RESPONSE.txt > > > We are getting File descriptor leak when wildfly responds to webservice call. > I think this happens if the webresvice response is huge complex structure, > I confirmed by adding the sleep just before the returning from the webservice method and checking lsof -p <pid>, And again checking it after client receives the response,. > I notice for each webservice call, 2 file descriptors are open and never closed. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8160) Webservice response File Descriptor leak

by Jim Ma (JIRA)

[ https://issues.jboss.org/browse/WFLY-8160?page=com.atlassian.jira.plugin.... ] Jim Ma commented on WFLY-8160: ------------------------------ Hi [~maheshvizag], Can you please provide the other classes/test project that we can reproduce this issue locally ? What is your client code ? > Webservice response File Descriptor leak > ---------------------------------------- > > Key: WFLY-8160 > URL: https://issues.jboss.org/browse/WFLY-8160 > Project: WildFly > Issue Type: Bug > Components: Web Services > Affects Versions: 9.0.0.Final, 9.0.2.Final, 10.1.0.Final > Environment: JDK: jdk1.8.0_121, jdk1.8.0_66 > WilfFly : wildfly-10.1.0.Final, wildfly-9.0.2.Final , wildfly-9.0.0.Final > OS: Red Hat Enterprise Linux Server release 7.1 (Maipo) > Hardware: 64 bit 4 core > Reporter: Mahesh Reddy > Assignee: Alessio Soldano > Priority: Blocker > Attachments: BioMatcherWebserviceImpl.java, SOAP_REQUEST.txt, SOAP_RESPONSE.txt > > > We are getting File descriptor leak when wildfly responds to webservice call. > I think this happens if the webresvice response is huge complex structure, > I confirmed by adding the sleep just before the returning from the webservice method and checking lsof -p <pid>, And again checking it after client receives the response,. > I notice for each webservice call, 2 file descriptors are open and never closed. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira March 2017