August 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-3988) Domain prints WARNING with JDK10+ during start-up (XNIO illegal reflective access)

by Sultan Zhantemirov (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3988?page=com.atlassian.jira.plugi... ] Sultan Zhantemirov updated WFCORE-3988: --------------------------------------- Comment: was deleted (was: I would also like to let you know that there is the same issue while starting eap7x/one-command-build.manu by Manu framework. {{WARNING: Illegal reflective access by com.google.inject.internal.cglib.core.$ReflectUtils$2 (file:/home/szhantem/acceptance-jdk10-ocb/manu-eap72-acceptance-last/manu-eap-1.1.109/lib/guice-3.0.jar) to method java.lang.ClassLoader.defineClass(java.lang.String,byte[],int,int,java.security.ProtectionDomain)}} Fedora 27, openjdk version "10.0.2" 2018-07-17. ) > Domain prints WARNING with JDK10+ during start-up (XNIO illegal reflective access) > ---------------------------------------------------------------------------------- > > Key: WFCORE-3988 > URL: https://issues.jboss.org/browse/WFCORE-3988 > Project: WildFly Core > Issue Type: Bug > Components: Management > Reporter: Marek Kopecký > Assignee: Jeff Mesnil > Priority: Blocker > > Domain prints WARNING with JDK10+ during start-up (XNIO illegal reflective access) > {noformat} > [mkopecky@dhcp-10-40-4-197 bin]$ export JAVA_OPTS="--add-modules=java.se" > [mkopecky@dhcp-10-40-4-197 bin]$ ./domain.sh > JAVA_OPTS already set in environment; overriding default settings with values: --add-modules=java.se > ========================================================================= > JBoss Bootstrap Environment > JBOSS_HOME: /home/mkopecky/playground/wf/wfly.29/wfly.29 > JAVA: /home/mkopecky/base/jdk11_ea21_2018_08_01/bin/java > JAVA_OPTS: -server --add-modules=java.se > ========================================================================= > 10:37:11,438 INFO [org.jboss.modules] (main) JBoss Modules version 1.8.5.Final > 10:37:11,659 INFO [org.jboss.threads] (main) JBoss Threads version 2.3.2.Final > ... > [Host Controller] WARNING: An illegal reflective access operation has occurred > [Host Controller] WARNING: Illegal reflective access by org.xnio.nio.NioXnio$2 (jar:file:/home/mkopecky/playground/wf/wfly.29/wfly.29/modules/system/layers/base/org/jboss/xnio/nio/main/xnio-nio-3.6.3.Final.jar!/) to constructor sun.nio.ch.EPollSelectorProvider() > [Host Controller] WARNING: Please consider reporting this to the maintainers of org.xnio.nio.NioXnio$2 > [Host Controller] WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations > [Host Controller] WARNING: All illegal access operations will be denied in a future release > {noformat} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2564) [DMN Designer] Data-types: Grid: General

by Jozef Marko (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2564?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-2564: -------------------------------- Description: Different types of Expression (the grid-view) should support defining the input and output data-types. I am leaving implementation of this until the ability to use and define data-types at the graph-view is fully complete; as the scenarios required by this JIRA will re-use the same components. h3. Manual Acceptance test - Create two decision nodes - Specify some expression for both - Open expression editor for first - Rename the decision node in properties panel -- Check *<< Back to XXX* (/) -- Check Expression header cell (/) - Via navigation dock open second node expression -- Check *<< Back to XXX* (/) -- Check Expression header cell (/) - Rename the decision node in properties panel -- Check *<< Back to XXX* (/) -- Check Expression header cell (/) - Save and reopen diagram -- Check names are stored (/) was: Different types of Expression (the grid-view) should support defining the input and output data-types. I am leaving implementation of this until the ability to use and define data-types at the graph-view is fully complete; as the scenarios required by this JIRA will re-use the same components. h3. Manual Acceptance test - Create two decision nodes - Specify some expression for both - Open expression editor for first - Rename the decision node in properties panel -- Check *<< Back to XXX* (/) -- Check Expression header cell (x) - Via navigation dock open second node expression -- Check *<< Back to XXX* (/) -- Check Expression header cell (x) - Rename the decision node in properties panel -- Check *<< Back to XXX* (/) -- Check Expression header cell (x) - Save and reopen diagram -- Check names are stored (/) > [DMN Designer] Data-types: Grid: General > ---------------------------------------- > > Key: DROOLS-2564 > URL: https://issues.jboss.org/browse/DROOLS-2564 > Project: Drools > Issue Type: Feature Request > Components: DMN Editor > Reporter: Michael Anstis > Assignee: Michael Anstis > > Different types of Expression (the grid-view) should support defining the input and output data-types. I am leaving implementation of this until the ability to use and define data-types at the graph-view is fully complete; as the scenarios required by this JIRA will re-use the same components. > h3. Manual Acceptance test > - Create two decision nodes > - Specify some expression for both > - Open expression editor for first > - Rename the decision node in properties panel > -- Check *<< Back to XXX* (/) > -- Check Expression header cell (/) > - Via navigation dock open second node expression > -- Check *<< Back to XXX* (/) > -- Check Expression header cell (/) > - Rename the decision node in properties panel > -- Check *<< Back to XXX* (/) > -- Check Expression header cell (/) > - Save and reopen diagram > -- Check names are stored (/) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10735) Unable to disable iiop port (non-ssl)

by Tomasz Adamski (JIRA)

[ https://issues.jboss.org/browse/WFLY-10735?page=com.atlassian.jira.plugin... ] Tomasz Adamski commented on WFLY-10735: --------------------------------------- [~baranowb] Yes, this is a bug. POA has to use SSL socket only if no cleartext socket binding is configured. I have created a fix already but it has to be merged on top of WFLY-9107 (added link to that issue). > Unable to disable iiop port (non-ssl) > ------------------------------------- > > Key: WFLY-10735 > URL: https://issues.jboss.org/browse/WFLY-10735 > Project: WildFly > Issue Type: Bug > Affects Versions: 13.0.0.Final > Reporter: Derek Horton > Assignee: Tomasz Adamski > Fix For: 14.0.0.CR1 > > > Wildfly 13.0.0.Final > Removing the "iiop" socket-binding from the orb configuration: > <subsystem xmlns="urn:jboss:domain:iiop-openjdk:2.0"> > <orb ssl-socket-binding="iiop-ssl"/> > <initializers security="identity" transactions="spec"/> > <security server-requires-ssl="true" client-requires-ssl="true" support-ssl="true" security-domain="jsse"/> > </subsystem> > and commenting out the iiop socket-binding leads to the following error: > 2018-07-24 14:47:29,315 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([("subsystem" => "iiop-openjdk")]) - failure description: { > "WFLYCTL0412: Required services that are not installed:" => ["jboss.binding.iiop"], > "WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.iiop-openjdk.orb-service is missing [jboss.binding.iiop]"] > } > 2018-07-24 14:47:29,351 INFO [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0183: Service status report > WFLYCTL0184: New missing/unsatisfied dependencies: > service jboss.binding.iiop (missing) dependents: [service jboss.iiop-openjdk.orb-service] -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3988) Domain prints WARNING with JDK10+ during start-up (XNIO illegal reflective access)

by Sultan Zhantemirov (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3988?page=com.atlassian.jira.plugi... ] Sultan Zhantemirov commented on WFCORE-3988: -------------------------------------------- I would also like to let you know that there is the same issue while starting eap7x/one-command-build.manu by Manu framework. {{WARNING: Illegal reflective access by com.google.inject.internal.cglib.core.$ReflectUtils$2 (file:/home/szhantem/acceptance-jdk10-ocb/manu-eap72-acceptance-last/manu-eap-1.1.109/lib/guice-3.0.jar) to method java.lang.ClassLoader.defineClass(java.lang.String,byte[],int,int,java.security.ProtectionDomain)}} Fedora 27, openjdk version "10.0.2" 2018-07-17. > Domain prints WARNING with JDK10+ during start-up (XNIO illegal reflective access) > ---------------------------------------------------------------------------------- > > Key: WFCORE-3988 > URL: https://issues.jboss.org/browse/WFCORE-3988 > Project: WildFly Core > Issue Type: Bug > Components: Management > Reporter: Marek Kopecký > Assignee: Jeff Mesnil > Priority: Blocker > > Domain prints WARNING with JDK10+ during start-up (XNIO illegal reflective access) > {noformat} > [mkopecky@dhcp-10-40-4-197 bin]$ export JAVA_OPTS="--add-modules=java.se" > [mkopecky@dhcp-10-40-4-197 bin]$ ./domain.sh > JAVA_OPTS already set in environment; overriding default settings with values: --add-modules=java.se > ========================================================================= > JBoss Bootstrap Environment > JBOSS_HOME: /home/mkopecky/playground/wf/wfly.29/wfly.29 > JAVA: /home/mkopecky/base/jdk11_ea21_2018_08_01/bin/java > JAVA_OPTS: -server --add-modules=java.se > ========================================================================= > 10:37:11,438 INFO [org.jboss.modules] (main) JBoss Modules version 1.8.5.Final > 10:37:11,659 INFO [org.jboss.threads] (main) JBoss Threads version 2.3.2.Final > ... > [Host Controller] WARNING: An illegal reflective access operation has occurred > [Host Controller] WARNING: Illegal reflective access by org.xnio.nio.NioXnio$2 (jar:file:/home/mkopecky/playground/wf/wfly.29/wfly.29/modules/system/layers/base/org/jboss/xnio/nio/main/xnio-nio-3.6.3.Final.jar!/) to constructor sun.nio.ch.EPollSelectorProvider() > [Host Controller] WARNING: Please consider reporting this to the maintainers of org.xnio.nio.NioXnio$2 > [Host Controller] WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations > [Host Controller] WARNING: All illegal access operations will be denied in a future release > {noformat} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-281) Upgrade Clusters to OpenShift 3.10

by Guilherme Baufaker Rêgo (JIRA)

[ https://issues.jboss.org/browse/SWSQE-281?page=com.atlassian.jira.plugin.... ] Guilherme Baufaker Rêgo commented on SWSQE-281: ----------------------------------------------- PR which needs to be included on openshift 3.10 in order to solve another bug on elasticsearch: - https://github.com/openshift/openshift-ansible/pull/9177 > Upgrade Clusters to OpenShift 3.10 > ---------------------------------- > > Key: SWSQE-281 > URL: https://issues.jboss.org/browse/SWSQE-281 > Project: Kiali QE > Issue Type: QE Task > Reporter: Matt Mahoney > Assignee: Guilherme Baufaker Rêgo > > Update Clusters to Openshift 3.10 in order to match Istio 1.0 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-281) Upgrade Clusters to OpenShift 3.10

by Guilherme Baufaker Rêgo (JIRA)

[ https://issues.jboss.org/browse/SWSQE-281?page=com.atlassian.jira.plugin.... ] Guilherme Baufaker Rêgo edited comment on SWSQE-281 at 8/1/18 8:22 AM: ----------------------------------------------------------------------- Bugs encountered during the upgrade process: - https://bugzilla.redhat.com/show_bug.cgi?id=1576088 - https://bugzilla.redhat.com/show_bug.cgi?id=1575822 - https://bugzilla.redhat.com/show_bug.cgi?id=1575507 - https://bugzilla.redhat.com/show_bug.cgi?id=1579676 Solutions: - https://access.redhat.com/solutions/3547831 Errata: - https://access.redhat.com/errata/RHBA-2018:1816 was (Author: gbaufake): Faced some bugs on the upgrade process Bugs Related: - https://bugzilla.redhat.com/show_bug.cgi?id=1576088 - https://bugzilla.redhat.com/show_bug.cgi?id=1575822 - https://bugzilla.redhat.com/show_bug.cgi?id=1575507 - https://bugzilla.redhat.com/show_bug.cgi?id=1579676 Solutions: - https://access.redhat.com/solutions/3547831 Errata: -https://access.redhat.com/errata/RHBA-2018:1816 > Upgrade Clusters to OpenShift 3.10 > ---------------------------------- > > Key: SWSQE-281 > URL: https://issues.jboss.org/browse/SWSQE-281 > Project: Kiali QE > Issue Type: QE Task > Reporter: Matt Mahoney > Assignee: Guilherme Baufaker Rêgo > > Update Clusters to Openshift 3.10 in order to match Istio 1.0 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2764) Remove dead code in AuthoringPerspective, AdministrationPerspective and Social Home Page

by Klara Kufova (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2764?page=com.atlassian.jira.plugi... ] Klara Kufova updated DROOLS-2764: --------------------------------- Tester: Klara Kufova (was: Jozef Marko) > Remove dead code in AuthoringPerspective, AdministrationPerspective and Social Home Page > ---------------------------------------------------------------------------------------- > > Key: DROOLS-2764 > URL: https://issues.jboss.org/browse/DROOLS-2764 > Project: Drools > Issue Type: Task > Affects Versions: 7.9.0.Final > Reporter: Toni Rikkola > Assignee: Toni Rikkola > > h3. Manual acceptance test > - Deployment to app server doesn't throw error > - Go through perspectives, check no runtime error occurs > - Check if old documentation is not present -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10777) Add WildFly Elytron / JASPIC Integration Tests

by Darran Lofthouse (JIRA)

Darran Lofthouse created WFLY-10777: --------------------------------------- Summary: Add WildFly Elytron / JASPIC Integration Tests Key: WFLY-10777 URL: https://issues.jboss.org/browse/WFLY-10777 Project: WildFly Issue Type: Task Components: Security, Test Suite Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 14.0.0.CR1 The following key scenarios should be covered within the Elytron testsuite module: - * Pre-configured JASPIC In this case the SAMs are configured within the Elytron subsystem and applied at runtime to the web application. Two predominant modes to consider: - # Fully integrated, i.e. the Callbacks make use of the SecurityDomain for authentication. # Ad-Hoc Identity i.e. We still have a security domain but trust the SAM to establish an ad-hoc identity. * Programatically configured JASPIC During servlet initilisation the new JaspicConfigurationBuilder API can be used to dynamically register a configuration. Likely to need the same two modes. * Retrospective JASPIC In both the above cases the deployment can be deployed and either use Elytron HTTP authentication mechanisms or be unsecured, JASPIC for the deployment can be activated either via configuration or programatically and should take precedence over the existing authentication. * Programatic Authentication A servlet can use the authentication API on the HttpServletRequest and trigger authentication. * No SecurityDomain This one may not be as applicable at this stage but we should at some point support JASPIC being applied to a deployment not associated with any security domain, i.e. a new deployment on a clean install could programatically register a JASPIC configuration. Without any security domain the identity would only have relevance within the servlet container so establishing an ad-hoc identity is actually a better approach. Additionally this relies on no default being present in the default config. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2821) [DMN Designer] [IE11] Missing Edit Expression type icon

by Jozef Marko (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2821?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-2821: -------------------------------- Steps to Reproduce: # Create new diagram # Add a decision node # Select that node # Notice missing icon for edit expression type was: # Create new diagram # Add a decision node # Select that node # Press delete or click on trash icon # Error dialog will appear > [DMN Designer] [IE11] Missing Edit Expression type icon > ------------------------------------------------------- > > Key: DROOLS-2821 > URL: https://issues.jboss.org/browse/DROOLS-2821 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.10.0.Final > Environment: IE11 > Reporter: Jozef Marko > Assignee: Michael Anstis > Labels: drools-tools > Attachments: Screenshot from 2018-08-01 13-34-32.png > > > After node deletion error dialo appears: *An error happened [com.google.gwt.core.client.JavaScriptException: (TypeError) : Object doesn't support property or method 'startsWith']. Do you want to undo the last action?* -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2821) [DMN Designer] [IE11] Missing Edit Expression type icon

by Jozef Marko (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2821?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-2821: -------------------------------- Description: Icon for edit expression type is missing. (was: After node deletion error dialo appears: *An error happened [com.google.gwt.core.client.JavaScriptException: (TypeError) : Object doesn't support property or method 'startsWith']. Do you want to undo the last action?*) > [DMN Designer] [IE11] Missing Edit Expression type icon > ------------------------------------------------------- > > Key: DROOLS-2821 > URL: https://issues.jboss.org/browse/DROOLS-2821 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.10.0.Final > Environment: IE11 > Reporter: Jozef Marko > Assignee: Michael Anstis > Labels: drools-tools > Attachments: Screenshot from 2018-08-01 13-34-32.png > > > Icon for edit expression type is missing. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 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 August 2018