March 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-3683) [DMN Designer] Data Types - Properties panel must be refreshed when a Data Type is created

by Michael Anstis (Jira)

[ https://issues.jboss.org/browse/DROOLS-3683?page=com.atlassian.jira.plugi... ] Michael Anstis edited comment on DROOLS-3683 at 3/6/19 9:30 AM: ---------------------------------------------------------------- You need to re-select the {{InputData}} by first selecting another node and then the {{InputData}} again. The "Properties Panel" content does not update when changes on the Data Type tab affects available data-types. was (Author: manstis): You need to de-select the {{InputData}} by first selecting another node and then the {{InputData}} again. The "Properties Panel" content does not update when changes on the Data Type tab affects available data-types. > [DMN Designer] Data Types - Properties panel must be refreshed when a Data Type is created > ------------------------------------------------------------------------------------------ > > Key: DROOLS-3683 > URL: https://issues.jboss.org/browse/DROOLS-3683 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.18.0.Final > Reporter: Guilherme Carreiro > Assignee: Guilherme Carreiro > Priority: Major > Labels: drools-tools > > Data Types are not refreshing the properties panel. > Steps to reproduce > - Add two input nodes ("Driver" and "Violation) > - Add two decision nodes ("Suspended?" and "Fine?") > - Connect "Drive" to "Suspended?" > - Connect "Violation" to "Fine?" > - Connect "Fine?" to "Suspended?" > - Select "Violation" > - Create three new DTs with an input node selected > - Go back to the graph > - Noticed the "Output data type" dropdown is not updated -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-630) Setup Openshift 3.11 Cluster In PSI For Beta/GA Soak Testing

by Matt Mahoney (Jira)

[ https://issues.jboss.org/browse/SWSQE-630?page=com.atlassian.jira.plugin.... ] Matt Mahoney updated SWSQE-630: ------------------------------- Summary: Setup Openshift 3.11 Cluster In PSI For Beta/GA Soak Testing (was: Setup Openshift 3.1 Cluster In PSI For Beta/GA Soak Testing) > Setup Openshift 3.11 Cluster In PSI For Beta/GA Soak Testing > ------------------------------------------------------------ > > Key: SWSQE-630 > URL: https://issues.jboss.org/browse/SWSQE-630 > Project: Kiali QE > Issue Type: QE Task > Reporter: Matt Mahoney > Priority: Major > > There is a need to run soak tests on Kiali Beta and GA builds, that will run for about 5 days. This can not currently be done on OCP4/AWS due to the 48hr cluster life restriction. > As an alternative to OCP4/AWS, run the Kiali soak tests on Openshift 3.11, and so so in the PSI Openstack infrastructure. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-630) Setup Openshift 3.1 Cluster In PSI For Beta/GA Soak Testing

by Matt Mahoney (Jira)

Matt Mahoney created SWSQE-630: ---------------------------------- Summary: Setup Openshift 3.1 Cluster In PSI For Beta/GA Soak Testing Key: SWSQE-630 URL: https://issues.jboss.org/browse/SWSQE-630 Project: Kiali QE Issue Type: QE Task Reporter: Matt Mahoney There is a need to run soak tests on Kiali Beta and GA builds, that will run for about 5 days. This can not currently be done on OCP4/AWS due to the 48hr cluster life restriction. As an alternative to OCP4/AWS, run the Kiali soak tests on Openshift 3.11, and so so in the PSI Openstack infrastructure. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-629) Set up monitoring for istio PSI OpenStack project

by Filip Brychta (Jira)

Filip Brychta created SWSQE-629: ----------------------------------- Summary: Set up monitoring for istio PSI OpenStack project Key: SWSQE-629 URL: https://issues.jboss.org/browse/SWSQE-629 Project: Kiali QE Issue Type: QE Task Reporter: Filip Brychta Assignee: Filip Brychta We want to monitor usage of the cluster and send emails with usage to users and alerts when we are coming close to the resource limits. Maybe send email warning for long running machines to owners? -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-622) Create a Polarion Test Run TEmplate for Beta/GA

by Hayk Hovsepyan (Jira)

[ https://issues.jboss.org/browse/SWSQE-622?page=com.atlassian.jira.plugin.... ] Hayk Hovsepyan resolved SWSQE-622. ---------------------------------- Resolution: Done https://polarion.engineering.redhat.com/polarion/#/project/SwiftSunshine/... > Create a Polarion Test Run TEmplate for Beta/GA > ----------------------------------------------- > > Key: SWSQE-622 > URL: https://issues.jboss.org/browse/SWSQE-622 > Project: Kiali QE > Issue Type: QE Task > Reporter: Hayk Hovsepyan > Assignee: Hayk Hovsepyan > Priority: Major > > Currently we already have a template: https://polarion.engineering.redhat.com/polarion/#/project/SwiftSunshine/... > We need to add all important testcases into that. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-155) WildFly gets stuck with TLSv1.3 on JDK 11

by Pavel Jelinek (Jira)

[ https://issues.jboss.org/browse/WFWIP-155?page=com.atlassian.jira.plugin.... ] Pavel Jelinek updated WFWIP-155: -------------------------------- Labels: jdk11 (was: ) > WildFly gets stuck with TLSv1.3 on JDK 11 > ----------------------------------------- > > Key: WFWIP-155 > URL: https://issues.jboss.org/browse/WFWIP-155 > Project: WildFly WIP > Issue Type: Bug > Components: Security > Environment: JDK 11 > Reporter: Adam Krajcik > Assignee: Farah Juma > Priority: Blocker > Labels: jdk11 > > WildFly gets stuck with when using TLSv1.3. The process starts to heavily use the processor and cannot be stopped by simple SIGINT(Ctrl+C). The issue needs further investigation as no apparent reason for it being stuck. > One possibility is mentioned in the comments for UNDERTOW-1493 is [JDK-8208526|https://bugs.openjdk.java.net/browse/JDK-8208526]. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11814) PrometheusCollector is not thread-safe causing NPEs during deployment

by Paul Ferraro (Jira)

Paul Ferraro created WFLY-11814: ----------------------------------- Summary: PrometheusCollector is not thread-safe causing NPEs during deployment Key: WFLY-11814 URL: https://issues.jboss.org/browse/WFLY-11814 Project: WildFly Issue Type: Bug Components: MP Metrics Affects Versions: 16.0.0.Final Reporter: Paul Ferraro Assignee: Jeff Mesnil The logic within PrometheusCollector.addMetricFamilySampleSupplier(...) is not thread safe and can easily trigger an NPE during deployment. e.g. {noformat} 10:33:32,706 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC000001: Failed to start service jboss.deployment.subunit."web-sso.ear"."sso-with-no-auth.war".metrics: org.jboss.msc.service.StartException in service jboss.deployment.subunit."web-sso.ear"."sso-with-no-auth.war".metrics: Failed to start service at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1730) 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:1982) at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486) at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377) at java.lang.Thread.run(Thread.java:748) Caused by: java.lang.NullPointerException at org.wildfly.extension.microprofile.metrics.PrometheusCollector.addMetricFamilySampleSupplier(PrometheusCollector.java:32) at org.wildfly.extension.microprofile.metrics.MetricCollector.collectResourceMetrics0(MetricCollector.java:157) at org.wildfly.extension.microprofile.metrics.MetricCollector.collectResourceMetrics0(MetricCollector.java:166) at org.wildfly.extension.microprofile.metrics.MetricCollector.collectResourceMetrics(MetricCollector.java:92) at org.wildfly.extension.microprofile.metrics.deployment.DeploymentMetricService.start(DeploymentMetricService.java:54) at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1738) at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1700) ... 6 more {noformat} -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4303) NullPointerException - with SNI configured on IBM JDK 1.8

by Diana Vilkolakova (Jira)

[ https://issues.jboss.org/browse/WFCORE-4303?page=com.atlassian.jira.plugi... ] Diana Vilkolakova reassigned WFCORE-4303: ----------------------------------------- Assignee: Diana Vilkolakova > NullPointerException - with SNI configured on IBM JDK 1.8 > --------------------------------------------------------- > > Key: WFCORE-4303 > URL: https://issues.jboss.org/browse/WFCORE-4303 > Project: WildFly Core > Issue Type: Bug > Components: Security > Environment: IBM JDK 1.8: > {code} > java version "1.8.0_181" > Java(TM) SE Runtime Environment (build 8.0.5.20 - pxa6480sr5fp20-20180802_01(SR5 FP20)) > IBM J9 VM (build 2.9, JRE 1.8.0 Linux amd64-64-Bit Compressed References 20180731_393394 (JIT enabled, AOT enabled) > OpenJ9 - bd23af8 > OMR - ca1411c > IBM - 98805ca) > JCL - 20180719_01 based on Oracle jdk8u181-b12 > {code} > Reporter: Jan Stourac > Assignee: Diana Vilkolakova > Priority: Major > > When running with IBM JDK 1.8, there is an NPE during the request performed against https-listener which has configured 'server-ssl-sni-context' instance (when using standard 'server-ssl-context' no exception is present): > {code} > $ curl https://localhost:8443 -k > curl: (35) OpenSSL SSL_connect: SSL_ERROR_SYSCALL in connection to localhost:8443 > {code} > related exception in server.log: > {code} > 18:23:01,227 ERROR [io.undertow.request.io] (default I/O-6) UT005090: Unexpected failure: java.lang.NullPointerException > at io.undertow.protocols.ssl.SslConduit.doUnwrap(SslConduit.java:772) > at io.undertow.protocols.ssl.SslConduit.read(SslConduit.java:567) > at org.xnio.conduits.ConduitStreamSourceChannel.read(ConduitStreamSourceChannel.java:127) > at io.undertow.server.protocol.http.AlpnOpenListener$AlpnConnectionListener.handleEvent(AlpnOpenListener.java:348) > at io.undertow.server.protocol.http.AlpnOpenListener.handleEvent(AlpnOpenListener.java:305) > 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} > When I switch to OpenSSL provider using > {code} > /subsystem=elytron/server-ssl-context=defaultSSC:write-attribute(name=providers,value=openssl) > {code} > then the exception disappears. > ---- > Note: sometimes I can also see shorter exception stacktrace: > {code} > 18:17:15,711 ERROR [io.undertow.request.io] (default I/O-2) UT005090: Unexpected failure: java.lang.NullPointerException > at io.undertow.protocols.ssl.SslConduit.doUnwrap(SslConduit.java:772) > at io.undertow.protocols.ssl.SslConduit.doHandshake(SslConduit.java:648) > at io.undertow.protocols.ssl.SslConduit.access$900(SslConduit.java:63) > at io.undertow.protocols.ssl.SslConduit$SslReadReadyHandler.readReady(SslConduit.java:1136) > at org.xnio.nio.NioSocketConduit.handleReady(NioSocketConduit.java:89) > at org.xnio.nio.WorkerThread.run(WorkerThread.java:591) > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3725) [DMN Designer] Included Models - Error when a file with included models is saved

by Guilherme Carreiro (Jira)

[ https://issues.jboss.org/browse/DROOLS-3725?page=com.atlassian.jira.plugi... ] Guilherme Carreiro updated DROOLS-3725: --------------------------------------- Sprint: 2019 Week 08-10 > [DMN Designer] Included Models - Error when a file with included models is saved > -------------------------------------------------------------------------------- > > Key: DROOLS-3725 > URL: https://issues.jboss.org/browse/DROOLS-3725 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Reporter: Guilherme Carreiro > Assignee: Guilherme Carreiro > Priority: Major > Labels: drools-tools > Attachments: 2019-03-01 17.49.00.gif > > > When a file with included models is saved and re-opened, the following error happens: > !2019-03-01 17.49.00.gif|thumbnail! -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3693) Prepare a crash course on how to use JP for parsing and generating code

by Luca Molteni (Jira)

[ https://issues.jboss.org/browse/DROOLS-3693?page=com.atlassian.jira.plugi... ] Luca Molteni closed DROOLS-3693. -------------------------------- Resolution: Done > Prepare a crash course on how to use JP for parsing and generating code > ----------------------------------------------------------------------- > > Key: DROOLS-3693 > URL: https://issues.jboss.org/browse/DROOLS-3693 > Project: Drools > Issue Type: Task > Reporter: Luca Molteni > Assignee: Luca Molteni > Priority: Minor > -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 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 March 2019