February 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-11787) Add test case for JBEAP-16152: identity propagation does not work when programmatic web authentication via HttpServletRequest.login() is used

by Daniel Čihák (Jira)

Daniel Čihák created WFLY-11787: ----------------------------------- Summary: Add test case for JBEAP-16152: identity propagation does not work when programmatic web authentication via HttpServletRequest.login() is used Key: WFLY-11787 URL: https://issues.jboss.org/browse/WFLY-11787 Project: WildFly Issue Type: Bug Components: Security Reporter: Daniel Čihák Assignee: Daniel Čihák Add a test case for BEAP-16152: identity propagation does not work when programmatic web authentication via HttpServletRequest.login() is used. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3674) UX proposal for error reporting after test run

by tao zhu (Jira)

[ https://issues.jboss.org/browse/DROOLS-3674?page=com.atlassian.jira.plugi... ] tao zhu commented on DROOLS-3674: --------------------------------- [~danielezonca]Great! Thanks > UX proposal for error reporting after test run > ---------------------------------------------- > > Key: DROOLS-3674 > URL: https://issues.jboss.org/browse/DROOLS-3674 > Project: Drools > Issue Type: Task > Components: Scenario Simulation and Testing > Reporter: Daniele Zonca > Assignee: tao zhu > Priority: Major > Labels: ScenarioSimulation, UXTeam > Attachments: Error reporting after test run-different kinds.png, Error reporting after test run-different kinds2.png, Error reporting after test run-popup.png, Error reporting after test run-popup.png, Error reporting after test run.png > > > As user after a test run, I want see not only the cell that are not correct (red background) but also the reason. > For instance have the possibility to see the actual value that is different from the expected or the error message. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11720) Cannot invoke EJB over HTTP on JDK 11

by Cheng Fang (Jira)

[ https://issues.jboss.org/browse/WFLY-11720?page=com.atlassian.jira.plugin... ] Cheng Fang commented on WFLY-11720: ----------------------------------- I may be missing something, but I don't see anything on WildFly side that need to be fixed for this issue. Can you be more specific what needs to change? > Cannot invoke EJB over HTTP on JDK 11 > ------------------------------------- > > Key: WFLY-11720 > URL: https://issues.jboss.org/browse/WFLY-11720 > Project: WildFly > Issue Type: Bug > Components: EJB, Remoting > Affects Versions: 16.0.0.Beta1 > Environment: JDK 11 > Reporter: Jan Kašík > Assignee: Cheng Fang > Priority: Critical > Attachments: classes.zip, client-app.zip > > > Run of client app calling EJB over HTTP fails on JDK 11 with following log: > {noformat} > Feb 14, 2019 12:49:30 PM org.wildfly.naming.client.Version <clinit> > INFO: WildFly Naming version 1.0.6.Final > WARNING: An illegal reflective access operation has occurred > WARNING: Illegal reflective access by org.wildfly.security.manager.GetAccessibleDeclaredFieldAction (file:/home/hudson/hudson_workspace/mod_cluster/client/wildfly-elytron-1.1.3.Final.jar) to field java.security.AccessControlContext.context > WARNING: Please consider reporting this to the maintainers of org.wildfly.security.manager.GetAccessibleDeclaredFieldAction > WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations > WARNING: All illegal access operations will be denied in a future release > Feb 14, 2019 12:49:30 PM org.wildfly.security.Version <clinit> > INFO: ELY00001: WildFly Elytron version 1.1.3.Final > Feb 14, 2019 12:49:30 PM org.jboss.ejb.client.EJBClient <clinit> > INFO: JBoss EJB Client version 4.0.2.Final > Feb 14, 2019 12:49:30 PM org.xnio.Xnio <clinit> > INFO: XNIO version 3.6.5.Final > Feb 14, 2019 12:49:30 PM org.xnio.nio.NioXnio <clinit> > INFO: XNIO NIO Implementation Version 3.6.5.Final > Feb 14, 2019 12:49:30 PM org.jboss.threads.Version <clinit> > INFO: JBoss Threads version 2.3.0.Beta2 > Feb 14, 2019 12:49:30 PM org.jboss.remoting3.EndpointImpl <clinit> > INFO: JBoss Remoting version 5.0.0.Final > Feb 14, 2019 12:49:30 PM org.jboss.threads.LoggingUncaughtExceptionHandler uncaughtException > ERROR: Thread Thread[XNIO-1 task-1,5,main] threw an uncaught exception > java.lang.ExceptionInInitializerError > at org.jboss.marshalling.river.RiverMarshaller.<clinit>(RiverMarshaller.java:1335) > at org.jboss.marshalling.river.RiverMarshallerFactory.createMarshaller(RiverMarshallerFactory.java:54) > at org.wildfly.httpclient.common.HttpTargetContext.createMarshaller(HttpTargetContext.java:132) > at org.wildfly.httpclient.ejb.HttpEJBReceiver.marshalEJBRequest(HttpEJBReceiver.java:367) > at org.wildfly.httpclient.ejb.HttpEJBReceiver.lambda$processInvocation$1(HttpEJBReceiver.java:185) > at org.wildfly.httpclient.common.HttpTargetContext$1.lambda$completed$0(HttpTargetContext.java:338) > at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1871) > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1400) > at java.base/java.lang.Thread.run(Thread.java:834) > Caused by: java.lang.IllegalStateException: No standard field found for reverse order comparator! > at org.jboss.marshalling.river.Protocol.<clinit>(Protocol.java:287) > ... 9 more > {noformat} -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-620) Document the Jaeger QE pipeline

by Jeeva Kandasamy (Jira)

Jeeva Kandasamy created SWSQE-620: ------------------------------------- Summary: Document the Jaeger QE pipeline Key: SWSQE-620 URL: https://issues.jboss.org/browse/SWSQE-620 Project: Kiali QE Issue Type: Sub-task Reporter: Jeeva Kandasamy Assignee: Jeeva Kandasamy Maistra Downstream Pipeline Needs to be documented on Service Mesh Presentation (https://docs.google.com/presentation/d/1NNk0E6QExG9AUhPDpixV9aGlymoOIqNb6...) Update Jaeger part -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11720) Cannot invoke EJB over HTTP on JDK 11

by Jan Kašík (Jira)

[ https://issues.jboss.org/browse/WFLY-11720?page=com.atlassian.jira.plugin... ] Jan Kašík reopened WFLY-11720: ------------------------------ Users are still consuming affected artifacts, so this needs to be fixed. > Cannot invoke EJB over HTTP on JDK 11 > ------------------------------------- > > Key: WFLY-11720 > URL: https://issues.jboss.org/browse/WFLY-11720 > Project: WildFly > Issue Type: Bug > Components: EJB, Remoting > Affects Versions: 16.0.0.Beta1 > Environment: JDK 11 > Reporter: Jan Kašík > Assignee: Cheng Fang > Priority: Critical > Attachments: classes.zip, client-app.zip > > > Run of client app calling EJB over HTTP fails on JDK 11 with following log: > {noformat} > Feb 14, 2019 12:49:30 PM org.wildfly.naming.client.Version <clinit> > INFO: WildFly Naming version 1.0.6.Final > WARNING: An illegal reflective access operation has occurred > WARNING: Illegal reflective access by org.wildfly.security.manager.GetAccessibleDeclaredFieldAction (file:/home/hudson/hudson_workspace/mod_cluster/client/wildfly-elytron-1.1.3.Final.jar) to field java.security.AccessControlContext.context > WARNING: Please consider reporting this to the maintainers of org.wildfly.security.manager.GetAccessibleDeclaredFieldAction > WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations > WARNING: All illegal access operations will be denied in a future release > Feb 14, 2019 12:49:30 PM org.wildfly.security.Version <clinit> > INFO: ELY00001: WildFly Elytron version 1.1.3.Final > Feb 14, 2019 12:49:30 PM org.jboss.ejb.client.EJBClient <clinit> > INFO: JBoss EJB Client version 4.0.2.Final > Feb 14, 2019 12:49:30 PM org.xnio.Xnio <clinit> > INFO: XNIO version 3.6.5.Final > Feb 14, 2019 12:49:30 PM org.xnio.nio.NioXnio <clinit> > INFO: XNIO NIO Implementation Version 3.6.5.Final > Feb 14, 2019 12:49:30 PM org.jboss.threads.Version <clinit> > INFO: JBoss Threads version 2.3.0.Beta2 > Feb 14, 2019 12:49:30 PM org.jboss.remoting3.EndpointImpl <clinit> > INFO: JBoss Remoting version 5.0.0.Final > Feb 14, 2019 12:49:30 PM org.jboss.threads.LoggingUncaughtExceptionHandler uncaughtException > ERROR: Thread Thread[XNIO-1 task-1,5,main] threw an uncaught exception > java.lang.ExceptionInInitializerError > at org.jboss.marshalling.river.RiverMarshaller.<clinit>(RiverMarshaller.java:1335) > at org.jboss.marshalling.river.RiverMarshallerFactory.createMarshaller(RiverMarshallerFactory.java:54) > at org.wildfly.httpclient.common.HttpTargetContext.createMarshaller(HttpTargetContext.java:132) > at org.wildfly.httpclient.ejb.HttpEJBReceiver.marshalEJBRequest(HttpEJBReceiver.java:367) > at org.wildfly.httpclient.ejb.HttpEJBReceiver.lambda$processInvocation$1(HttpEJBReceiver.java:185) > at org.wildfly.httpclient.common.HttpTargetContext$1.lambda$completed$0(HttpTargetContext.java:338) > at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1871) > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1400) > at java.base/java.lang.Thread.run(Thread.java:834) > Caused by: java.lang.IllegalStateException: No standard field found for reverse order comparator! > at org.jboss.marshalling.river.Protocol.<clinit>(Protocol.java:287) > ... 9 more > {noformat} -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-608) QE CI/CP Integration - stage 1

by Filip Brychta (Jira)

[ https://issues.jboss.org/browse/SWSQE-608?page=com.atlassian.jira.plugin.... ] Filip Brychta updated SWSQE-608: -------------------------------- Sprint: Kiali Sprint #18, Kiali Sprint #19 (was: Kiali Sprint #18) > QE CI/CP Integration - stage 1 > ------------------------------ > > Key: SWSQE-608 > URL: https://issues.jboss.org/browse/SWSQE-608 > Project: Kiali QE > Issue Type: Story > Reporter: Matt Mahoney > Assignee: Filip Brychta > Priority: Major > > 90 Day QE CI/CP Integration Goals as defined in https://docs.google.com/document/d/13rp2_oEN2fKIskzuqtGB64zWPGBGQR50yMVBU... -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11786) Wildfly 15 documentation missing images

by Marco Rossi (Jira)

Marco Rossi created WFLY-11786: ---------------------------------- Summary: Wildfly 15 documentation missing images Key: WFLY-11786 URL: https://issues.jboss.org/browse/WFLY-11786 Project: WildFly Issue Type: Bug Components: Documentation Affects Versions: 15.0.0.Final Reporter: Marco Rossi Attachments: Screenshot_2019-02-27 Getting Started Developing Applications Guide.png In getting started guide for Wildfly 15 some images are missing, for example reference to: http://docs.wildfly.org/15/images/gfx/Eclipse_Helloworld_Deploy_1.jpg return 404 not found (see attached image) -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4352) When on JDK 12, disable tests that hang due to https://bugs.openjdk.java.net/browse/JDK-8219658

by Richard Opalka (Jira)

[ https://issues.jboss.org/browse/WFCORE-4352?page=com.atlassian.jira.plugi... ] Richard Opalka edited comment on WFCORE-4352 at 2/27/19 6:44 AM: ----------------------------------------------------------------- [~brian.stansberry] affected tests should be: * testsuite/standalone/src/test/java/org/jboss/as/test/integration/auditlog/AuditLogToTLSSyslogTestCase.java * testsuite/manualmode/src/test/java/org/jboss/as/test/manualmode/auditlog/AuditLogBootingSyslogTest.java but I still believe the fix could get it into the JDK12 final release :) was (Author: ropalka): [~brian.stansberry] affected tests should be: * testsuite/standalone/src/test/java/org/jboss/as/test/integration/auditlog/AuditLogToTLSSyslogTestCase.java * testsuite/manualmode/src/test/java/org/jboss/as/test/manualmode/auditlog/AuditLogBootingSyslogTest.java but I still believe the fix could get it into the JDK12 final release :) > When on JDK 12, disable tests that hang due to https://bugs.openjdk.java.net/browse/JDK-8219658 > ----------------------------------------------------------------------------------------------- > > Key: WFCORE-4352 > URL: https://issues.jboss.org/browse/WFCORE-4352 > Project: WildFly Core > Issue Type: Task > Components: Test Suite > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Priority: Major > Fix For: 9.0.0.Beta1 > > > A couple tests hang due to https://bugs.openjdk.java.net/browse/JDK-8219658 when run on JDK 12. So until that's fixed check java.version and skip the tests if it's 12. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4352) When on JDK 12, disable tests that hang due to https://bugs.openjdk.java.net/browse/JDK-8219658

by Richard Opalka (Jira)

[ https://issues.jboss.org/browse/WFCORE-4352?page=com.atlassian.jira.plugi... ] Richard Opalka commented on WFCORE-4352: ---------------------------------------- [~brian.stansberry] affected tests should be: * testsuite/standalone/src/test/java/org/jboss/as/test/integration/auditlog/AuditLogToTLSSyslogTestCase.java * testsuite/manualmode/src/test/java/org/jboss/as/test/manualmode/auditlog/AuditLogBootingSyslogTest.java but I still believe the fix could get it into the JDK12 final release :) > When on JDK 12, disable tests that hang due to https://bugs.openjdk.java.net/browse/JDK-8219658 > ----------------------------------------------------------------------------------------------- > > Key: WFCORE-4352 > URL: https://issues.jboss.org/browse/WFCORE-4352 > Project: WildFly Core > Issue Type: Task > Components: Test Suite > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Priority: Major > Fix For: 9.0.0.Beta1 > > > A couple tests hang due to https://bugs.openjdk.java.net/browse/JDK-8219658 when run on JDK 12. So until that's fixed check java.version and skip the tests if it's 12. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3674) UX proposal for error reporting after test run

by Daniele Zonca (Jira)

[ https://issues.jboss.org/browse/DROOLS-3674?page=com.atlassian.jira.plugi... ] Daniele Zonca commented on DROOLS-3674: --------------------------------------- [~zhutaojiajia] Hi, I like this proposal, I think it is fine Daniele > UX proposal for error reporting after test run > ---------------------------------------------- > > Key: DROOLS-3674 > URL: https://issues.jboss.org/browse/DROOLS-3674 > Project: Drools > Issue Type: Task > Components: Scenario Simulation and Testing > Reporter: Daniele Zonca > Assignee: tao zhu > Priority: Major > Labels: ScenarioSimulation, UXTeam > Attachments: Error reporting after test run-different kinds.png, Error reporting after test run-different kinds2.png, Error reporting after test run-popup.png, Error reporting after test run-popup.png, Error reporting after test run.png > > > As user after a test run, I want see not only the cell that are not correct (red background) but also the reason. > For instance have the possibility to see the actual value that is different from the expected or the error message. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 10 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 February 2019