January 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-9122) Containers for distributed work manager tests always started in testsuite/integration/manualmode

by Richard Janík (JIRA)

[ https://issues.jboss.org/browse/WFLY-9122?page=com.atlassian.jira.plugin.... ] Richard Janík reassigned WFLY-9122: ----------------------------------- Assignee: Richard Janík (was: Yeray Borges) > Containers for distributed work manager tests always started in testsuite/integration/manualmode > ------------------------------------------------------------------------------------------------ > > Key: WFLY-9122 > URL: https://issues.jboss.org/browse/WFLY-9122 > Project: WildFly > Issue Type: Bug > Components: Test Suite > Reporter: Josef Cacek > Assignee: Richard Janík > > The Arquillian containers {{dwm-container-0}} and {{dwm-container-1}} are always started in the manualmode testsuite module. > It can lead to port conflicts when another test wants to use its own server configuration with port offset 200 or 300. It also adds additional time to execute single test ({{mvn test -Dtest=MyTestCase}}), because these 2 containers has to be started first. > The {{dwm-*}} containers are used by distributed work manager tests in package {{org.jboss.as.test.manualmode.jca.workmanager.distributed}}. > CC [~rjanik] -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9122) Containers for distributed work manager tests always started in testsuite/integration/manualmode

by Richard Janík (JIRA)

[ https://issues.jboss.org/browse/WFLY-9122?page=com.atlassian.jira.plugin.... ] Richard Janík commented on WFLY-9122: ------------------------------------- [~yersan] Since this is my fault, I'd like to take this one. Currently working on it as well as on WFLY-9701. > Containers for distributed work manager tests always started in testsuite/integration/manualmode > ------------------------------------------------------------------------------------------------ > > Key: WFLY-9122 > URL: https://issues.jboss.org/browse/WFLY-9122 > Project: WildFly > Issue Type: Bug > Components: Test Suite > Reporter: Josef Cacek > Assignee: Richard Janík > > The Arquillian containers {{dwm-container-0}} and {{dwm-container-1}} are always started in the manualmode testsuite module. > It can lead to port conflicts when another test wants to use its own server configuration with port offset 200 or 300. It also adds additional time to execute single test ({{mvn test -Dtest=MyTestCase}}), because these 2 containers has to be started first. > The {{dwm-*}} containers are used by distributed work manager tests in package {{org.jboss.as.test.manualmode.jca.workmanager.distributed}}. > CC [~rjanik] -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9701) Dwm tests intermittently failing on Solaris

by Richard Janík (JIRA)

Richard Janík created WFLY-9701: ----------------------------------- Summary: Dwm tests intermittently failing on Solaris Key: WFLY-9701 URL: https://issues.jboss.org/browse/WFLY-9701 Project: WildFly Issue Type: Bug Components: Test Suite Affects Versions: 12.0.0.Alpha1 Reporter: Richard Janík Assignee: Richard Janík I've been alerted to Dwm tests sometimes failing on Solaris. The TeamCity CI shows that this happens with PRs with unrelated fixes and happens in ~4% of runs. Sample fail: https://ci.wildfly.org/viewLog.html?buildId=84840&tab=buildResultsDiv&bui... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2251) Align Test Scenario KIE configuration with BAPL-708

by Jozef Marko (JIRA)

Jozef Marko created DROOLS-2251: ----------------------------------- Summary: Align Test Scenario KIE configuration with BAPL-708 Key: DROOLS-2251 URL: https://issues.jboss.org/browse/DROOLS-2251 Project: Drools Issue Type: Task Components: Test Scenarios Editor Affects Versions: 7.6.0.Final Reporter: Jozef Marko Assignee: Toni Rikkola Test Scenario designer KIE configuration part should be updated to use terms *KIE base* and *KIE session* instead of the *knowledge base* and *knowledge session*. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2250) Align Engine hints in Decision Table column wizard with BAPL-708

by Jozef Marko (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2250?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-2250: -------------------------------- Tester: Jozef Marko > Align Engine hints in Decision Table column wizard with BAPL-708 > ---------------------------------------------------------------- > > Key: DROOLS-2250 > URL: https://issues.jboss.org/browse/DROOLS-2250 > Project: Drools > Issue Type: Task > Components: Guided Decision Table Editor > Affects Versions: 7.6.0.Final > Reporter: Jozef Marko > Assignee: Michael Anstis > Attachments: Screenshot from 2018-01-17 13-49-51.png, Screenshot from 2018-01-17 13-50-37.png > > > Due to the BAPL-708 and the [doc|https://docs.google.com/spreadsheets/d/1kmK92hY3JJp7gZTvLzd0CawaZzvI2...] with new product terminology, we should update the Engine hint shown in the attached screenshots. We should use *decision engine* or *process / engine* instad of *inference engine*, *rules engine* etc. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2250) Align Engine hints in Decision Table column wizard with BAPL-708

by Jozef Marko (JIRA)

Jozef Marko created DROOLS-2250: ----------------------------------- Summary: Align Engine hints in Decision Table column wizard with BAPL-708 Key: DROOLS-2250 URL: https://issues.jboss.org/browse/DROOLS-2250 Project: Drools Issue Type: Task Components: Guided Decision Table Editor Affects Versions: 7.6.0.Final Reporter: Jozef Marko Assignee: Michael Anstis Attachments: Screenshot from 2018-01-17 13-49-51.png, Screenshot from 2018-01-17 13-50-37.png Due to the BAPL-708 and the [doc|https://docs.google.com/spreadsheets/d/1kmK92hY3JJp7gZTvLzd0CawaZzvI2...] with new product terminology, we should update the Engine hint shown in the attached screenshots. We should use *decision engine* or *process / engine* instad of *inference engine*, *rules engine* etc. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9700) Add attribute to model which will indicate that backup is synchronized with live server

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-9700?page=com.atlassian.jira.plugin.... ] Kabir Khan deleted WFLY-9700: ----------------------------- > Add attribute to model which will indicate that backup is synchronized with live server > ---------------------------------------------------------------------------------------- > > Key: WFLY-9700 > URL: https://issues.jboss.org/browse/WFLY-9700 > Project: WildFly > Issue Type: Feature Request > Reporter: Miroslav Novak > Assignee: Jeff Mesnil > Priority: Critical > > If HA is configured with replicated journal then it takes some time to backup to synchronize with live server. Once backup is in sync with live then following information appears in server.log: > {code} > 13:20:00,739 INFO [org.apache.activemq.artemis.core.server] (Thread-3 (ActiveMQ-client-netty-threads-457000966)) AMQ221024: Backup server ActiveMQServerImpl::serverUUID=bc015b34-fd73-11e5-80ca-1b35f669abb8 is synchronized with live-server. > 13:20:01,500 INFO [org.apache.activemq.artemis.core.server] (Thread-2 (ActiveMQ-server-org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl$2@41f992ab-83559664)) AMQ221031: backup announced > {code} > Reading server logs to see whether backup is in sync is not convinient and user friendly way. Could we add this information to model so it can be detected through CLI command? > New attribute with name {{synchronized-with-live}} should be added to {{/subsystem=messaging-activemq/server=default/ha-policy=replication-slave}} > This information can be gathered by calling: {{SharedNothingBackupActivation.isRemoteBackupUpToDate()}} > Additionally we should provide this attribute also in replicated live server in: {{/subsystem=messaging-activemq/server=default/ha-policy=replication-master}} as Administrator might want to know whether live can be shutdown. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9699) Add attribute to model which will indicate that backup is synchronized with live server

by Kabir Khan (JIRA)

Kabir Khan created WFLY-9699: -------------------------------- Summary: Add attribute to model which will indicate that backup is synchronized with live server Key: WFLY-9699 URL: https://issues.jboss.org/browse/WFLY-9699 Project: WildFly Issue Type: Feature Request Components: JMS Affects Versions: 10.0.0.Final Reporter: Miroslav Novak Assignee: Jeff Mesnil Priority: Critical If HA is configured with replicated journal then it takes some time to backup to synchronize with live server. Once backup is in sync with live then following information appears in server.log: {code} 13:20:00,739 INFO [org.apache.activemq.artemis.core.server] (Thread-3 (ActiveMQ-client-netty-threads-457000966)) AMQ221024: Backup server ActiveMQServerImpl::serverUUID=bc015b34-fd73-11e5-80ca-1b35f669abb8 is synchronized with live-server. 13:20:01,500 INFO [org.apache.activemq.artemis.core.server] (Thread-2 (ActiveMQ-server-org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl$2@41f992ab-83559664)) AMQ221031: backup announced {code} Reading server logs to see whether backup is in sync is not convinient and user friendly way. Could we add this information to model so it can be detected through CLI command? New attribute with name {{synchronized-with-live}} should be added to {{/subsystem=messaging-activemq/server=default/ha-policy=replication-slave}} This information can be gathered by calling: {{SharedNothingBackupActivation.isRemoteBackupUpToDate()}} Additionally we should provide this attribute also in replicated live server in: {{/subsystem=messaging-activemq/server=default/ha-policy=replication-master}} as Administrator might want to know whether live can be shutdown. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9700) Add attribute to model which will indicate that backup is synchronized with live server

by Kabir Khan (JIRA)

Kabir Khan created WFLY-9700: -------------------------------- Summary: Add attribute to model which will indicate that backup is synchronized with live server Key: WFLY-9700 URL: https://issues.jboss.org/browse/WFLY-9700 Project: WildFly Issue Type: Feature Request Components: JMS Affects Versions: 10.0.0.Final Reporter: Miroslav Novak Assignee: Jeff Mesnil Priority: Critical If HA is configured with replicated journal then it takes some time to backup to synchronize with live server. Once backup is in sync with live then following information appears in server.log: {code} 13:20:00,739 INFO [org.apache.activemq.artemis.core.server] (Thread-3 (ActiveMQ-client-netty-threads-457000966)) AMQ221024: Backup server ActiveMQServerImpl::serverUUID=bc015b34-fd73-11e5-80ca-1b35f669abb8 is synchronized with live-server. 13:20:01,500 INFO [org.apache.activemq.artemis.core.server] (Thread-2 (ActiveMQ-server-org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl$2@41f992ab-83559664)) AMQ221031: backup announced {code} Reading server logs to see whether backup is in sync is not convinient and user friendly way. Could we add this information to model so it can be detected through CLI command? New attribute with name {{synchronized-with-live}} should be added to {{/subsystem=messaging-activemq/server=default/ha-policy=replication-slave}} This information can be gathered by calling: {{SharedNothingBackupActivation.isRemoteBackupUpToDate()}} Additionally we should provide this attribute also in replicated live server in: {{/subsystem=messaging-activemq/server=default/ha-policy=replication-master}} as Administrator might want to know whether live can be shutdown. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9696) Provide minimalistic profile for Artemis backup configuration

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-9696?page=com.atlassian.jira.plugin.... ] Kabir Khan deleted WFLY-9696: ----------------------------- > Provide minimalistic profile for Artemis backup configuration > ------------------------------------------------------------- > > Key: WFLY-9696 > URL: https://issues.jboss.org/browse/WFLY-9696 > Project: WildFly > Issue Type: Feature Request > Reporter: Miroslav Novak > Assignee: Jeff Mesnil > > If Artemis is configured as dedicated backup, no deployments like MDB,EJB,Servlets should be deployed to it. It should serve to its purpose which is to wait for Wildfly 10 with Artemis configured as live to fail. > We should provide minimalistic configuration for Wildfly serving purely as Artemis backup server. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 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 2018