July 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (SWSQE-1155) UI Automations Labels for Applications

by Hayk Hovsepyan (Jira)

[ https://issues.redhat.com/browse/SWSQE-1155?page=com.atlassian.jira.plugi... ] Hayk Hovsepyan resolved SWSQE-1155. ----------------------------------- Resolution: Done > UI Automations Labels for Applications > -------------------------------------- > > Key: SWSQE-1155 > URL: https://issues.redhat.com/browse/SWSQE-1155 > Project: Kiali QE > Issue Type: QE Task > Reporter: Hayk Hovsepyan > Assignee: Hayk Hovsepyan > Priority: Major > Labels: automation > > It is commented and TODO: Service name label should be taken from OC. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5485) Move test cases from drools-compiler to drools-test-coverage

by Toshiya Kobayashi (Jira)

[ https://issues.redhat.com/browse/DROOLS-5485?page=com.atlassian.jira.plug... ] Toshiya Kobayashi updated DROOLS-5485: -------------------------------------- Description: Move test cases from drools-compiler to drools-test-coverage/test-compiler-integration so that we can increase the test coverage for executable-model. At the moment, I'm not yet sure how many of the test cases can be moved. Basically DRL based test only. Luca noted: > there are some tests in -compiler that are not supported in the model compiler (I'm thinking about all the ASM/type generation related). That should be left in -compiler and hopefully moved outside like the traits If we find test failures by executable-model, we would spawn new JIRAs to deal with them one-by-one. was: Move test cases from drools-compiler to drools-model-compiler so that we can increase the test coverage for executable-model. At the moment, I'm not yet sure how many of the test cases can be moved. Basically DRL based test only. Luca noted: > there are some tests in -compiler that are not supported in the model compiler (I'm thinking about all the ASM/type generation related). That should be left in -compiler and hopefully moved outside like the traits If we find test failures by executable-model, we would spawn new JIRAs to deal with them one-by-one. > Move test cases from drools-compiler to drools-test-coverage > ------------------------------------------------------------ > > Key: DROOLS-5485 > URL: https://issues.redhat.com/browse/DROOLS-5485 > Project: Drools > Issue Type: Task > Components: core engine, executable model > Affects Versions: 7.39.0.Final > Reporter: Toshiya Kobayashi > Assignee: Toshiya Kobayashi > Priority: Major > > Move test cases from drools-compiler to drools-test-coverage/test-compiler-integration so that we can increase the test coverage for executable-model. > At the moment, I'm not yet sure how many of the test cases can be moved. Basically DRL based test only. > Luca noted: > > there are some tests in -compiler that are not supported in the model compiler (I'm thinking about all the ASM/type generation related). That should be left in -compiler and hopefully moved outside like the traits > If we find test failures by executable-model, we would spawn new JIRAs to deal with them one-by-one. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5485) Move test cases from drools-compiler to drools-test-coverage

by Toshiya Kobayashi (Jira)

[ https://issues.redhat.com/browse/DROOLS-5485?page=com.atlassian.jira.plug... ] Toshiya Kobayashi updated DROOLS-5485: -------------------------------------- Summary: Move test cases from drools-compiler to drools-test-coverage (was: Move test cases from drools-compiler to drools-model-compiler) > Move test cases from drools-compiler to drools-test-coverage > ------------------------------------------------------------ > > Key: DROOLS-5485 > URL: https://issues.redhat.com/browse/DROOLS-5485 > Project: Drools > Issue Type: Task > Components: core engine, executable model > Affects Versions: 7.39.0.Final > Reporter: Toshiya Kobayashi > Assignee: Toshiya Kobayashi > Priority: Major > > Move test cases from drools-compiler to drools-model-compiler so that we can increase the test coverage for executable-model. > At the moment, I'm not yet sure how many of the test cases can be moved. Basically DRL based test only. > Luca noted: > > there are some tests in -compiler that are not supported in the model compiler (I'm thinking about all the ASM/type generation related). That should be left in -compiler and hopefully moved outside like the traits > If we find test failures by executable-model, we would spawn new JIRAs to deal with them one-by-one. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13654) Upgrade wildfly-http-client to 1.1.2.Final

by Tomasz Adamski (Jira)

[ https://issues.redhat.com/browse/WFLY-13654?page=com.atlassian.jira.plugi... ] Tomasz Adamski closed WFLY-13654. --------------------------------- Resolution: Duplicate Issue > Upgrade wildfly-http-client to 1.1.2.Final > ------------------------------------------ > > Key: WFLY-13654 > URL: https://issues.redhat.com/browse/WFLY-13654 > Project: WildFly > Issue Type: Component Upgrade > Components: Web (Undertow) > Reporter: Tomasz Adamski > Assignee: Tomasz Adamski > Priority: Major > > [https://github.com/wildfly/wildfly-http-client/compare/1.1.1.Final...1.1....] -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13654) Upgrade wildfly-http-client to 1.1.2.Final

by Tomasz Adamski (Jira)

[ https://issues.redhat.com/browse/WFLY-13654?page=com.atlassian.jira.plugi... ] Tomasz Adamski updated WFLY-13654: ---------------------------------- Description: [https://github.com/wildfly/wildfly-http-client/compare/1.1.1.Final...1.1....] > Upgrade wildfly-http-client to 1.1.2.Final > ------------------------------------------ > > Key: WFLY-13654 > URL: https://issues.redhat.com/browse/WFLY-13654 > Project: WildFly > Issue Type: Component Upgrade > Components: Web (Undertow) > Reporter: Tomasz Adamski > Assignee: Tomasz Adamski > Priority: Major > > [https://github.com/wildfly/wildfly-http-client/compare/1.1.1.Final...1.1....] -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13654) Upgrade wildfly-http-client to 1.1.2.Final

by Tomasz Adamski (Jira)

Tomasz Adamski created WFLY-13654: ------------------------------------- Summary: Upgrade wildfly-http-client to 1.1.2.Final Key: WFLY-13654 URL: https://issues.redhat.com/browse/WFLY-13654 Project: WildFly Issue Type: Component Upgrade Components: Web (Undertow) Reporter: Tomasz Adamski Assignee: Tomasz Adamski -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13492) Upgrade Wildfly HTTP Client to 1.1.2.Final

by Flavia Rainone (Jira)

[ https://issues.redhat.com/browse/WFLY-13492?page=com.atlassian.jira.plugi... ] Flavia Rainone updated WFLY-13492: ---------------------------------- Summary: Upgrade Wildfly HTTP Client to 1.1.2.Final (was: Upgrade Wildfly HTTP Client to 1.1.1.Final) > Upgrade Wildfly HTTP Client to 1.1.2.Final > ------------------------------------------ > > Key: WFLY-13492 > URL: https://issues.redhat.com/browse/WFLY-13492 > Project: WildFly > Issue Type: Component Upgrade > Reporter: Flavia Rainone > Assignee: Flavia Rainone > Priority: Major > Fix For: 21.0.0.Beta1 > > > Upgrade WildFly HTTP Client to 1.0.18.Final -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13492) Upgrade Wildfly HTTP Client to 1.1.2.Final

by Flavia Rainone (Jira)

[ https://issues.redhat.com/browse/WFLY-13492?page=com.atlassian.jira.plugi... ] Flavia Rainone reassigned WFLY-13492: ------------------------------------- Assignee: Tomasz Adamski (was: Flavia Rainone) > Upgrade Wildfly HTTP Client to 1.1.2.Final > ------------------------------------------ > > Key: WFLY-13492 > URL: https://issues.redhat.com/browse/WFLY-13492 > Project: WildFly > Issue Type: Component Upgrade > Reporter: Flavia Rainone > Assignee: Tomasz Adamski > Priority: Major > Fix For: 21.0.0.Beta1 > > > Upgrade WildFly HTTP Client to 1.1.2.Final -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13492) Upgrade Wildfly HTTP Client to 1.1.2.Final

by Flavia Rainone (Jira)

[ https://issues.redhat.com/browse/WFLY-13492?page=com.atlassian.jira.plugi... ] Flavia Rainone updated WFLY-13492: ---------------------------------- Description: Upgrade WildFly HTTP Client to 1.1.2.Final (was: Upgrade WildFly HTTP Client to 1.0.18.Final) > Upgrade Wildfly HTTP Client to 1.1.2.Final > ------------------------------------------ > > Key: WFLY-13492 > URL: https://issues.redhat.com/browse/WFLY-13492 > Project: WildFly > Issue Type: Component Upgrade > Reporter: Flavia Rainone > Assignee: Flavia Rainone > Priority: Major > Fix For: 21.0.0.Beta1 > > > Upgrade WildFly HTTP Client to 1.1.2.Final -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10749) Artemis with JDBC store on slow or high latency database crashed on: Critical IO Error. Failed to process JDBC Record statements: java.sql.BatchUpdateException: IO Error: Socket read timed out

by Emmanuel Hugonnet (Jira)

[ https://issues.redhat.com/browse/WFLY-10749?page=com.atlassian.jira.plugi... ] Emmanuel Hugonnet updated WFLY-10749: ------------------------------------- Priority: Major (was: Critical) > Artemis with JDBC store on slow or high latency database crashed on: Critical IO Error. Failed to process JDBC Record statements: java.sql.BatchUpdateException: IO Error: Socket read timed out > ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-10749 > URL: https://issues.redhat.com/browse/WFLY-10749 > Project: WildFly > Issue Type: Bug > Components: JMS > Affects Versions: 12.0.0.Final, 13.0.0.Final, 14.0.0.Final, 15.0.0.Beta1 > Reporter: Miroslav Novak > Assignee: Emmanuel Hugonnet > Priority: Major > > Artemis configured with JDBC store is not robust if database is slow/under high load and when there is higher latency to database. Artemis has tendency to shutdown itself on "Critical IO Error" under really low load. It is visible when EAP QE moved Jenkins to Central CI where is higher latency to used Oracle12cR2 database. In following test scenario: > * Start 2 WF/EAP server in cluster. There is queue InQueue and OutQueue deployed on both of the servers. > * Send 10 000 small messages to InQueue to server 1 > * Then deploy MDB on server 2. MDB consumes messages from InQueue and resends to OutQueue > * Wait until MDB processes all messages and check that 10 000 messages is in OutQueue > Result: > Sometimes happens that Artemis in server 1 crashes due to following exception: > {code} > 20:13:45,641 WARN [org.apache.activemq.artemis.jdbc.store.journal.JDBCJournalImpl] (Thread-17 (ActiveMQ-server-org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl$3@4de066d8)) IO Error: Socket read > timed out: java.sql.BatchUpdateException: IO Error: Socket read timed out > at oracle.jdbc.driver.OraclePreparedStatement.executeLargeBatch(OraclePreparedStatement.java:10032) > at oracle.jdbc.driver.T4CPreparedStatement.executeLargeBatch(T4CPreparedStatement.java:1364) > at oracle.jdbc.driver.OraclePreparedStatement.executeBatch(OraclePreparedStatement.java:9839) > at oracle.jdbc.driver.OracleStatementWrapper.executeBatch(OracleStatementWrapper.java:234) > at org.jboss.jca.adapters.jdbc.WrappedStatement.executeBatch(WrappedStatement.java:1180) > at org.apache.activemq.artemis.jdbc.store.journal.JDBCJournalImpl.sync(JDBCJournalImpl.java:228) [artemis-jdbc-store-1.5.5.jbossorg-012.jar:1.5.5.jbossorg-012] > at org.apache.activemq.artemis.jdbc.store.journal.JDBCJournalImpl$JDBCJournalSync.run(JDBCJournalImpl.java:991) [artemis-jdbc-store-1.5.5.jbossorg-012.jar:1.5.5.jbossorg-012] > at org.apache.activemq.artemis.core.server.ActiveMQScheduledComponent$2.run(ActiveMQScheduledComponent.java:284) [artemis-commons-1.5.5.jbossorg-012.jar:1.5.5.jbossorg-012] > at org.apache.activemq.artemis.utils.OrderedExecutorFactory$OrderedExecutor$ExecutorTask.run(OrderedExecutorFactory.java:122) [artemis-commons-1.5.5.jbossorg-012.jar:1.5.5.jbossorg-012] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [rt.jar:1.8.0_171] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [rt.jar:1.8.0_171] > at java.lang.Thread.run(Thread.java:748) [rt.jar:1.8.0_171] > 20:13:45,652 WARN [org.apache.activemq.artemis.core.server] (Thread-17 (ActiveMQ-server-org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl$3@4de066d8)) AMQ222010: Critical IO Error, shutting down the server. file=NULL, message=Critical IO Error. Failed to process JDBC Record statements: java.sql.BatchUpdateException: IO Error: Socket read timed out > at oracle.jdbc.driver.OraclePreparedStatement.executeLargeBatch(OraclePreparedStatement.java:10032) > at oracle.jdbc.driver.T4CPreparedStatement.executeLargeBatch(T4CPreparedStatement.java:1364) > at oracle.jdbc.driver.OraclePreparedStatement.executeBatch(OraclePreparedStatement.java:9839) > at oracle.jdbc.driver.OracleStatementWrapper.executeBatch(OracleStatementWrapper.java:234) > at org.jboss.jca.adapters.jdbc.WrappedStatement.executeBatch(WrappedStatement.java:1180) > at org.apache.activemq.artemis.jdbc.store.journal.JDBCJournalImpl.sync(JDBCJournalImpl.java:228) [artemis-jdbc-store-1.5.5.jbossorg-012.jar:1.5.5.jbossorg-012] > at org.apache.activemq.artemis.jdbc.store.journal.JDBCJournalImpl$JDBCJournalSync.run(JDBCJournalImpl.java:991) [artemis-jdbc-store-1.5.5.jbossorg-012.jar:1.5.5.jbossorg-012] > at org.apache.activemq.artemis.core.server.ActiveMQScheduledComponent$2.run(ActiveMQScheduledComponent.java:284) [artemis-commons-1.5.5.jbossorg-012.jar:1.5.5.jbossorg-012] > at org.apache.activemq.artemis.utils.OrderedExecutorFactory$OrderedExecutor$ExecutorTask.run(OrderedExecutorFactory.java:122) [artemis-commons-1.5.5.jbossorg-012.jar:1.5.5.jbossorg-012] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [rt.jar:1.8.0_171] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [rt.jar:1.8.0_171] > at java.lang.Thread.run(Thread.java:748) [rt.jar:1.8.0_171] > 20:13:45,655 WARN [org.apache.activemq.artemis.jdbc.store.journal.JDBCJournalImpl] (Thread-17 (ActiveMQ-server-org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl$3@4de066d8)) java.sql.SQLRecoverableException: Closed Connection > {code} > This thing can be very frustrating for customers who would rely on JDBC store in production. We should provide more robust solution and guide how to configure JDBC store to avoid this situation. > This problem will arise also when moving to OpenShift which runs in cloud environment with unreliable and slow network to database like Amazon AWS, MS Azure or OpenStack. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 2 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira July 2020