October 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-4674) Temporary remove background Tab

by Yeser Amer (Jira)

Yeser Amer created DROOLS-4674: ---------------------------------- Summary: Temporary remove background Tab Key: DROOLS-4674 URL: https://issues.jboss.org/browse/DROOLS-4674 Project: Drools Issue Type: Task Reporter: Yeser Amer Assignee: Yeser Amer Fix For: 7.29.0.Final Temporary remove Background Grid tab for 7.29.0 release, considering it is not ready to be used by users -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4484) [DMN Designer] Data Types - Refactor the Data Types list to use a drag and drop mechanism

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-4484?page=com.atlassian.jira.plugi... ] Jozef Marko commented on DROOLS-4484: ------------------------------------- [~karreiro] thank you for acceptance criteria, I miss a case when user drag item outside from a structure, is this supported? > [DMN Designer] Data Types - Refactor the Data Types list to use a drag and drop mechanism > ----------------------------------------------------------------------------------------- > > Key: DROOLS-4484 > URL: https://issues.jboss.org/browse/DROOLS-4484 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Guilherme Gomes > Assignee: Guilherme Gomes > Priority: Major > Labels: drools-tools > Attachments: s1.gif, s2.gif, s3.gif, s4.gif, s5.gif > > > This JIRAs covers all refactoring to apply the drag and drop mechanism (https://issues.jboss.org/browse/DROOLS-4483) into the DMN Data Types list. > *Acceptance criteria:* > - The drag and drop feature must behaves as the following scenarios describe: > -- *Scenario 1:* When users drag tCompany up and it's collapsed, all fields are dragged with tCompany: > !s1.gif|width=400! > -- *Scenario 2:* When users drag tCompany up and it's not collapsed, all fields are dragged with tCompany: > !s2.gif|width=400! > -- *Scenario 3:* When users drag name below of a structured data type (address), the name field is moved as a nested data type: > !s3.gif|width=400! > -- *Scenario 4:* When users drag a new field into the collapsed tCompany, it automatically expands and the new field is added to it: > !s4.gif|width=400! > -- *Scenario 5:* When users drag a data type above or below of another one, the position is persisted in the model: > !s5.gif|width=400! -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4670) Grid values doesn't undos in editor when editor was set on previous version.

by Daniele Zonca (Jira)

[ https://issues.jboss.org/browse/DROOLS-4670?page=com.atlassian.jira.plugi... ] Daniele Zonca reassigned DROOLS-4670: ------------------------------------- Assignee: Yeser Amer (was: Daniele Zonca) > Grid values doesn't undos in editor when editor was set on previous version. > ---------------------------------------------------------------------------- > > Key: DROOLS-4670 > URL: https://issues.jboss.org/browse/DROOLS-4670 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Affects Versions: 7.28.0.Final > Reporter: Anna Dupliak > Assignee: Yeser Amer > Priority: Major > Labels: CustomerFocus > Attachments: Undo.mov > > > [^Undo.mov] See how data in grid restores partially -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-980) Automate DR Subsets Status checks

by Hayk Hovsepyan (Jira)

Hayk Hovsepyan created SWSQE-980: ------------------------------------ Summary: Automate DR Subsets Status checks Key: SWSQE-980 URL: https://issues.jboss.org/browse/SWSQE-980 Project: Kiali QE Issue Type: QE Task Reporter: Hayk Hovsepyan -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12697) Upgrade Jackson2 to 2.10.0

by Alessio Soldano (Jira)

[ https://issues.jboss.org/browse/WFLY-12697?page=com.atlassian.jira.plugin... ] Alessio Soldano reassigned WFLY-12697: -------------------------------------- Assignee: Alessio Soldano (was: Brian Stansberry) > Upgrade Jackson2 to 2.10.0 > -------------------------- > > Key: WFLY-12697 > URL: https://issues.jboss.org/browse/WFLY-12697 > Project: WildFly > Issue Type: Component Upgrade > Reporter: Alessio Soldano > Assignee: Alessio Soldano > Priority: Major > Fix For: 19.0.0.Beta1 > > > https://github.com/FasterXML/jackson/wiki/Jackson-Release-2.10 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12697) Upgrade Jackson2 to 2.10.0

by Alessio Soldano (Jira)

Alessio Soldano created WFLY-12697: -------------------------------------- Summary: Upgrade Jackson2 to 2.10.0 Key: WFLY-12697 URL: https://issues.jboss.org/browse/WFLY-12697 Project: WildFly Issue Type: Component Upgrade Reporter: Alessio Soldano Assignee: Brian Stansberry Fix For: 19.0.0.Beta1 https://github.com/FasterXML/jackson/wiki/Jackson-Release-2.10 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4673) Executable model compilation fails with function call and large input array

by Martin Weiler (Jira)

Martin Weiler created DROOLS-4673: ------------------------------------- Summary: Executable model compilation fails with function call and large input array Key: DROOLS-4673 URL: https://issues.jboss.org/browse/DROOLS-4673 Project: Drools Issue Type: Bug Components: core engine, executable model Affects Versions: 7.28.0.Final Reporter: Martin Weiler Assignee: Luca Molteni A rule with the following RHS fails to compile in the executable model: {noformat} $input.setNo12Count(functions.sumOf(new Object[]{$no1Count_1, $no2Count_1, $no3Count_1, $no4Count_1, $no5Count_1, $no6Count_1, $no7Count_1, $no8Count_1, $no9Count_1, $no10Count_1, $no11Count_1}).intValue()); {noformat} Failure: {noformat} text=cannot find symbol symbol: method execute((drools,$n[...]t); }) {noformat} Compilation is successful if one of the input parameters (eg. {{$no11Count_1}}) is removed. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4672) Executable model compilation fails with function call and large input array

by Martin Weiler (Jira)

[ https://issues.jboss.org/browse/DROOLS-4672?page=com.atlassian.jira.plugi... ] Martin Weiler updated DROOLS-4672: ---------------------------------- Git Pull Request: https://github.com/kiegroup/drools/pull/2602 > Executable model compilation fails with function call and large input array > --------------------------------------------------------------------------- > > Key: DROOLS-4672 > URL: https://issues.jboss.org/browse/DROOLS-4672 > Project: Drools > Issue Type: Bug > Components: core engine, executable model > Affects Versions: 7.28.0.Final > Reporter: Martin Weiler > Assignee: Luca Molteni > Priority: Major > Labels: support > > A rule with the following RHS fails to compile in the executable model: > {noformat} > $input.setNo12Count(functions.sumOf(new Object[]{$no1Count_1, $no2Count_1, $no3Count_1, $no4Count_1, $no5Count_1, $no6Count_1, $no7Count_1, $no8Count_1, $no9Count_1, $no10Count_1, $no11Count_1}).intValue()); > {noformat} > Failure: > {noformat} > text=cannot find symbol > symbol: method execute((drools,$n[...]t); }) > {noformat} > Compilation is successful if one of the input parameters (eg. {{$no11Count_1}}) is removed. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4672) Executable model compilation fails with function call and large input array

by Martin Weiler (Jira)

Martin Weiler created DROOLS-4672: ------------------------------------- Summary: Executable model compilation fails with function call and large input array Key: DROOLS-4672 URL: https://issues.jboss.org/browse/DROOLS-4672 Project: Drools Issue Type: Bug Components: core engine, executable model Affects Versions: 7.28.0.Final Reporter: Martin Weiler Assignee: Luca Molteni A rule with the following RHS fails to compile in the executable model: {noformat} $input.setNo12Count(functions.sumOf(new Object[]{$no1Count_1, $no2Count_1, $no3Count_1, $no4Count_1, $no5Count_1, $no6Count_1, $no7Count_1, $no8Count_1, $no9Count_1, $no10Count_1, $no11Count_1}).intValue()); {noformat} Failure: {noformat} text=cannot find symbol symbol: method execute((drools,$n[...]t); }) {noformat} Compilation is successful if one of the input parameters (eg. {{$no11Count_1}}) is removed. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 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 10/21/19 4:17 PM: ------------------------------------------------------------ That's good to know, [~ropalka]. Thanks for looking into this. [~adamkrajcik] / [~jstourac] Please see the comment above from [~ropalka]. Is QE still able to reproduce this issue? was (Author: fjuma): [~adamkrajcik] / [~jstourac] Please see the comment above from [~ropalka]. Is QE still able to reproduce this issue? > 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: 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. Configure and start server with TLSv1.3 and JDK 11: > {code} > connect > /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, 9 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 October 2019