August 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-10711) Implement Health Check so that it can be consumed by OpenShift Console

by Tomas Remes (JIRA)

[ https://issues.jboss.org/browse/WFLY-10711?page=com.atlassian.jira.plugin... ] Tomas Remes updated WFLY-10711: ------------------------------- Tester: (was: Tomas Remes) > Implement Health Check so that it can be consumed by OpenShift Console > ---------------------------------------------------------------------- > > Key: WFLY-10711 > URL: https://issues.jboss.org/browse/WFLY-10711 > Project: WildFly > Issue Type: Feature Request > Reporter: Bilge Ozpeynirci > Assignee: Jeff Mesnil > Labels: OS_Observability > > Implement Health Check so that it can be consumed by OpenShift Console > This should be implemented in manner that is consistent with WildFly Swarm i.e. MicroProfile specifications where applicable. > This requirement can be delivered as Technology Preview for WF 14. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2789) [Guided Rule] Can not validate sounds like

by Jozef Marko (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2789?page=com.atlassian.jira.plugi... ] Jozef Marko reopened DROOLS-2789: --------------------------------- > [Guided Rule] Can not validate sounds like > ------------------------------------------ > > Key: DROOLS-2789 > URL: https://issues.jboss.org/browse/DROOLS-2789 > Project: Drools > Issue Type: Bug > Components: Guided Rule Editor > Affects Versions: 7.9.0.Final > Reporter: Jozef Marko > Assignee: Michael Anstis > Labels: drools-tools > Fix For: 7.10.0.Final > > Attachments: Screenshot from 2018-07-25 10-06-47.png, empty.zip > > > The attached dialog appears if user validates a rule with *soundslike* operator inside. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2789) [Guided Rule] Can not validate sounds like

by Jozef Marko (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2789?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-2789: -------------------------------- Fix Version/s: 7.10.0.Final > [Guided Rule] Can not validate sounds like > ------------------------------------------ > > Key: DROOLS-2789 > URL: https://issues.jboss.org/browse/DROOLS-2789 > Project: Drools > Issue Type: Bug > Components: Guided Rule Editor > Affects Versions: 7.9.0.Final > Reporter: Jozef Marko > Assignee: Michael Anstis > Labels: drools-tools > Fix For: 7.10.0.Final > > Attachments: Screenshot from 2018-07-25 10-06-47.png, empty.zip > > > The attached dialog appears if user validates a rule with *soundslike* operator inside. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2789) [Guided Rule] Can not validate sounds like

by Jozef Marko (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2789?page=com.atlassian.jira.plugi... ] Jozef Marko closed DROOLS-2789. ------------------------------- Resolution: Cannot Reproduce > [Guided Rule] Can not validate sounds like > ------------------------------------------ > > Key: DROOLS-2789 > URL: https://issues.jboss.org/browse/DROOLS-2789 > Project: Drools > Issue Type: Bug > Components: Guided Rule Editor > Affects Versions: 7.9.0.Final > Reporter: Jozef Marko > Assignee: Michael Anstis > Labels: drools-tools > Fix For: 7.10.0.Final > > Attachments: Screenshot from 2018-07-25 10-06-47.png, empty.zip > > > The attached dialog appears if user validates a rule with *soundslike* operator inside. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2789) [Guided Rule] Can not validate sounds like

by Jozef Marko (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2789?page=com.atlassian.jira.plugi... ] Jozef Marko closed DROOLS-2789. ------------------------------- Resolution: Cannot Reproduce > [Guided Rule] Can not validate sounds like > ------------------------------------------ > > Key: DROOLS-2789 > URL: https://issues.jboss.org/browse/DROOLS-2789 > Project: Drools > Issue Type: Bug > Components: Guided Rule Editor > Affects Versions: 7.9.0.Final > Reporter: Jozef Marko > Assignee: Michael Anstis > Labels: drools-tools > Attachments: Screenshot from 2018-07-25 10-06-47.png, empty.zip > > > The attached dialog appears if user validates a rule with *soundslike* operator inside. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2862) Implement add row/ add column commands

by Gabriele Cardosi (JIRA)

Gabriele Cardosi created DROOLS-2862: ---------------------------------------- Summary: Implement add row/ add column commands Key: DROOLS-2862 URL: https://issues.jboss.org/browse/DROOLS-2862 Project: Drools Issue Type: Task Components: Scenario Simulation and Testing Reporter: Gabriele Cardosi Assignee: Gabriele Cardosi Implements command to add row/column. For the moment being, they should be mapped to specific "header" contextual menu items -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2860) Add second level header

by Gabriele Cardosi (JIRA)

Gabriele Cardosi created DROOLS-2860: ---------------------------------------- Summary: Add second level header Key: DROOLS-2860 URL: https://issues.jboss.org/browse/DROOLS-2860 Project: Drools Issue Type: Task Components: Scenario Simulation and Testing Reporter: Gabriele Cardosi Assignee: Gabriele Cardosi Inside the grid, the scenario-specific columns are grouped in two categories: "Given" and "Expected". All the "Given" columns should go below the main "Given" header, and all the "Expected" ones below "Expected". For each column there should be, then, a specific header -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-370) Add Virtual Services and Destination Rules tab Automation tests

by Hayk Hovsepyan (JIRA)

[ https://issues.jboss.org/browse/SWSQE-370?page=com.atlassian.jira.plugin.... ] Hayk Hovsepyan commented on SWSQE-370: -------------------------------------- PR sent https://github.com/Kiali-QE/kiali-qe-python/pull/65 > Add Virtual Services and Destination Rules tab Automation tests > --------------------------------------------------------------- > > Key: SWSQE-370 > URL: https://issues.jboss.org/browse/SWSQE-370 > Project: Kiali QE > Issue Type: QE Task > Reporter: Hayk Hovsepyan > Assignee: Hayk Hovsepyan > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-83) [Artemis 2.x upgrade] javax.jms.InvalidClientIDException: clientID=cts was already set into another connection

by Miroslav Novak (JIRA)

[ https://issues.jboss.org/browse/WFWIP-83?page=com.atlassian.jira.plugin.s... ] Miroslav Novak updated WFWIP-83: -------------------------------- Steps to Reproduce: Following steps will start TCK 7 on your local machine: {code} export ROOT=$PWD git clone http://git.app.eng.bos.redhat.com/git/messaging-thirdparty-testsuite.git cd messaging-thirdparty-testsuite export WORKSPACE=$PWD export MODULE=core20 echo "Run MODULE = ${MODULE}" cd $WORKSPACE/tck7-configuration/amq7/ export BUILD_ZIP_URL=https://mw-messaging-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat... export BUILD_NAME=jboss-eap export AMQ_DOWNLOAD_URL=http://download.eng.brq.redhat.com/devel/candidates/amq/... export BUILD_ZIP_ROOT_DIR=jboss-eap bash -x setup_tck7-eap7_env2.sh jms tck7 ignorethisparameter {code} Once tests starts running kill it and start EAP/WF server manually by: {{sh standalone.sh -c standalone-full-tck7.xml}} Then move to directory with test and run command like: {{ant -Dtest=verifyLookupWithRAElementSpecifiedTest -Dtest.client=Client.java all}} > [Artemis 2.x upgrade] javax.jms.InvalidClientIDException: clientID=cts was already set into another connection > -------------------------------------------------------------------------------------------------------------- > > Key: WFWIP-83 > URL: https://issues.jboss.org/browse/WFWIP-83 > Project: WildFly WIP > Issue Type: Bug > Components: Artemis, JMS > Reporter: Miroslav Novak > Assignee: Martyn Taylor > Priority: Blocker > Labels: activemq, feature-branch-blocker > > There is regression TCK 7 when running WF/EAP with Artemis 2.x resource adapter against AMQ 7.2.0.GA. WF/EAP with Artemis 2.x is last build from [2018-08-06]: > https://mw-messaging-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/EAP-... > There are approximately 200 failures with exception: > {code} > [javatest.batch] ESC[0mESC[0m09:55:10,602 INFO [stdout] (Thread-68) 08-03-2018 09:55:10: SVR-ERROR: javax.jms.InvalidClientIDException: clientID=cts was already set into another connection > [javatest.batch] ESC[0mESC[0m09:55:10,602 INFO [stdout] (Thread-68) at org.apache.activemq.artemis.jms.client.ActiveMQConnection.validateClientID(ActiveMQConnection.java:266) > [javatest.batch] ESC[0mESC[0m09:55:10,602 INFO [stdout] (Thread-68) at org.apache.activemq.artemis.jms.client.ActiveMQConnection.authorize(ActiveMQConnection.java:681) > [javatest.batch] ESC[0mESC[0m09:55:10,603 INFO [stdout] (Thread-68) at org.apache.activemq.artemis.jms.client.ActiveMQConnectionFactory.createConnectionInternal(ActiveMQConnectionFactory.java:849) > [javatest.batch] ESC[0mESC[0m09:55:10,603 INFO [stdout] (Thread-68) at org.apache.activemq.artemis.jms.client.ActiveMQConnectionFactory.createXATopicConnection(ActiveMQConnectionFactory.java:387) > [javatest.batch] ESC[0mESC[0m09:55:10,603 INFO [stdout] (Thread-68) at org.apache.activemq.artemis.ra.ActiveMQRAManagedConnection.setup(ActiveMQRAManagedConnection.java:745) > [javatest.batch] ESC[0mESC[0m09:55:10,604 INFO [stdout] (Thread-68) at org.apache.activemq.artemis.ra.ActiveMQRAManagedConnection.<init>(ActiveMQRAManagedConnection.java:161) > [javatest.batch] ESC[0mESC[0m09:55:10,604 INFO [stdout] (Thread-68) at org.apache.activemq.artemis.ra.ActiveMQRAManagedConnectionFactory.createManagedConnection(ActiveMQRAManagedConnectionFactory.java:151) > [javatest.batch] ESC[0mESC[0m09:55:10,604 INFO [stdout] (Thread-68) at org.jboss.jca.core.connectionmanager.pool.mcp.SemaphoreConcurrentLinkedDequeManagedConnectionPool.createConnectionEventListener(Semaphor > eConcurrentLinkedDequeManagedConnectionPool.java:1326) > [javatest.batch] ESC[0mESC[0m09:55:10,605 INFO [stdout] (Thread-68) at org.jboss.jca.core.connectionmanager.pool.mcp.SemaphoreConcurrentLinkedDequeManagedConnectionPool.getConnection(SemaphoreConcurrentLinke > dDequeManagedConnectionPool.java:499) > [javatest.batch] ESC[0mESC[0m09:55:10,605 INFO [stdout] (Thread-68) at org.jboss.jca.core.connectionmanager.pool.AbstractPool.getSimpleConnection(AbstractPool.java:632) > [javatest.batch] ESC[0mESC[0m09:55:10,605 INFO [stdout] (Thread-68) at org.jboss.jca.core.connectionmanager.pool.AbstractPool.getConnection(AbstractPool.java:604) > [javatest.batch] ESC[0mESC[0m09:55:10,606 INFO [stdout] (Thread-68) at org.jboss.jca.core.connectionmanager.AbstractConnectionManager.getManagedConnection(AbstractConnectionManager.java:624) > [javatest.batch] ESC[0mESC[0m09:55:10,610 INFO [stdout] (Thread-68) at org.jboss.jca.core.connectionmanager.tx.TxConnectionManagerImpl.getManagedConnection(TxConnectionManagerImpl.java:430) > [javatest.batch] ESC[0mESC[0m09:55:10,610 INFO [stdout] (Thread-68) at org.jboss.jca.core.connectionmanager.AbstractConnectionManager.allocateConnection(AbstractConnectionManager.java:789) > [javatest.batch] ESC[0mESC[0m09:55:10,610 INFO [stdout] (Thread-68) at org.apache.activemq.artemis.ra.ActiveMQRASessionFactoryImpl.allocateConnection(ActiveMQRASessionFactoryImpl.java:872) > [javatest.batch] ESC[0mESC[0m09:55:10,611 INFO [stdout] (Thread-68) at org.apache.activemq.artemis.ra.ActiveMQRASessionFactoryImpl.createSession(ActiveMQRASessionFactoryImpl.java:531) > [javatest.batch] ESC[0mESC[0m09:55:10,611 INFO [stdout] (Thread-68) at org.apache.activemq.artemis.ra.ActiveMQRASessionFactoryImpl.createSession(ActiveMQRASessionFactoryImpl.java:746) > [javatest.batch] ESC[0mESC[0m09:55:10,611 INFO [stdout] (Thread-68) at org.apache.activemq.artemis.ra.ActiveMQRASessionFactoryImpl.createSession(ActiveMQRASessionFactoryImpl.java:751) > [javatest.batch] ESC[0mESC[0m09:55:10,612 INFO [stdout] (Thread-68) at org.apache.activemq.artemis.ra.ActiveMQRAConnectionFactoryImpl.validateUser(ActiveMQRAConnectionFactoryImpl.java:475) > [javatest.batch] ESC[0mESC[0m09:55:10,612 INFO [stdout] (Thread-68) at org.apache.activemq.artemis.ra.ActiveMQRAConnectionFactoryImpl.createTopicConnection(ActiveMQRAConnectionFactoryImpl.java:217) > [javatest.batch] ESC[0mESC[0m09:55:10,612 INFO [stdout] (Thread-68) at com.sun.ts.tests.jms.ee.ejbweb.xa.TransactionTests.testInitForT(TransactionTests.java:354) > [javatest.batch] ESC[0mESC[0m09:55:10,613 INFO [stdout] (Thread-68) at com.sun.ts.tests.jms.ee.ejbweb.xa.TransactionTests.Test06(TransactionTests.java:634) > [javatest.batch] ESC[0mESC[0m09:55:10,613 INFO [stdout] (Thread-68) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > [javatest.batch] ESC[0mESC[0m09:55:10,613 INFO [stdout] (Thread-68) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > [javatest.batch] ESC[0mESC[0m09:55:10,613 INFO [stdout] (Thread-68) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > [javatest.batch] ESC[0mESC[0m09:55:10,614 INFO [stdout] (Thread-68) at java.lang.reflect.Method.invoke(Method.java:498) > [javatest.batch] ESC[0mESC[0m09:55:10,614 INFO [stdout] (Thread-68) at com.sun.ts.lib.harness.EETest.run(EETest.java:550) > [javatest.batch] ESC[0mESC[0m09:55:10,614 INFO [stdout] (Thread-68) at com.sun.ts.lib.harness.ServiceEETest.run(ServiceEETest.java:113) > [javatest.batch] ESC[0mESC[0m09:55:10,614 INFO [stdout] (Thread-68) at com.sun.ts.tests.common.vehicle.ejb.EJBVehicle.runTest(EJBVehicle.java:70) > {code} > Note that TCK 7 is passing when trying with current Wildfly master (Artemis 1.5.5.012). > Link to TCK 7 job: > https://eap-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/eap-7.x-third-... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-86) [Artemis 2.x upgrade] Duplicated messages in scenario with stop/start JMS bridge

by Miroslav Novak (JIRA)

[ https://issues.jboss.org/browse/WFWIP-86?page=com.atlassian.jira.plugin.s... ] Miroslav Novak commented on WFWIP-86: ------------------------------------- [~jbertram] Thanks, I've fixed steps to reproduce. ?..between EAP and Wildfly so I changed to test to run EAP & EAP and it failed eventually as well..? Ok, was with EAP 7.1 against EAP 7.1? > [Artemis 2.x upgrade] Duplicated messages in scenario with stop/start JMS bridge > -------------------------------------------------------------------------------- > > Key: WFWIP-86 > URL: https://issues.jboss.org/browse/WFWIP-86 > Project: WildFly WIP > Issue Type: Bug > Components: Artemis > Reporter: Miroslav Novak > Assignee: Martyn Taylor > Priority: Blocker > > There are duplicated messages in scenario where JMS bridge is stopped and started. > Test Scenario: > * Start 2 servers and configure JMS from node-1 to node-3 > * Start sending messages to queue InQueue to node-1 > * Stop JMS bridge using management operation (CLI) > * Wait for 5 sec > * Start JMS bridge using management operation > * Start receiving mesage from node-3 from OutQueue > Expected results: > There are no lost/duplicated mesages. > Actual Result: > Receiver got duplicated messages. > Link to failed Jenkins run: > https://eap-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/eap-7.x-messag... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 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 August 2018