October 2017 - jboss-jira - Jboss List Archives

[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)

8 years, 6 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)

8 years, 6 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)

8 years, 6 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)

8 years, 6 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)

8 years, 6 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)

8 years, 6 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)

8 years, 6 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)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (HAWKULARQE-199) CFME Tests - Make Midddleware Provider WidgetasticTaggable

by Hayk Hovsepyan (JIRA)

[ https://issues.jboss.org/browse/HAWKULARQE-199?page=com.atlassian.jira.pl... ] Hayk Hovsepyan resolved HAWKULARQE-199. --------------------------------------- Resolution: Done Merged > CFME Tests - Make Midddleware Provider WidgetasticTaggable > ---------------------------------------------------------- > > Key: HAWKULARQE-199 > URL: https://issues.jboss.org/browse/HAWKULARQE-199 > Project: Hawkular QE > Issue Type: Task > Reporter: Hayk Hovsepyan > Assignee: Hayk Hovsepyan > > <gshefer> psav, BaseProvider is still Taggable and not yet WidgetasticTaggable, should I replace it in BaseProvider or just inherit this in ContainersProvider? > <cfme_bot> PR: #5703 [WIPTEST] Widgetastic conversions - downstream-59z - failure > <psav> I think for now yes, unless izapolsk can provide better guidance > <psav> once we see it is WTtaggable on all of them > <psav> we can convert > <izapolsk> gshefer, sure thing, please update BaseProvider as well > <izapolsk> gshefer++ > <cfme_bot> gshefer == 23 > <psav> ahh ok > <psav> izapolsk: it's ready for it? > <cfme_bot> PR: #5432 [WIPTEST] Revert snapshot tests redone - downstream-59z - failure > <gshefer> are you sure, couldn't this effects others which didn't yet implement things like navmazing objects for tagging? > <izapolsk> psav, gshefer, checking > * kkulkarn (~kkulkarn(a)ovpn-123-9.rdu2.redhat.com) has joined #cfme-qe > <psav> OK > <psav> wow just think > <psav> we _could_ implement the EditTags on the WTTaggable class > <psav> as long as it's the same button name for all providers > <psav> unless we do this alreayd > <izapolsk> checking > <psav> :D > <vparekh> hey can someone please help me debug this, not getting why it is yelling > <vparekh> http://pastebin.test.redhat.com/527476 > <psav> looking > <izapolsk> cloudinfra prov is alraedy WidgetasticTaggable > <psav> vparekh: did you decorate the Tenant object? > <psav> is this master? > <psav> if not > <psav> I need link to code > <vparekh> giving code, just a min > <psav> excellent > <izapolsk> middleware provider looks not updated > <psav> hhovsepy_afk: ^^? > <psav> ahhh > <psav> afk > <psav> #sadpanda > <psav> izapolsk: how much effort to fix that yup you think? > <izapolsk> fix - 1h + testing - 2-3h > <psav> hmmm > <psav> I wonder if raoul could squeeze that in > <izapolsk> I think ~2 h > <psav> it would be another big win > <izapolsk> yup > <psav> would that remove the Taggable class completely > <izapolsk> let me check > <psav> or just in providers > <psav> nah > <psav> I can check > <izapolsk> 18 usages > <izapolsk> most in containter > <izapolsk> containters > <vparekh> psav, its in https://github.com/ManageIQ/integration_tests/pull/5492 files > <psav> looks like containers yeh > <psav> and middleware > <psav> thta's it > <psav> 18 usages > <izapolsk> 11 - containers , 6 - midlleware > <psav> 1 in common > <psav> jejeje > <psav> vparekh: looking at it > <juwatts> the ones in containers should be going away soon with gshefer's conversion > * kkulkarn-wfh has quit (Ping timeout: 600 seconds) > <kkulkarn> hello, looking for 2nd level review on https://github.com/ManageIQ/integration_tests/pull/5655 > <vparekh> this time, 'The show' had cfme-qe covered :D > * sshveta_afk has quit (Ping timeout: 600 seconds) > <psav> vparekh: because it's .parent > <psav> not .collection > <vparekh> ah but where > <vparekh> psav, > <vparekh> traceback doesn't have it > * dmisharo has quit (Quit: Konversation terminated!) > * kkulkarn is now known as kkulkarn-wfh > <psav> what do you mean? > <gshefer> izapolsk, psav, is this make sense that Details view has entities attr? - https://github.com/ManageIQ/integration_tests/blob/master/cfme/common/__i... > <psav> where's the traceback? > <mpusater> All, have we noticed the IPV4 problem on certain rhv hosts more than others? > <psav> lcouz|teambuilding: ^^? > <cfme_bot> PR: #5432 [WIPTEST] Revert snapshot tests redone - downstream-57z - failure > <vparekh> psav, http://pastebin.test.redhat.com/527476 > <gshefer> then it'll require me to do ugly workarounds > <izapolsk> ? > <psav> I'll find it > <psav> line 1459 > <psav> prerequisite = NavigateToAttribute('collection', 'All') > <izapolsk> gshefer, someone called view with SummaryTables - entities. What exactly is not ok ? > <psav> that should be changed to parent > <psav> not collection > * raoul|afk is now known as raoul > <vparekh> ah > <vparekh> changing > <vparekh> psav++ > <cfme_bot> psav == 524 > <gshefer> izapolsk, in our object the summary tables are not under entities > <gshefer> izapolsk, inconsistency > <psav> vparekh: just one of the things to check when you are doing this kind of conversion > <vparekh> I was actually finding if I missed something in code, and didn't see the navigation > <vparekh> I need coffee, hehe > <izapolsk> gshefer, can you fix this in containers ? > * You are now known as hhovsepy > <psav> ahhh hhovsepy^^? > <psav> see the comments about Taggable vs WidgetasticTaggable > <psav> any help yo ucan give us here would be appreciated in removing the old class > <psav> containers and hawkular are the only two remaining places > <psav> mornin mshriver > <gshefer> izapolsk, and in provider it called contents > <sbulage> hey mshriver o/ > <gshefer> izapolsk, that crazy, in everyplace is different > <psav> consistency FTL :( > <mshriver> late mornin' psav :) feeling much better now > <mpusater> ok a quick peak right now indicates that infra-rhv40-sprout{1,2,7} are not having issues and infra-rhv40-sprout{3,4,5,6) are. > <mpusater> also vmware as I anticipated is not affected. > <izapolsk> gshefer, I'll fix that on Monday, okay ? > <cfme_bot> PR: #5670 [1LP][RFR] fix to upgrade testing - downstream-57z - failure > <mshriver> mpusater I don't think I ever saw/tested the IPv4 issues on rhv{1,2,7} because those would fail with insufficient resources > <gshefer> izapolsk, in which way? because I'm converting now all to WT, I have PR > <izapolsk> use entities -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9504) Drop JGroups transformers for model versions prior to 1.3.0

by Paul Ferraro (JIRA)

Paul Ferraro created WFLY-9504: ---------------------------------- Summary: Drop JGroups transformers for model versions prior to 1.3.0 Key: WFLY-9504 URL: https://issues.jboss.org/browse/WFLY-9504 Project: WildFly Issue Type: Task Components: Clustering Affects Versions: 11.0.0.Final Reporter: Paul Ferraro Assignee: Paul Ferraro Fix For: 12.0.0.Alpha1 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

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