February 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-11789) Intermittent failures in NotClosingInjectedContextTestCase

by Brian Stansberry (Jira)

Brian Stansberry created WFLY-11789: --------------------------------------- Summary: Intermittent failures in NotClosingInjectedContextTestCase Key: WFLY-11789 URL: https://issues.jboss.org/browse/WFLY-11789 Project: WildFly Issue Type: Bug Components: JMS Reporter: Brian Stansberry Assignee: ehsavoie Hugonnet Test is failing quite regularly now: https://ci.wildfly.org/project.html?projectId=WF_PullRequest&testNameId=-... Please send up a PR to @Ignore unless there's a quick fix. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3675) Create HTML/CSS for global setting dock + Test Scenario creation popup

by Sarah Rambacher (Jira)

[ https://issues.jboss.org/browse/DROOLS-3675?page=com.atlassian.jira.plugi... ] Sarah Rambacher commented on DROOLS-3675: ----------------------------------------- [~zhutaojiajia] What do you think about using radio buttons for the Type and Expression Language fields, since there are only 2 options? [~danielezonca] thinks there would be 3 at most in the future. I think it would be easier for the user to see the options and just one click to change if necessary. > Create HTML/CSS for global setting dock + Test Scenario creation popup > ---------------------------------------------------------------------- > > Key: DROOLS-3675 > URL: https://issues.jboss.org/browse/DROOLS-3675 > Project: Drools > Issue Type: Task > Components: Scenario Simulation and Testing > Reporter: Daniele Zonca > Assignee: Sarah Rambacher > Priority: Major > Labels: ScenarioSimulation > > Please refer to for the mockup > https://issues.jboss.org/browse/DROOLS-3492 -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11640) NPE with wildfly-openssl using OpenSSL 1.1.1a

by Jan Stourac (Jira)

[ https://issues.jboss.org/browse/WFLY-11640?page=com.atlassian.jira.plugin... ] Jan Stourac commented on WFLY-11640: ------------------------------------ [~iweiss], I can see the very same issue even on my Fedora 29. See: # get and download WildFly 15.0.1.Final # unzip and start ./bin/standalone.sh # configure openssl provider: {code} /core-service=management/security-realm=ApplicationRealm/server-identity=ssl:write-attribute(name=protocol,value=openssl.TLSv1.2) reload {code} # perform https request against server: curl -k https://localhost:8443 # see error in server.log Same version of OpenSSL library: {code} $ rpm -qi openssl Name : openssl Epoch : 1 Version : 1.1.1a Release : 1.fc29 Architecture: x86_64 {code} What version of WildFly have you been testing this against? > NPE with wildfly-openssl using OpenSSL 1.1.1a > --------------------------------------------- > > Key: WFLY-11640 > URL: https://issues.jboss.org/browse/WFLY-11640 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Affects Versions: 15.0.1.Final > Environment: OpenSSL 1.1.1a > Reporter: Jan Stourac > Assignee: Ingo Weiss > Priority: Major > > It is impossible to use {{wildfly-openssl}} binding with OpenSSL 1.1.1a (RHEL8 uses 1.1.1 at the moment but there seems to be same issue). There is an NPE during the ciphersuites initialization: > {code} > 9:10:58,330 WARNING [org.wildfly.openssl.OpenSSLContextSPI] (MSC service thread 1-3) WFOPENSSL0014 Failed to initialize ciphers: java.lang.NullPointerException > at org.wildfly.openssl.CipherSuiteConverter.toJava(CipherSuiteConverter.java:284) > at org.wildfly.openssl.OpenSSLContextSPI.getAvailableCipherSuites(OpenSSLContextSPI.java:109) > at org.wildfly.openssl.OpenSSLEngine.getSupportedCipherSuites(OpenSSLEngine.java:711) > at org.wildfly.openssl.OpenSSLSocket.getSupportedCipherSuites(OpenSSLSocket.java:163) > at javax.net.ssl.SSLContextSpi.engineGetSupportedSSLParameters(SSLContextSpi.java:194) > at javax.net.ssl.SSLContext.getSupportedSSLParameters(SSLContext.java:436) > at org.jboss.as.domain.management.security.SSLContextService.wrapSslContext(SSLContextService.java:116) > at org.jboss.as.domain.management.security.SSLContextService.start(SSLContextService.java:102) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1738) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1700) > at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1558) > at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35) > at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985) > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487) > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1378) > at java.lang.Thread.run(Thread.java:748) > {code} > and then there is NPE during the request itself: > {code} > 19:12:18,417 ERROR [org.xnio.listener] (default I/O-2) XNIO001007: A channel event listener threw an exception: java.lang.NullPointerException > at org.wildfly.openssl.CipherSuiteConverter.toJava(CipherSuiteConverter.java:284) > at org.wildfly.openssl.OpenSSLEngine.toJavaCipherSuite(OpenSSLEngine.java:1094) > at org.wildfly.openssl.OpenSSLEngine.getEnabledCipherSuites(OpenSSLEngine.java:729) > at org.wildfly.openssl.OpenSSLContextSPI.getCiphers(OpenSSLContextSPI.java:339) > at org.wildfly.openssl.OpenSSLEngine.getEnabledCipherSuites(OpenSSLEngine.java:720) > at io.undertow.server.protocol.http.AlpnOpenListener.engineSupportsHTTP2(AlpnOpenListener.java:324) > at io.undertow.server.protocol.http.AlpnOpenListener$1.apply(AlpnOpenListener.java:239) > at io.undertow.server.protocol.http.AlpnOpenListener$1.apply(AlpnOpenListener.java:235) > at io.undertow.server.protocol.http.AlpnOpenListener$SSLConduitUpdater.apply(AlpnOpenListener.java:430) > at io.undertow.server.protocol.http.AlpnOpenListener$SSLConduitUpdater.apply(AlpnOpenListener.java:419) > at io.undertow.protocols.alpn.DefaultAlpnEngineManager.registerEngine(DefaultAlpnEngineManager.java:31) > at io.undertow.protocols.alpn.ALPNManager.registerEngineCallback(ALPNManager.java:80) > at io.undertow.server.protocol.http.AlpnOpenListener.handleEvent(AlpnOpenListener.java:235) > at io.undertow.server.protocol.http.AlpnOpenListener.handleEvent(AlpnOpenListener.java:64) > at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92) > at org.xnio.ChannelListeners$10.handleEvent(ChannelListeners.java:291) > at org.xnio.ChannelListeners$10.handleEvent(ChannelListeners.java:286) > at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92) > at org.xnio.ChannelListeners$DelegatingChannelListener.handleEvent(ChannelListeners.java:1092) > at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92) > at org.xnio.nio.QueuedNioTcpServer$1.run(QueuedNioTcpServer.java:131) > at org.xnio.nio.WorkerThread.safeRun(WorkerThread.java:612) > at org.xnio.nio.WorkerThread.run(WorkerThread.java:479) > {code} > Looking briefly into it, the cipher that is trying to be used is *{{TLS_AES_256_GCM_SHA384}}*. It is interesting that this cipher has underscores '_' in its name instead of hyphens '-' as most of the openssl ciphers have. Looks like these were added in the sake of TLSv1.3, [see here|https://github.com/openssl/openssl/commit/fa25763b5528b56b448d64bfba...]. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11788) revert ironjacamar to 1.4.12

by Stefano Maestri (Jira)

[ https://issues.jboss.org/browse/WFLY-11788?page=com.atlassian.jira.plugin... ] Stefano Maestri moved JBEAP-16477 to WFLY-11788: ------------------------------------------------ Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-11788 (was: JBEAP-16477) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Target Release: (was: 7.backlog.GA) > revert ironjacamar to 1.4.12 > ---------------------------- > > Key: WFLY-11788 > URL: https://issues.jboss.org/browse/WFLY-11788 > Project: WildFly > Issue Type: Task > Reporter: Stefano Maestri > Priority: Major > -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 8 months

1
0
0 / 0

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

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

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

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

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

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

6 years, 8 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira February 2019