October 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-1775) JDK 9 on drools DMN: JavaBackendTypeTest.testPerson fails on ConcurrentModificationException

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1775?page=com.atlassian.jira.plugi... ] Mario Fusco commented on DROOLS-1775: ------------------------------------- [~tari_manga] [~tzimanyi] [~tirelli] After this fix https://github.com/kiegroup/drools/commit/7fa9700566ce9d197644435d8a66521... I ran the whole test suite with jdk9 on my machine and all drools tests was green. I suspect that the former fix also solve this problem, but I never reproduced it so I cannot be sure. Please check it again. > JDK 9 on drools DMN: JavaBackendTypeTest.testPerson fails on ConcurrentModificationException > -------------------------------------------------------------------------------------------- > > Key: DROOLS-1775 > URL: https://issues.jboss.org/browse/DROOLS-1775 > Project: Drools > Issue Type: Bug > Components: dmn engine > Affects Versions: 7.4.1.Final > Reporter: Tibor Zimányi > Assignee: Matteo Mortari > > When test JavaBackendTypeTest.testPerson from kie-dmn-feel module is run on JDK 9, it fails on ConcurrentModificationException with the following stacktrace [1]. > [1] https://gist.github.com/baldimir/d19c772ae170546047bd4f9fa6c80dd6 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1774) JDK 9 with drools: Drools persistence tests fail on ClassNotFoundException: JAXBException

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1774?page=com.atlassian.jira.plugi... ] Mario Fusco reassigned DROOLS-1774: ----------------------------------- Assignee: Mario Fusco (was: Petr Široký) > JDK 9 with drools: Drools persistence tests fail on ClassNotFoundException: JAXBException > ------------------------------------------------------------------------------------------ > > Key: DROOLS-1774 > URL: https://issues.jboss.org/browse/DROOLS-1774 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 7.4.1.Final > Reporter: Tibor Zimányi > Assignee: Mario Fusco > > When tests from drools-persistence-jpa module are run with JDK 9, the tests fail with this stacktrace [1]. It is probably due to xml apis not being part of default Java 9 modules. > To see all failing test in the persistence module, please see this spreadsheet [2]. > [1] https://gist.github.com/baldimir/76bff4a7a5ad3786f865cc7d0eb59efe > [2] https://docs.google.com/a/redhat.com/spreadsheets/d/1acFYb9utXhHb3KU2t3Fn... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1773) JDK 9 with drools: Trait tests fail on invokespecial codes

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1773?page=com.atlassian.jira.plugi... ] Mario Fusco updated DROOLS-1773: -------------------------------- Sprint: 2017 Week 43-44 > JDK 9 with drools: Trait tests fail on invokespecial codes > ---------------------------------------------------------- > > Key: DROOLS-1773 > URL: https://issues.jboss.org/browse/DROOLS-1773 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 7.4.1.Final > Reporter: Tibor Zimányi > Assignee: Mario Fusco > > When Drools trait tests tests are executed with JDK 9, some of them fail with errors related to invokespecial codes with similar stacktrace to this [1]. Please see the linked spreadsheet [2] for more information. The spreadsheet contains JDK 9 fails also from other areas. > [1] https://gist.github.com/baldimir/9972c37fe1a1af09bfa0a1605c611306 > [2] https://docs.google.com/a/redhat.com/spreadsheets/d/1acFYb9utXhHb3KU2t3Fn... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1773) JDK 9 with drools: Trait tests fail on invokespecial codes

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1773?page=com.atlassian.jira.plugi... ] Mario Fusco resolved DROOLS-1773. --------------------------------- Resolution: Done Fixed by https://github.com/kiegroup/drools/commit/7fa9700566ce9d197644435d8a66521... > JDK 9 with drools: Trait tests fail on invokespecial codes > ---------------------------------------------------------- > > Key: DROOLS-1773 > URL: https://issues.jboss.org/browse/DROOLS-1773 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 7.4.1.Final > Reporter: Tibor Zimányi > Assignee: Mario Fusco > > When Drools trait tests tests are executed with JDK 9, some of them fail with errors related to invokespecial codes with similar stacktrace to this [1]. Please see the linked spreadsheet [2] for more information. The spreadsheet contains JDK 9 fails also from other areas. > [1] https://gist.github.com/baldimir/9972c37fe1a1af09bfa0a1605c611306 > [2] https://docs.google.com/a/redhat.com/spreadsheets/d/1acFYb9utXhHb3KU2t3Fn... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9506) [GSS](7.1.0) use of WildFlyInitialContext with wildfly-config.xml throws javax.naming.NoInitialContextException

by Jiri Ondrusek (JIRA)

Jiri Ondrusek created WFLY-9506: ----------------------------------- Summary: [GSS](7.1.0) use of WildFlyInitialContext with wildfly-config.xml throws javax.naming.NoInitialContextException Key: WFLY-9506 URL: https://issues.jboss.org/browse/WFLY-9506 Project: WildFly Issue Type: Bug Components: EJB, Naming Affects Versions: 12.0.0.Alpha1 Environment: 7.1.0.Beta and 7.1.0.ER2 Reporter: Jiri Ondrusek Assignee: Jiri Ondrusek If a client use WildFlyInitialContext without properties the following Exception is thrown: Exception in thread "main" javax.naming.NoInitialContextException at org.wildfly.naming.client.WildFlyInitialContext.getDefaultInitCtx(WildFlyInitialContext.java:65) at javax.naming.InitialContext.getURLOrDefaultInitCtx(InitialContext.java:350) at javax.naming.InitialContext.lookup(InitialContext.java:417) at org.jboss.wfink.eap71.playground.wildfly.client.WildFlyICConfigClient.main(WildFlyICConfigClient.java:33) It is expected that this works according to https://github.com/wildfly/wildfly-naming-client#usage. The reproducer can be found here https://github.com/wfink/jboss-eap7.1-playground/blob/master/clients/Wild... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9505) [GSS](7.1.0) use of WildFlyInitialContext with wildfly-config.xml throws javax.naming.NoInitialContextException

by Jiri Ondrusek (JIRA)

[ https://issues.jboss.org/browse/WFLY-9505?page=com.atlassian.jira.plugin.... ] Jiri Ondrusek moved JBEAP-13671 to WFLY-9505: --------------------------------------------- Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-9505 (was: JBEAP-13671) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: EJB Naming (was: EJB) (was: Naming) Affects Version/s: 12.0.0.Alpha1 (was: 7.1.0.DR18) > [GSS](7.1.0) use of WildFlyInitialContext with wildfly-config.xml throws javax.naming.NoInitialContextException > --------------------------------------------------------------------------------------------------------------- > > Key: WFLY-9505 > URL: https://issues.jboss.org/browse/WFLY-9505 > Project: WildFly > Issue Type: Bug > Components: EJB, Naming > Affects Versions: 12.0.0.Alpha1 > Environment: 7.1.0.Beta and 7.1.0.ER2 > Reporter: Jiri Ondrusek > Assignee: Jiri Ondrusek > > If a client use WildFlyInitialContext without properties the following Exception is thrown: > Exception in thread "main" javax.naming.NoInitialContextException > at org.wildfly.naming.client.WildFlyInitialContext.getDefaultInitCtx(WildFlyInitialContext.java:65) > at javax.naming.InitialContext.getURLOrDefaultInitCtx(InitialContext.java:350) > at javax.naming.InitialContext.lookup(InitialContext.java:417) > at org.jboss.wfink.eap71.playground.wildfly.client.WildFlyICConfigClient.main(WildFlyICConfigClient.java:33) > It is expected that this works according to https://github.com/wildfly/wildfly-naming-client#usage. > The reproducer can be found here > https://github.com/wfink/jboss-eap7.1-playground/blob/master/clients/Wild... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9413) Update EclipseLink module to remove unused asm/javassist dependencies

by Scott Marlow (JIRA)

[ https://issues.jboss.org/browse/WFLY-9413?page=com.atlassian.jira.plugin.... ] Scott Marlow closed WFLY-9413. ------------------------------ > Update EclipseLink module to remove unused asm/javassist dependencies > --------------------------------------------------------------------- > > Key: WFLY-9413 > URL: https://issues.jboss.org/browse/WFLY-9413 > Project: WildFly > Issue Type: Task > Components: JPA / Hibernate > Reporter: Scott Marlow > Assignee: Scott Marlow > Fix For: 12.0.0.Alpha1 > > > The EclipseLink module doesn't depend on asm/javassist modules. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3390) WARN logged during server shutdown when Elytron JACC is set

by Ilia Vassilev (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3390?page=com.atlassian.jira.plugi... ] Ilia Vassilev reassigned WFCORE-3390: ------------------------------------- Assignee: Ilia Vassilev > WARN logged during server shutdown when Elytron JACC is set > ----------------------------------------------------------- > > Key: WFCORE-3390 > URL: https://issues.jboss.org/browse/WFCORE-3390 > Project: WildFly Core > Issue Type: Bug > Components: Security > Affects Versions: 3.0.9.Final > Reporter: Ondrej Kotek > Assignee: Ilia Vassilev > Priority: Critical > > When Elytron JACC policy resource is defined, there is WARN logged during server shutdown: > {{WARN [org.wildfly.security] (MSC service thread 1-8) ELY08509: Calling any of the Policy.getPermissions() methods is not supported; please see the Java Authorization Contract for Containers (JACC) specification (section "1.4 Requirements", item 1) and the Java SE API specification for the Policy.getPermissions() methods for more information. Instead, use the Policy.implies() method for authorization checking.}} > This is suspicious behaviour. Customers that monitor logs for warnings have to deal with this. Setting Critical. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (HAWKULARQE-123) [QE] - JMAN4-125 - Stop an EAP Domain - Sprint-68

by Hayk Hovsepyan (JIRA)

[ https://issues.jboss.org/browse/HAWKULARQE-123?page=com.atlassian.jira.pl... ] Hayk Hovsepyan commented on HAWKULARQE-123: ------------------------------------------- PR for domain State https://github.com/ManageIQ/integration_tests/pull/5728 > [QE] - JMAN4-125 - Stop an EAP Domain - Sprint-68 > ------------------------------------------------- > > Key: HAWKULARQE-123 > URL: https://issues.jboss.org/browse/HAWKULARQE-123 > Project: Hawkular QE > Issue Type: Task > Reporter: Hayk Hovsepyan > Assignee: Hayk Hovsepyan > Labels: 4.6 > > See [JMAN4-125|https://issues.jboss.org/browse/JMAN4-125] > Requirement's Test Plan: https://mojo.redhat.com/docs/DOC-1141233 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3392) inaccurate error message in validating required attribute with alternatives

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3392?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-3392: ------------------------------------- Issue Type: Enhancement (was: Bug) > inaccurate error message in validating required attribute with alternatives > --------------------------------------------------------------------------- > > Key: WFCORE-3392 > URL: https://issues.jboss.org/browse/WFCORE-3392 > Project: WildFly Core > Issue Type: Enhancement > Components: Domain Management > Affects Versions: 4.0.0.Alpha2 > Reporter: Chao Wang > Assignee: Chao Wang > Priority: Minor > > This is created based on comments in [JBEAP-8666|https://issues.jboss.org/browse/JBEAP-8666?focusedCommentId=13...] > {quote}failure message is inaccurate and points out only that ssl-context must be defined, it should also mention the security-realm as one of the options. > {noformat} > /subsystem=undertow/server=default-server/https-listener=aaa:add(socket-binding=ajp) > { > "outcome" => "failed", > "failure-description" => "WFLYCTL0172: ssl-context is required", > "rolled-back" => true > } > {noformat} > {quote} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 5 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 October 2017