January 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (SWSQE-234) Scalability Testing on Configurations (Number of Services on Mesh)

by Guilherme Baufaker Rêgo (Jira)

[ https://issues.jboss.org/browse/SWSQE-234?page=com.atlassian.jira.plugin.... ] Guilherme Baufaker Rêgo resolved SWSQE-234. ------------------------------------------- Resolution: Out of Date > Scalability Testing on Configurations (Number of Services on Mesh) > ------------------------------------------------------------------ > > Key: SWSQE-234 > URL: https://issues.jboss.org/browse/SWSQE-234 > Project: Kiali QE > Issue Type: Story > Reporter: Guilherme Baufaker Rêgo > Assignee: Guilherme Baufaker Rêgo > Priority: Major > > As an administrator, I want to know what is "theoretical" limit of test meshes configurations (number of services, versions) that can be displayed on Kiali UI. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3556) 'update' works differently than 'modify' when using dialect "mvel" with property reactive

by Mario Fusco (Jira)

[ https://issues.jboss.org/browse/DROOLS-3556?page=com.atlassian.jira.plugi... ] Mario Fusco updated DROOLS-3556: -------------------------------- Sprint: 2019 Week 02-04 > 'update' works differently than 'modify' when using dialect "mvel" with property reactive > ------------------------------------------------------------------------------------------ > > Key: DROOLS-3556 > URL: https://issues.jboss.org/browse/DROOLS-3556 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 7.14.0.Final > Environment: - Red Hat Decision Manager > - 7.2.0 > Reporter: Hiroko Miura > Assignee: Mario Fusco > Priority: Major > Labels: support > Attachments: updatePropertyReactive.zip > > > Behavior of 'update' is different from 'modify' when dialect "mvel" is used with property reactive. > In case of reproducer, when using update() after fact modification, the rule is continuously executed even though the condition no longer match.(i.e. re-evaluation does not work as expected) -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-239) Establish Hardware Scenarios to Test (Footprints)

by Guilherme Baufaker Rêgo (Jira)

[ https://issues.jboss.org/browse/SWSQE-239?page=com.atlassian.jira.plugin.... ] Guilherme Baufaker Rêgo resolved SWSQE-239. ------------------------------------------- Resolution: Duplicate Issue Addressed on https://issues.jboss.org/browse/KIALI-1924 > Establish Hardware Scenarios to Test (Footprints) > -------------------------------------------------- > > Key: SWSQE-239 > URL: https://issues.jboss.org/browse/SWSQE-239 > Project: Kiali QE > Issue Type: Story > Reporter: Guilherme Baufaker Rêgo > Assignee: Guilherme Baufaker Rêgo > Priority: Major > > As an administrator, I want to know what is minimum requirements to run Kiali > As a Kiali Tester, I want to know what is the recommend testing hardware that tests are going to simulate. > Some notes: > Minimum requirements to run Kiali (~ 16gb?) > Action Item: Ask Kevin Corner about customer environment size > On small openshift cluster? > One Namespace with Hundreds Services > Multiple Namespace with Hundreds and 5 Services -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3402) Encoding set in constructor not taking effect

by Tibor Zimányi (Jira)

[ https://issues.jboss.org/browse/DROOLS-3402?page=com.atlassian.jira.plugi... ] Tibor Zimányi updated DROOLS-3402: ---------------------------------- Sprint: 2018 Week 48-50 (was: 2018 Week 48-50, 2019 Week 02-04) > Encoding set in constructor not taking effect > --------------------------------------------- > > Key: DROOLS-3402 > URL: https://issues.jboss.org/browse/DROOLS-3402 > Project: Drools > Issue Type: Bug > Affects Versions: 7.13.0.Final > Reporter: Barnabás Kurucz > Assignee: Tibor Zimányi > Priority: Major > > In my drl file, I'm using German characters such as Umlauts or ß. Thus, I am setting the encoding to UTF-8 with the overloaded constructor when creating the Resource for the Kie File System. However, after firing the rules on the inserted Fact Drools does not seem to apply the specified encoding. I insert the fact, and if the condition is true to that fact it should modify the Action1 (String) attribute of the fact to "Rückfrage" and return the modified fact. However, when I look at the retrieved bean's Action1 attribute I am seeing "RÃ¼ckfrage" instead of "Rückfrage". I tried both UTF-8 and ISO-8859-1 encoding. Any ideas what's wrong? > Drools 7.13 > *KieSessionGenerator*: > public KieSessionGenerator() { > KieServices kieServices = KieServices.Factory.get(); > KieFileSystem kieFileSystem = kieServices.newKieFileSystem(); > kieFileSystem.write(ResourceFactory.newClassPathResource(drlFile, "UTF-8")); > KieBuilder kieBuilder = kieServices.newKieBuilder(kieFileSystem); > kieBuilder.buildAll(); > KieModule kieModule = kieBuilder.getKieModule(); > KieContainer kieContainer = kieServices.newKieContainer(kieModule.getReleaseId()); > kieSession = kieContainer.newKieSession(); > } > *Snippet from DRL:* > rule "813" > when > $bean : Bean(longDesc == "Infektion") > then > $bean.setAction1("Rückfrage"); > end > *Inserting the fact:* > public Bean lookupBean(Bean bean) { > kieSessionGenerator.getKieSession().insert(bean); > kieSessionGenerator.getKieSession().fireAllRules(); > return bean; > } > UPDATE: After some further investigation it looks the issue can be reproduced only when the default system encoding is set to CP-1252. > Since the system default was CP-1252, the JVM was running with that encoding and the KIE Resource also had used this encoding, even though I set UTF-8 in its conctructor. > Once I changed the system default to UTF-8, the special characters (ä, etc.) were shown correctly. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-420) Workaround to expose istio-ingress-gateway and grafana

by Guilherme Baufaker Rêgo (Jira)

[ https://issues.jboss.org/browse/SWSQE-420?page=com.atlassian.jira.plugin.... ] Guilherme Baufaker Rêgo resolved SWSQE-420. ------------------------------------------- Resolution: Done > Workaround to expose istio-ingress-gateway and grafana > ------------------------------------------------------ > > Key: SWSQE-420 > URL: https://issues.jboss.org/browse/SWSQE-420 > Project: Kiali QE > Issue Type: Sub-task > Reporter: Guilherme Baufaker Rêgo > Assignee: Guilherme Baufaker Rêgo > Priority: Major > > - Until an upstream issue is not merged, we will need a workaround to expose istio-ingress-gateway and grafana routes on Openshift. > Upstream Issue: https://github.com/istio/istio/issues/8730 -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10937) Starting WFLY scripts with JDK 11 blows up with ModuleNotFoundException java.se

by Suganya Rajeswaran (Jira)

[ https://issues.jboss.org/browse/WFLY-10937?page=com.atlassian.jira.plugin... ] Suganya Rajeswaran commented on WFLY-10937: ------------------------------------------- I have place set "JAVA_OPTS=%JAVA_OPTS% -add-modules=java.se" after :JAVA_OPTS_SET my understanding is correct? > Starting WFLY scripts with JDK 11 blows up with ModuleNotFoundException java.se > ------------------------------------------------------------------------------- > > Key: WFLY-10937 > URL: https://issues.jboss.org/browse/WFLY-10937 > Project: WildFly > Issue Type: Bug > Components: Scripts > Reporter: Marek Kopecký > Assignee: Richard Opalka > Priority: Blocker > Labels: Java11, blocker-WF14, jdk11 > Fix For: 15.0.0.Beta1, 15.0.0.Final > > Attachments: appclient.conf.bat > > > Starting WFLY scripts with JDK 11 blows up with ModuleNotFoundException java.se > *Affected scripts* > * appclient > * jdr > * wsconsume > * wsprovide > *Example of logs* > {noformat} > [mkopecky@dhcp-10-40-4-197 bin]$ ./jdr.sh > org.jboss.modules.ModuleNotFoundException: java.se > at org.jboss.modules.Module.addPaths(Module.java:1266) > at org.jboss.modules.Module.link(Module.java:1622) > at org.jboss.modules.Module.relinkIfNecessary(Module.java:1650) > at org.jboss.modules.ModuleLoader.loadModule(ModuleLoader.java:296) > at org.jboss.modules.Main.main(Main.java:437) > [mkopecky@dhcp-10-40-4-197 bin]$ > {noformat} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10937) Starting WFLY scripts with JDK 11 blows up with ModuleNotFoundException java.se

by James Perkins (Jira)

[ https://issues.jboss.org/browse/WFLY-10937?page=com.atlassian.jira.plugin... ] James Perkins commented on WFLY-10937: -------------------------------------- Are your {{JAVA_OPTS}} already set by chance? You could try moving that setting below {{:JAVA_OPTS_SET}}. That way even if the {{JAVA_OPTS}} are set it should be set. > Starting WFLY scripts with JDK 11 blows up with ModuleNotFoundException java.se > ------------------------------------------------------------------------------- > > Key: WFLY-10937 > URL: https://issues.jboss.org/browse/WFLY-10937 > Project: WildFly > Issue Type: Bug > Components: Scripts > Reporter: Marek Kopecký > Assignee: Richard Opalka > Priority: Blocker > Labels: Java11, blocker-WF14, jdk11 > Fix For: 15.0.0.Beta1, 15.0.0.Final > > Attachments: appclient.conf.bat > > > Starting WFLY scripts with JDK 11 blows up with ModuleNotFoundException java.se > *Affected scripts* > * appclient > * jdr > * wsconsume > * wsprovide > *Example of logs* > {noformat} > [mkopecky@dhcp-10-40-4-197 bin]$ ./jdr.sh > org.jboss.modules.ModuleNotFoundException: java.se > at org.jboss.modules.Module.addPaths(Module.java:1266) > at org.jboss.modules.Module.link(Module.java:1622) > at org.jboss.modules.Module.relinkIfNecessary(Module.java:1650) > at org.jboss.modules.ModuleLoader.loadModule(ModuleLoader.java:296) > at org.jboss.modules.Main.main(Main.java:437) > [mkopecky@dhcp-10-40-4-197 bin]$ > {noformat} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10937) Starting WFLY scripts with JDK 11 blows up with ModuleNotFoundException java.se

by Suganya Rajeswaran (Jira)

[ https://issues.jboss.org/browse/WFLY-10937?page=com.atlassian.jira.plugin... ] Suganya Rajeswaran commented on WFLY-10937: ------------------------------------------- [^appclient.conf.bat] FYR [~jamezp] > Starting WFLY scripts with JDK 11 blows up with ModuleNotFoundException java.se > ------------------------------------------------------------------------------- > > Key: WFLY-10937 > URL: https://issues.jboss.org/browse/WFLY-10937 > Project: WildFly > Issue Type: Bug > Components: Scripts > Reporter: Marek Kopecký > Assignee: Richard Opalka > Priority: Blocker > Labels: Java11, blocker-WF14, jdk11 > Fix For: 15.0.0.Beta1, 15.0.0.Final > > Attachments: appclient.conf.bat > > > Starting WFLY scripts with JDK 11 blows up with ModuleNotFoundException java.se > *Affected scripts* > * appclient > * jdr > * wsconsume > * wsprovide > *Example of logs* > {noformat} > [mkopecky@dhcp-10-40-4-197 bin]$ ./jdr.sh > org.jboss.modules.ModuleNotFoundException: java.se > at org.jboss.modules.Module.addPaths(Module.java:1266) > at org.jboss.modules.Module.link(Module.java:1622) > at org.jboss.modules.Module.relinkIfNecessary(Module.java:1650) > at org.jboss.modules.ModuleLoader.loadModule(ModuleLoader.java:296) > at org.jboss.modules.Main.main(Main.java:437) > [mkopecky@dhcp-10-40-4-197 bin]$ > {noformat} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10937) Starting WFLY scripts with JDK 11 blows up with ModuleNotFoundException java.se

by Suganya Rajeswaran (Jira)

[ https://issues.jboss.org/browse/WFLY-10937?page=com.atlassian.jira.plugin... ] Suganya Rajeswaran updated WFLY-10937: -------------------------------------- Attachment: appclient.conf.bat > Starting WFLY scripts with JDK 11 blows up with ModuleNotFoundException java.se > ------------------------------------------------------------------------------- > > Key: WFLY-10937 > URL: https://issues.jboss.org/browse/WFLY-10937 > Project: WildFly > Issue Type: Bug > Components: Scripts > Reporter: Marek Kopecký > Assignee: Richard Opalka > Priority: Blocker > Labels: Java11, blocker-WF14, jdk11 > Fix For: 15.0.0.Beta1, 15.0.0.Final > > Attachments: appclient.conf.bat > > > Starting WFLY scripts with JDK 11 blows up with ModuleNotFoundException java.se > *Affected scripts* > * appclient > * jdr > * wsconsume > * wsprovide > *Example of logs* > {noformat} > [mkopecky@dhcp-10-40-4-197 bin]$ ./jdr.sh > org.jboss.modules.ModuleNotFoundException: java.se > at org.jboss.modules.Module.addPaths(Module.java:1266) > at org.jboss.modules.Module.link(Module.java:1622) > at org.jboss.modules.Module.relinkIfNecessary(Module.java:1650) > at org.jboss.modules.ModuleLoader.loadModule(ModuleLoader.java:296) > at org.jboss.modules.Main.main(Main.java:437) > [mkopecky@dhcp-10-40-4-197 bin]$ > {noformat} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3400) [DMN Designer] Data Types - Validate the Data Type name using the logic that the marshaller implements

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-3400?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-3400: -------------------------------- Description: Validate the Data Type name (in the UI) using the same logic as the marshaller(in the backend). h2. Acceptance test - Do not use *--* as default name for itemDefinitions and itemComponents (/) was: Validate the Data Type name (in the UI) using the same logic as the marshaller(in the backend). h2. Acceptance test - Do not use *--* as default name for itemDefinitions and itemComponents > [DMN Designer] Data Types - Validate the Data Type name using the logic that the marshaller implements > ------------------------------------------------------------------------------------------------------ > > Key: DROOLS-3400 > URL: https://issues.jboss.org/browse/DROOLS-3400 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Reporter: Guilherme Carreiro > Assignee: Guilherme Carreiro > Priority: Major > Labels: drools-tools > > Validate the Data Type name (in the UI) using the same logic as the marshaller(in the backend). > h2. Acceptance test > - Do not use *--* as default name for itemDefinitions and itemComponents (/) -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 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 January 2019