November 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-4809) DMN v1.3 verify calculation precision from ch10

by Matteo Mortari (Jira)

[ https://issues.jboss.org/browse/DROOLS-4809?page=com.atlassian.jira.plugi... ] Matteo Mortari updated DROOLS-4809: ----------------------------------- Description: In the PDF the minus operand is an "en dash" and not the minus sign --bear in mind this does not allow to copy-paste from the spec's .PDF > DMN v1.3 verify calculation precision from ch10 > ----------------------------------------------- > > Key: DROOLS-4809 > URL: https://issues.jboss.org/browse/DROOLS-4809 > Project: Drools > Issue Type: Task > Components: dmn engine > Reporter: Matteo Mortari > Assignee: Matteo Mortari > Priority: Minor > > In the PDF the minus operand is an "en dash" and not the minus sign --bear in mind this does not allow to copy-paste from the spec's .PDF -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4809) DMN v1.3 verify calculation precision from ch10

by Matteo Mortari (Jira)

Matteo Mortari created DROOLS-4809: -------------------------------------- Summary: DMN v1.3 verify calculation precision from ch10 Key: DROOLS-4809 URL: https://issues.jboss.org/browse/DROOLS-4809 Project: Drools Issue Type: Task Components: dmn engine Reporter: Matteo Mortari Assignee: Matteo Mortari -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-1013) Traffic tab status

by Hayk Hovsepyan (Jira)

[ https://issues.jboss.org/browse/SWSQE-1013?page=com.atlassian.jira.plugin... ] Hayk Hovsepyan resolved SWSQE-1013. ----------------------------------- Resolution: Done > Traffic tab status > ------------------ > > Key: SWSQE-1013 > URL: https://issues.jboss.org/browse/SWSQE-1013 > Project: Kiali QE > Issue Type: QE Task > Reporter: Hayk Hovsepyan > Assignee: Hayk Hovsepyan > Priority: Major > Labels: automation > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4808) [DMN Designer] Time Constraint picker remains shown

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-4808?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-4808: -------------------------------- Priority: Optional (was: Major) > [DMN Designer] Time Constraint picker remains shown > --------------------------------------------------- > > Key: DROOLS-4808 > URL: https://issues.jboss.org/browse/DROOLS-4808 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.31.0.Final > Reporter: Jozef Marko > Assignee: Michael Anstis > Priority: Optional > Labels: drools-tools > Attachments: time-range-2.webm > > > See the attached video, there is scenario, when a timzeone/timeofset picker remains shown. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4808) [DMN Designer] Time Constraint picker remains shown

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-4808?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-4808: -------------------------------- Labels: drools-tools (was: drools-tools kogito-tooling) > [DMN Designer] Time Constraint picker remains shown > --------------------------------------------------- > > Key: DROOLS-4808 > URL: https://issues.jboss.org/browse/DROOLS-4808 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.31.0.Final > Reporter: Jozef Marko > Assignee: Michael Anstis > Priority: Major > Labels: drools-tools > Attachments: time-range-2.webm > > > Issue found during KOGITO-124 review. The Time range constraint dialog is not working properly. See the attached videos. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4808) [DMN Designer] Time Constraint picker remains shown

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-4808?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-4808: -------------------------------- Attachment: (was: time-range-1.webm) > [DMN Designer] Time Constraint picker remains shown > --------------------------------------------------- > > Key: DROOLS-4808 > URL: https://issues.jboss.org/browse/DROOLS-4808 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.31.0.Final > Reporter: Jozef Marko > Assignee: Michael Anstis > Priority: Major > Labels: drools-tools > Attachments: time-range-2.webm > > > Issue found during KOGITO-124 review. The Time range constraint dialog is not working properly. See the attached videos. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4808) [DMN Designer] Time Constraint picker remains shown

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-4808?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-4808: -------------------------------- Description: See the attached video, there is scenario, when a timzeone/timeofset picker remains shown. (was: Issue found during KOGITO-124 review. The Time range constraint dialog is not working properly. See the attached videos.) > [DMN Designer] Time Constraint picker remains shown > --------------------------------------------------- > > Key: DROOLS-4808 > URL: https://issues.jboss.org/browse/DROOLS-4808 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.31.0.Final > Reporter: Jozef Marko > Assignee: Michael Anstis > Priority: Major > Labels: drools-tools > Attachments: time-range-2.webm > > > See the attached video, there is scenario, when a timzeone/timeofset picker remains shown. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4808) [DMN Designer] Time Constraint picker remains shown

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-4808?page=com.atlassian.jira.plugi... ] Jozef Marko moved KOGITO-668 to DROOLS-4808: -------------------------------------------- Project: Drools (was: Kogito) Key: DROOLS-4808 (was: KOGITO-668) Docs QE Status: NEW Component/s: DMN Editor (was: Authoring Tooling) Affects Version/s: 7.31.0.Final (was: 0.6.0) QE Status: NEW > [DMN Designer] Time Constraint picker remains shown > --------------------------------------------------- > > Key: DROOLS-4808 > URL: https://issues.jboss.org/browse/DROOLS-4808 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.31.0.Final > Reporter: Jozef Marko > Assignee: Michael Anstis > Priority: Major > Labels: drools-tools, kogito-tooling > Attachments: time-range-1.webm, time-range-2.webm > > > Issue found during KOGITO-124 review. The Time range constraint dialog is not working properly. See the attached videos. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-1362) NPE from SemaphoreConcurrentLinkedDequeManagedConnectionPool.returnForFrequencyCheck

by Michał Adamczuk (Jira)

[ https://issues.jboss.org/browse/JBJCA-1362?page=com.atlassian.jira.plugin... ] Michał Adamczuk commented on JBJCA-1362: ---------------------------------------- I have the same problem. wildfly 15.0.1 ironjacamar 1.4.11.Final {code} 2019-11-12 23:45:15,776 WARN [org.jboss.jca.core.connectionmanager.pool.validator.ConnectionValidator] (ConnectionValidator) [rid:,fn:,csid:,crid:] IJ000602: ConnectionValidator ignored unexpected runtime exception: java.lang.NullPointerException at java.base/java.util.Objects.requireNonNull(Objects.java:221) at java.base/java.util.concurrent.ConcurrentLinkedDeque.linkLast(ConcurrentLinkedDeque.java:347) at java.base/java.util.concurrent.ConcurrentLinkedDeque.addLast(ConcurrentLinkedDeque.java:840) at org.jboss.ironjacamar.impl@1.4.11.Final//org.jboss.jca.core.connectionmanager.pool.mcp.SemaphoreConcurrentLinkedDequeManagedConnectionPool.returnForFrequencyCheck(SemaphoreConcurrentLinkedDequeManagedConnectionPool.java:1578) at org.jboss.ironjacamar.impl@1.4.11.Final//org.jboss.jca.core.connectionmanager.pool.mcp.SemaphoreConcurrentLinkedDequeManagedConnectionPool.validateConnections(SemaphoreConcurrentLinkedDequeManagedConnectionPool.java:1504) at org.jboss.ironjacamar.impl@1.4.11.Final//org.jboss.jca.core.connectionmanager.pool.validator.ConnectionValidator$ConnectionValidatorRunner.run(ConnectionValidator.java:277) at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) at java.base/java.lang.Thread.run(Thread.java:834) {code} > NPE from SemaphoreConcurrentLinkedDequeManagedConnectionPool.returnForFrequencyCheck > ------------------------------------------------------------------------------------ > > Key: JBJCA-1362 > URL: https://issues.jboss.org/browse/JBJCA-1362 > Project: IronJacamar > Issue Type: Bug > Components: Core > Reporter: Osamu Nagano > Priority: Major > > NPE happens in the ConnectionValidator thread, about once a week on EAP 7.0.7 (IronJacamar 1.3.7.Final-redhat-1). > {code} > 2017-11-23 14:02:49,527 WARN [org.jboss.jca.core.connectionmanager.pool.validator.ConnectionValidator] (ConnectionValidator) IJ000602: ConnectionValidator ignored unexpected runtime exception: java.lang.NullPointerException > at java.util.concurrent.ConcurrentLinkedDeque.checkNotNull(ConcurrentLinkedDeque.java:798) > at java.util.concurrent.ConcurrentLinkedDeque.linkLast(ConcurrentLinkedDeque.java:386) > at java.util.concurrent.ConcurrentLinkedDeque.addLast(ConcurrentLinkedDeque.java:903) > at org.jboss.jca.core.connectionmanager.pool.mcp.SemaphoreConcurrentLinkedDequeManagedConnectionPool.returnForFrequencyCheck(SemaphoreConcurrentLinkedDequeManagedConnectionPool.java:1597) > at org.jboss.jca.core.connectionmanager.pool.mcp.SemaphoreConcurrentLinkedDequeManagedConnectionPool.validateConnections(SemaphoreConcurrentLinkedDequeManagedConnectionPool.java:1523) > at org.jboss.jca.core.connectionmanager.pool.validator.ConnectionValidator$ConnectionValidatorRunner.run(ConnectionValidator.java:277) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > {code} > Configuration: > {code} > <datasource jndi-name="java:/DB1" pool-name="DB1" statistics-enabled="true"> > <connection-url>jdbc:oracle:thin:@ServerA:1521:DB1</connection-url> > <driver-class>oracle.jdbc.OracleDriver</driver-class> > <connection-property name="v$session.program"> > ServerA > </connection-property> > <driver>oracle</driver> > <pool> > <min-pool-size>490</min-pool-size> > <initial-pool-size>490</initial-pool-size> > <max-pool-size>490</max-pool-size> > <prefill>true</prefill> > <allow-multiple-users>false</allow-multiple-users> > </pool> > <security> > <user-name>username</user-name> > <password>password</password> > </security> > <validation> > <check-valid-connection-sql>SELECT 1 FROM DUAL</check-valid-connection-sql> > <validate-on-match>false</validate-on-match> > <background-validation>true</background-validation> > <background-validation-millis>120000</background-validation-millis> > </validation> > <timeout> > <blocking-timeout-millis>3000</blocking-timeout-millis> > <allocation-retry>10</allocation-retry> > <allocation-retry-wait-millis>60000</allocation-retry-wait-millis> > </timeout> > <statement> > <prepared-statement-cache-size>10</prepared-statement-cache-size> > </statement> > </datasource> > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-160) Fix throughput and response time differences between TLS 1.2 and TLS 1.3

by Farah Juma (Jira)

[ https://issues.jboss.org/browse/WFWIP-160?page=com.atlassian.jira.plugin.... ] Farah Juma edited comment on WFWIP-160 at 11/26/19 10:31 AM: ------------------------------------------------------------- [~dmlloyd] Do you have any thoughts on how we could go about solving the problem [~ropalka] mentioned in his [previous comment|https://issues.jboss.org/browse/WFWIP-160?focusedCommentId=138157... was (Author: fjuma): [~dmlloyd] Do you have thoughts on how we could go about solving the problem [~ropalka] mentioned in his [previous comment|https://issues.jboss.org/browse/WFWIP-160?focusedCommentId=138157... > Fix throughput and response time differences between TLS 1.2 and TLS 1.3 > ------------------------------------------------------------------------ > > Key: WFWIP-160 > URL: https://issues.jboss.org/browse/WFWIP-160 > Project: WildFly WIP > Issue Type: Task > Components: Web (Undertow) > Reporter: Farah Juma > Assignee: Richard Opalka > Priority: Blocker > Attachments: jstourac-report.zip, performance-hotspot.png, results-tlsv12.zip, results-tlsv13.zip > > > Performance with TLS 1.3 on WildFly appears to be worse than with TLS 1.2. In particular, throughput is much lower (roughly three times lower) and response time is much higher (roughly three times higher), which is not supposed to be the case. The underlying issue seems to be in Undertow or XNIO, that is the code that actually gets invoked during the TLS handshake process. Looking at CPU time, there is significantly more time being spent in [io.undertow.protocols.ssl.SslConduit$5.run()|https://github.com/undertow-...] with TLS 1.3 than with TLS 1.2. > Steps to reproduce (taken from EAP7-1022): > 1. Build WildFly using the following feature branches or download a QE build of WildFly [here|https://eap-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/undertow-...]: > https://github.com/fjuma/wildfly-elytron/tree/ELY-1706 > https://github.com/fjuma/wildfly-core/tree/WFCORE-4172 (Update the Elytron version in the pom.xml file to use the version built in the previous step) > https://github.com/fjuma/wildfly/tree/WFCORE-4172 (Update the Core version in the pom.xml file to use the version built in the previous step) > 2. Download and unzip JMeter from https://jmeter.apache.org/download_jmeter.cgi > 3. Download attached test plan [TLSv1.3.jmx|https://issues.jboss.org/secure/attachment/12449098/12449098_...] > 4. Start server with JDK11 and configure with TLSv1.3: > {code} > $ JAVA_HOME=/path/to/java/openjdk-11.0.2 <EAP_HOME>/bin/standalone.sh > $ <EAP_HOME>/bin/jboss-cli.sh -c > /subsystem=elytron/key-store=tls13:add(path=keystore.jks,relative-to=jboss.server.config.dir,credential-reference={clear-text=secret},type=JKS) > /subsystem=elytron/key-store=tls13:generate-key-pair(alias=localhost,algorithm=RSA,key-size=1024,validity=365,credential-reference={clear-text=secret},distinguished-name="CN=localhost") > /subsystem=elytron/key-store=tls13:store() > /subsystem=elytron/key-manager=tls13:add(key-store=tls13,credential-reference={clear-text=secret}) > /subsystem=elytron/server-ssl-context=tls13:add(key-manager=tls13,protocols=["TLSv1.3"]) > batch > /subsystem=undertow/server=default-server/https-listener=https:undefine-attribute(name=security-realm) > /subsystem=undertow/server=default-server/https-listener=https:write-attribute(name=ssl-context,value=tls13) > run-batch > reload > {code} > 5. Start jmeter with JDK 11 and downloaded test plan > {code} > export JAVA_HOME=/path/to/java/openjdk-11.0.2; bin/jmeter -n -t TLSv1.3.jmx -e -l tlsv13.log -o results-tlsv13 > {code} > 6. Set server to use TLSv1.2 > {code} > /subsystem=elytron/server-ssl-context=tls13:write-attribute(name=protocols,value=["TLSv1.2"]) > reload > {code} > 7. Repeat same for TLSv1.2 > {code} > export JAVA_HOME=/path/to/java/openjdk-11.0.2; bin/jmeter -n -t TLSv1.3.jmx -e -l tlsv12.log -o results-tlsv12 > {code} > 8. Compare results (there will be an index.html file in the results-tlsv12 and results-tlsv13 directories) -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 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 November 2019