July 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (SWSQE-786) New Job to add a member into ServiceMeshMemberRoll

by Guilherme Baufaker Rêgo (Jira)

[ https://issues.jboss.org/browse/SWSQE-786?page=com.atlassian.jira.plugin.... ] Guilherme Baufaker Rêgo updated SWSQE-786: ------------------------------------------ Sprint: Kiali Sprint #23, Kiali Sprint #25 (was: Kiali Sprint #23) > New Job to add a member into ServiceMeshMemberRoll > -------------------------------------------------- > > Key: SWSQE-786 > URL: https://issues.jboss.org/browse/SWSQE-786 > Project: Kiali QE > Issue Type: QE Task > Reporter: Hayk Hovsepyan > Assignee: Guilherme Baufaker Rêgo > Priority: Major > Labels: infrastructure > > As we have a new Kiali Operator PR#1010 merged, we need a new way to add any namespace into Kiali's accessible ones. > So the best way is to separate that action into a job and call it from any place needed. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-809) Jenkins job to provision OCP 4 in PSI

by Guilherme Baufaker Rêgo (Jira)

[ https://issues.jboss.org/browse/SWSQE-809?page=com.atlassian.jira.plugin.... ] Guilherme Baufaker Rêgo updated SWSQE-809: ------------------------------------------ Sprint: Kiali Sprint #25 (was: Maistra TP sprint 12) > Jenkins job to provision OCP 4 in PSI > ------------------------------------- > > Key: SWSQE-809 > URL: https://issues.jboss.org/browse/SWSQE-809 > Project: Kiali QE > Issue Type: QE Task > Reporter: Filip Brychta > Assignee: Filip Brychta > Priority: Major > Labels: infrastructure > > Manual installation of OCP 4 in PSI is very time-consuming so it would be good to have automation for that. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12184) WFTC is not integrated with http-client and transaction propagation does not work for server to server ejb over HTTP calls

by Kabir Khan (Jira)

[ https://issues.jboss.org/browse/WFLY-12184?page=com.atlassian.jira.plugin... ] Kabir Khan commented on WFLY-12184: ----------------------------------- [~flavia.rainone] [~ochaloup] The http client upgrade has been merged > WFTC is not integrated with http-client and transaction propagation does not work for server to server ejb over HTTP calls > -------------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-12184 > URL: https://issues.jboss.org/browse/WFLY-12184 > Project: WildFly > Issue Type: Bug > Components: EJB > Affects Versions: 17.0.0.Final > Reporter: Ondrej Chaloupka > Assignee: Ondrej Chaloupka > Priority: Major > > The ejb over http (aka. InitialContext lookup using the {{http://}} protocol) should be working fine (see https://issues.jboss.org/browse/WFLY-5029) but the transaction propagation does not work as the http-client provider is not integrated with WFTC. > The integration needs to be fixed. A naive way of fixing this is here: > https://github.com/ochaloup/wildfly/commit/e8e011b9597113a6fd80e9c2b26004... -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12270) Upgrade wildfly-http-client version to 1.0.16.Final

by Kabir Khan (Jira)

[ https://issues.jboss.org/browse/WFLY-12270?page=com.atlassian.jira.plugin... ] Kabir Khan updated WFLY-12270: ------------------------------ Summary: Upgrade wildfly-http-client version to 1.0.16.Final (was: Upgrade wildfly-htt-client version to 1.0.16.Final) > Upgrade wildfly-http-client version to 1.0.16.Final > --------------------------------------------------- > > Key: WFLY-12270 > URL: https://issues.jboss.org/browse/WFLY-12270 > Project: WildFly > Issue Type: Component Upgrade > Reporter: Flavia Rainone > Assignee: Flavia Rainone > Priority: Major > Fix For: 18.0.0.Beta1 > > > Upgrade wildfly-http-client version to 1.0.16.Final -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4298) Drools-wb-webapp: prefer locally built artifacts over remote ones

by Gabriele Cardosi (Jira)

Gabriele Cardosi created DROOLS-4298: ---------------------------------------- Summary: Drools-wb-webapp: prefer locally built artifacts over remote ones Key: DROOLS-4298 URL: https://issues.jboss.org/browse/DROOLS-4298 Project: Drools Issue Type: Enhancement Components: Scenario Simulation and Testing Reporter: Gabriele Cardosi Assignee: Gabriele Cardosi Currently drools-wb-webapp tries to download remotes updated snapshots. Setup maven configure to search before for locally built/installed ones -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4161) Scenario Test: UX for DMN Decision service

by Tao Zhu (Jira)

[ https://issues.jboss.org/browse/DROOLS-4161?page=com.atlassian.jira.plugi... ] Tao Zhu commented on DROOLS-4161: --------------------------------- And about the demo: what about update change the decision service to test after file creation? Do you suggest not to support this feature? [~danielezonca] Shall we add this function to the setting panel as [~kkufova] suggested? > Scenario Test: UX for DMN Decision service > ------------------------------------------ > > Key: DROOLS-4161 > URL: https://issues.jboss.org/browse/DROOLS-4161 > Project: Drools > Issue Type: Task > Components: Scenario Simulation and Testing > Reporter: Daniele Zonca > Assignee: Tao Zhu > Priority: Major > Labels: ScenarioSimulation, UX, UXTeam > > As user I want to test my decision service from a DMN model. > User needs to specify DMN model and decision service name to be tested. > Note: a decision service contains only a subset of decisions so the template (header) need to be updated/recreated or the information needs to be available during template creation -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4553) Logging on IBM Java doesn't create log

by Marek Kopecky (Jira)

[ https://issues.jboss.org/browse/WFCORE-4553?page=com.atlassian.jira.plugi... ] Marek Kopecky commented on WFCORE-4553: --------------------------------------- This is probably duplicated by WFCORE-4143 ... > Logging on IBM Java doesn't create log > -------------------------------------- > > Key: WFCORE-4553 > URL: https://issues.jboss.org/browse/WFCORE-4553 > Project: WildFly Core > Issue Type: Bug > Components: Logging > Environment: * IBM Java 1.8 > * RHEL6 & RHEL7 > Reporter: Vratislav Marek > Assignee: James Perkins > Priority: Major > > On application output found: > {code} > Bad level value for property: handler.CLIFILE.level > {code} > handler.CLIFILE.level is the name of a property from the test property file used in standalone testsuite > Stack trace: > {code} > java.lang.AssertionError > at org.junit.Assert.fail(Assert.java:86) > at org.junit.Assert.assertTrue(Assert.java:41) > at org.junit.Assert.assertTrue(Assert.java:52) > at org.jboss.as.test.integration.management.cli.SilentModeTestCase.checkIfEmpty(SilentModeTestCase.java:152) > at org.jboss.as.test.integration.management.cli.SilentModeTestCase.testLogging(SilentModeTestCase.java:99) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:90) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:55) > at java.lang.reflect.Method.invoke(Method.java:508) > at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50) > at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) > at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47) > at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17) > at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268) > at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26) > at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27) > at org.junit.runners.ParentRunner.run(ParentRunner.java:363) > at org.wildfly.core.testrunner.WildflyTestRunner.run(WildflyTestRunner.java:109) > at org.junit.runners.Suite.runChild(Suite.java:128) > at org.junit.runners.Suite.runChild(Suite.java:27) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268) > at org.junit.runners.ParentRunner.run(ParentRunner.java:363) > at org.apache.maven.surefire.junitcore.JUnitCore.run(JUnitCore.java:55) > at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.createRequestAndRun(JUnitCoreWrapper.java:137) > at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.executeEager(JUnitCoreWrapper.java:107) > at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.execute(JUnitCoreWrapper.java:83) > at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.execute(JUnitCoreWrapper.java:75) > at org.apache.maven.surefire.junitcore.JUnitCoreProvider.invoke(JUnitCoreProvider.java:158) > at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:383) > at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:344) > at org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:125) > at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:417) > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11127) Can not get activemq and undertow subsystem data from HTTP management api

by Lin Gao (Jira)

[ https://issues.jboss.org/browse/WFLY-11127?page=com.atlassian.jira.plugin... ] Lin Gao commented on WFLY-11127: -------------------------------- [~toni.moreno] There is no +*new*+ request format, the request format is supposed to be what "Workaround Description" described from first version of WildFly(8) Please refer to [The native management API|https://docs.jboss.org/author/display/WFLY8/The+native+management+API...]: {code:java} address – the address of the resource to invoke the operation against. This field's must be of ModelType.LIST with each element in the list being a ModelType.PROPERTY. {code} > Can not get activemq and undertow subsystem data from HTTP management api > ------------------------------------------------------------------------- > > Key: WFLY-11127 > URL: https://issues.jboss.org/browse/WFLY-11127 > Project: WildFly > Issue Type: Bug > Components: Management, Web (Undertow) > Affects Versions: 12.0.0.Final > Reporter: Toni Moreno > Assignee: Lin Gao > Priority: Critical > > As described in https://github.com/wildfly/wildfly/issues/11309 > I can not get some subsystems info data with the HTTP management API working with > > ====================================== > "product-version" => "12.0.0.Final", > "product-community-identifier" => "Product", > "product-home" => "/usr/local/wildfly-12.0.0.Final", > "standalone-or-domain-identifier" => "HOST_CONTROLLER", > "host-operating-system" => "Debian GNU/Linux 8 (jessie)}} > =============== > This the a activemq POST request with curl and its error > ---------8<------------------------------------------8<----------------------- > root@snmpcoldev01:~# curl --digest -L -D - http://localhost:9990/management --header "Content-Type: application/json" -d '{"host":"master","server":"server-two","subsystem":"messaging-activemq","server":"default"},"operation":"read-children-resources","child-type":"jms-queue","include-runtime":"true","json.pretty":1,"recursive-depth":2}' -u admin > Enter host password for user 'admin': > HTTP/1.1 401 Unauthorized > Connection: keep-alive > WWW-Authenticate: Digest realm="ManagementRealm", nonce="ABCwnAAANoo77ka2vPx9H1LY0IuT5cmkcn5HWBS88gigGzT786K6qnnpMAk=", opaque="00000000000000000000000000000000", algorithm=MD5, qop=auth > X-Frame-Options: SAMEORIGIN > Content-Length: 77 > Content-Type: text/html > Date: Sat, 02 Jun 2018 08:05:53 GMT > HTTP/1.1 500 Internal Server Error > Connection: keep-alive > X-Frame-Options: SAMEORIGIN > Content-Type: application/json; charset=utf-8 > Content-Length: 103 > Date: Sat, 02 Jun 2018 08:05:53 GMT > "java.io.IOException: org.jboss.dmr.stream.ModelException: Unexpected content following the DMR > --------->8------------------------------------------>8----------------------- > And this the query with the GUI client > [jboss_jms_queue_gui_query|https://user-images.githubusercontent.com/58834...] > Also with undertow subsystem > ---------8<------------------------------------------8<----------------------- > root@snmpcoldev01:~# curl --digest -L -D - http://localhost:9990/management --header "Content-Type: application/json" -d '{"address":{"host":"master","server":"server-two","subsystem":"undertow","server":"default-server","http-listener":"default"},"include-runtime":"true","json.pretty":1,"operation":"read-resource","recursive-depth":0}' -u admin > Enter host password for user 'admin': > HTTP/1.1 401 Unauthorized > Connection: keep-alive > WWW-Authenticate: Digest realm="ManagementRealm", nonce="ABC0jwAAN04NaeQD9tlEeeNzizRu5PGuUY9Adi18uuLUzOM1RZNHWkCqnc4=", opaque="00000000000000000000000000000000", algorithm=MD5, qop=auth > X-Frame-Options: SAMEORIGIN > Content-Length: 77 > Content-Type: text/html > Date: Sat, 02 Jun 2018 08:19:54 GMT > HTTP/1.1 500 Internal Server Error > Connection: keep-alive > X-Frame-Options: SAMEORIGIN > Content-Type: application/json; charset=utf-8 > Content-Length: 302 > Date: Sat, 02 Jun 2018 08:19:54 GMT > { > "outcome" : "failed", > "failure-description" : "WFLYCTL0030: No resource definition is registered for address [\n (\"host\" => \"master\"),\n (\"server\" => \"default-server\"),\n (\"subsystem\" => \"undertow\"),\n (\"http-listener\" => \"default\")\n]", > "rolled-back" : true > } > --------->8------------------------------------------>8----------------------- > Here Image of the GUI management query. > [jboss_undertow_listener_gui_query|https://user-images.githubusercontent.c...] -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4243) Test Scenario: rule scenarios with maps of simple types are failing

by Klara Kufova (Jira)

[ https://issues.jboss.org/browse/DROOLS-4243?page=com.atlassian.jira.plugi... ] Klara Kufova commented on DROOLS-4243: -------------------------------------- [~emmurphy], RHPAM-2244. Please update the corresponding Known Issues section based on the information in the Jira above. > Test Scenario: rule scenarios with maps of simple types are failing > ------------------------------------------------------------------- > > Key: DROOLS-4243 > URL: https://issues.jboss.org/browse/DROOLS-4243 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Reporter: Daniele Zonca > Assignee: Daniele Zonca > Priority: Critical > Labels: ScenarioSimulation, rhpam74releasenote > > Create a map of simple type as value (i.e. Map<String, String>) and try to use it -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4292) executable-model fails with more than 5 arguments query

by Toshiya Kobayashi (Jira)

[ https://issues.jboss.org/browse/DROOLS-4292?page=com.atlassian.jira.plugi... ] Toshiya Kobayashi edited comment on DROOLS-4292 at 7/7/19 11:56 PM: -------------------------------------------------------------------- I'm not sure if having Query*Def.java per query argument number is the only solution. If we cannot make it dynamic (so we will keep the Query*Def approach), the customer requests that at least 10 arguments are acceptable and the limitation is documented. was (Author: tkobayashi): I'm not sure if having Query*Def.java per query argument number is the only solution. If we cannot make it dynamic, the customer requests that at least 10 arguments are acceptable and the limitation is documented. > executable-model fails with more than 5 arguments query > ------------------------------------------------------- > > Key: DROOLS-4292 > URL: https://issues.jboss.org/browse/DROOLS-4292 > Project: Drools > Issue Type: Bug > Components: executable model > Affects Versions: 7.23.0.Final > Reporter: Toshiya Kobayashi > Assignee: Luca Molteni > Priority: Major > Labels: support > > executable-model build fails when a query defined with more than 5 arguments. > for example) > {noformat} > query peeps( String name, int age, long ageLong, int id, String likes ) > Person( name := name, age := age, ageLong := ageLong, id := id, likes := likes ) > end > {noformat} > {noformat} > java.lang.ArrayIndexOutOfBoundsException: 5 > at org.drools.model.QueryDef.getQueryClassByArity(QueryDef.java:30) > at org.drools.modelcompiler.builder.generator.QueryGenerator.getQueryType(QueryGenerator.java:120) > at org.drools.modelcompiler.builder.generator.QueryGenerator.processQueryDef(QueryGenerator.java:42) > at org.drools.modelcompiler.builder.generator.ModelGenerator.generateModel(ModelGenerator.java:143) > at org.drools.modelcompiler.builder.ModelBuilderImpl.compileKnowledgePackages(ModelBuilderImpl.java:147) > at org.drools.modelcompiler.builder.ModelBuilderImpl.buildRules(ModelBuilderImpl.java:97) > at org.drools.modelcompiler.builder.ModelBuilderImpl.buildPackages(ModelBuilderImpl.java:66) > at org.drools.compiler.builder.impl.CompositeKnowledgeBuilderImpl.build(CompositeKnowledgeBuilderImpl.java:108) > at org.drools.compiler.builder.impl.CompositeKnowledgeBuilderImpl.build(CompositeKnowledgeBuilderImpl.java:100) > at org.drools.compiler.kie.builder.impl.AbstractKieProject.buildKnowledgePackages(AbstractKieProject.java:261) > at org.drools.compiler.kie.builder.impl.AbstractKieProject.verify(AbstractKieProject.java:75) > at org.drools.compiler.kie.builder.impl.KieBuilderImpl.buildKieProject(KieBuilderImpl.java:271) > at org.drools.compiler.kie.builder.impl.KieBuilderImpl.buildAll(KieBuilderImpl.java:239) > at org.drools.compiler.kie.builder.impl.KieBuilderImpl.buildAll(KieBuilderImpl.java:208) > at org.drools.compiler.kie.builder.impl.KieBuilderImpl.buildAll(KieBuilderImpl.java:196) > at org.drools.modelcompiler.BaseModelTest.createKieBuilder(BaseModelTest.java:144) > at org.drools.modelcompiler.BaseModelTest.createKieBuilder(BaseModelTest.java:125) > at org.drools.modelcompiler.BaseModelTest.getKieContainer(BaseModelTest.java:114) > at org.drools.modelcompiler.BaseModelTest.getKieContainer(BaseModelTest.java:107) > at org.drools.modelcompiler.BaseModelTest.getKieSession(BaseModelTest.java:103) > at org.drools.modelcompiler.BaseModelTest.getKieSession(BaseModelTest.java:99) > at org.drools.modelcompiler.QueryTest.testQuery5Args(QueryTest.java:884) > {noformat} -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 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 July 2019