January 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (SWSQE-554) Add missing Openshit API calls

by Hayk Hovsepyan (Jira)

[ https://issues.jboss.org/browse/SWSQE-554?page=com.atlassian.jira.plugin.... ] Hayk Hovsepyan commented on SWSQE-554: -------------------------------------- https://github.com/Kiali-QE/kiali-qe-python/pull/135 > Add missing Openshit API calls > ------------------------------ > > Key: SWSQE-554 > URL: https://issues.jboss.org/browse/SWSQE-554 > Project: Kiali QE > Issue Type: Task > Reporter: Hayk Hovsepyan > Assignee: Hayk Hovsepyan > Priority: Major > > Currently there are several areas in UI tests that do not have call to Openshift API for data comparison. > 1. Figure out which calls are missing to Openshift. > 2. Create API call. > 3. Create assertions on that results to compare with UI data. > 4. PR per area (API call). -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3555) Implement cheatsheet for DMN simulation

by Daniele Zonca (Jira)

Daniele Zonca created DROOLS-3555: ------------------------------------- Summary: Implement cheatsheet for DMN simulation Key: DROOLS-3555 URL: https://issues.jboss.org/browse/DROOLS-3555 Project: Drools Issue Type: Task Components: Scenario Simulation and Testing Reporter: Daniele Zonca Assignee: Anna Baker Cheatsheet panel is hardcoded and it is specific for Rule testing and need to be extended for DMN simulations. This means that the content of that panel should be dynamically loaded based on the type of the file Steps 1. Create two i18n entries with Rule and DMN cheatsheet text (RightPanelViewImpl.html) 2. Create new dataField in RightPanelViewImpl for dynamic cheatsheet text loading (~cheatsheetContent or similar) 3. Create a method "initCheatsheet(ScenarioSimulationModel.Type type)" in RightPanelPresenter that based on the value of the parameter set the proper content to the data field 4. Extend ScenarioSimulationEditorPresenter.populateRightPanel() to call the initCheatsheet method on the right panel presenter ( model.getSimulation().getSimulationDescriptor().getType() ) 5. Add tests :-) -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3545) Create test for editingbox classes

by Anna Baker (Jira)

[ https://issues.jboss.org/browse/DROOLS-3545?page=com.atlassian.jira.plugi... ] Anna Baker closed DROOLS-3545. ------------------------------ Resolution: Done > Create test for editingbox classes > ---------------------------------- > > Key: DROOLS-3545 > URL: https://issues.jboss.org/browse/DROOLS-3545 > Project: Drools > Issue Type: Task > Components: Scenario Simulation and Testing > Reporter: Gabriele Cardosi > Assignee: Anna Baker > Priority: Major > > Create tests for classes inside org.drools.workbench.screens.scenariosimulation.client.collectioneditor.editingbox -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11652) Artemis network health check feature not configurable from EAP

by ehsavoie Hugonnet (Jira)

[ https://issues.jboss.org/browse/WFLY-11652?page=com.atlassian.jira.plugin... ] ehsavoie Hugonnet moved JBEAP-16300 to WFLY-11652: -------------------------------------------------- Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-11652 (was: JBEAP-16300) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: JMS (was: ActiveMQ) Affects Version/s: 15.0.1.Final (was: 7.2.0.GA) > Artemis network health check feature not configurable from EAP > -------------------------------------------------------------- > > Key: WFLY-11652 > URL: https://issues.jboss.org/browse/WFLY-11652 > Project: WildFly > Issue Type: Feature Request > Components: JMS > Affects Versions: 15.0.1.Final > Reporter: ehsavoie Hugonnet > Assignee: ehsavoie Hugonnet > Priority: Major > > To help mitigate the possibility of split brain problems Artemis has the ability to ping a configurable list of hosts to check the health of the brokers network connection, this feature is configured using the following parameters: > network-check-period > network-check-timeou > network-check-list > network-check-ping-command > network-check-ping6-command > None of these parameters are available from an EAP configuration. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3536) Update isEditingMode status on cells with CollectionEditor

by Gabriele Cardosi (Jira)

[ https://issues.jboss.org/browse/DROOLS-3536?page=com.atlassian.jira.plugi... ] Gabriele Cardosi resolved DROOLS-3536. -------------------------------------- Resolution: Done > Update isEditingMode status on cells with CollectionEditor > ---------------------------------------------------------- > > Key: DROOLS-3536 > URL: https://issues.jboss.org/browse/DROOLS-3536 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Reporter: Gabriele Cardosi > Assignee: Gabriele Cardosi > Priority: Major > > The "isEditingMode" flag is not cleared when clicking outside the grid. Verified on cell with CollectionEditor -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10380) ThreadPoolExecutor leak under SM due to lack of privileged block

by ehsavoie Hugonnet (Jira)

[ https://issues.jboss.org/browse/WFLY-10380?page=com.atlassian.jira.plugin... ] ehsavoie Hugonnet commented on WFLY-10380: ------------------------------------------ With Artemis upgrade this seems to have been fixed. > ThreadPoolExecutor leak under SM due to lack of privileged block > ---------------------------------------------------------------- > > Key: WFLY-10380 > URL: https://issues.jboss.org/browse/WFLY-10380 > Project: WildFly > Issue Type: Bug > Components: JMS > Reporter: David Lloyd > Assignee: ehsavoie Hugonnet > Priority: Critical > Labels: security-manager > > Still researching the source of these leaks. > The way the leak happens is, a {{java.util.concurrent.ThreadPoolExecutor}} is constructed from an unprivileged context. The pool starts up and threads are created without a problem, however, the thread pool is never shut down. The finalizer runs but since it tries to shut down the pool with an access control context that was captured during construction, it fails because the context did not have the {{modifyThread}} {{RuntimePermission}}, and the thread pool never shuts down. > We need to identify the points where TPEs are being constructed without controlled privileges. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-567) OCP 4.0 provisioning on AWS

by Matt Mahoney (Jira)

[ https://issues.jboss.org/browse/SWSQE-567?page=com.atlassian.jira.plugin.... ] Matt Mahoney commented on SWSQE-567: ------------------------------------ Helpful nodes: 1) confirm that your API key / value is correctly specified in ~/.aws/credentials. It should look something like this: [openshift-qe] aws_access_key_id = AKIAXXXXXXXXXXXXX aws_secret_access_key = XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX Run something on the command line to confirm that: sudo dnf install awscli aws --profile=openshift-qe --region=us-east-2 ec2 describe-vpcs You'll either see a big list of info (good) or a permission denied error. If you get an error, then double check that your credentials file looks similar to the above. Sometimes people accidentally leave off characters or add extra ones. 2) If that fails, you can provision yourself a new API key ID / secret pair. Log into the console and visit: Services --> IAM --> Users --> [your username] --> Security Credentials tab, and you'll see a place to generate a new API key / secret. Once you've done that, place it into your ~/.aws/credentials file, and remove the old API key (because you can only have a maximum of 2). > OCP 4.0 provisioning on AWS > --------------------------- > > Key: SWSQE-567 > URL: https://issues.jboss.org/browse/SWSQE-567 > Project: Kiali QE > Issue Type: Sub-task > Reporter: Matt Mahoney > Assignee: Matt Mahoney > Priority: Major > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11605) Slave Artemis in Wildfly 10.1.0.Final is starting without Master Shutdown - Split brain

by ehsavoie Hugonnet (Jira)

[ https://issues.jboss.org/browse/WFLY-11605?page=com.atlassian.jira.plugin... ] ehsavoie Hugonnet commented on WFLY-11605: ------------------------------------------ Looks like the connection between your 2 servers is not reliable given the number of connection issues. So this could effectively lead to a split brain. PS: WildFly 10 is almost 3 years old and not maintained, you really should proceed to an up to date version. > Slave Artemis in Wildfly 10.1.0.Final is starting without Master Shutdown - Split brain > --------------------------------------------------------------------------------------- > > Key: WFLY-11605 > URL: https://issues.jboss.org/browse/WFLY-11605 > Project: WildFly > Issue Type: Bug > Components: Clustering, JMS > Affects Versions: 10.1.0.Final > Reporter: Srinivas ev > Assignee: Jeff Mesnil > Priority: Blocker > Labels: https://developer.jboss.org/thread/279503 > Attachments: Master and Slave logs.txt, Project component log.txt, Wildfly error abrupt failback.txt > > > Scenario - Master, and Slave Running on 2 VM's. > Master Wildfly - <replication-master cluster-name="my-cluster" group-name="srini-queues-cluster-group" check-for-live-server="true"/> > Slave Wildfly - <replication-slave cluster-name="my-cluster" group-name="srini-queues-cluster-group" allow-failback="false" max-saved-replicated-journal-size="1"/> > PFB below 2 errors. > At this time Slave will start deploying Queues even when Master wildfly is not stopped completely. Both management consoles can be reached. > Ideally, the Master server(Wildfly) should completely stop for Slave to start the deployment of queues and start the replication. > 2019/01/16 19:56:21,118+05:30 ERROR [org.apache.activemq.artemis.core.server] (default I/O-2) AMQ224044: error acknowledging message: java.lang.NullPointer > Exception > at org.apache.activemq.artemis.core.server.impl.ServerConsumerImpl.removeReferenceByID(ServerConsumerImpl.java:811) > 2019/01/16 19:56:21,121+05:30 ERROR [org.apache.activemq.artemis.core.server] (default I/O-2) AMQ224016: Caught exception: ActiveMQIllegalStateException[er > rorType=ILLEGAL_STATE message=null] > at org.apache.activemq.artemis.core.server.impl.ServerConsumerImpl.individualAcknowledge(ServerConsumerImpl.java:772) > at org.apache.activemq.artemis.core.server.impl.ServerSessionImpl.individualAcknowledge(ServerSessionImpl.java:739) > Detailed logs are attached. > At this stage, 1st component in my project pipeline has identified the slave as master now and stick with sending messages to it. Whereas the other components in the pipeline still consuming from Master(based on consumer count). > This caused the break-in message flow. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11605) Slave Artemis in Wildfly 10.1.0.Final is starting without Master Shutdown - Split brain

by ehsavoie Hugonnet (Jira)

[ https://issues.jboss.org/browse/WFLY-11605?page=com.atlassian.jira.plugin... ] ehsavoie Hugonnet reassigned WFLY-11605: ---------------------------------------- Assignee: ehsavoie Hugonnet (was: Jeff Mesnil) > Slave Artemis in Wildfly 10.1.0.Final is starting without Master Shutdown - Split brain > --------------------------------------------------------------------------------------- > > Key: WFLY-11605 > URL: https://issues.jboss.org/browse/WFLY-11605 > Project: WildFly > Issue Type: Bug > Components: Clustering, JMS > Affects Versions: 10.1.0.Final > Reporter: Srinivas ev > Assignee: ehsavoie Hugonnet > Priority: Blocker > Labels: https://developer.jboss.org/thread/279503 > Attachments: Master and Slave logs.txt, Project component log.txt, Wildfly error abrupt failback.txt > > > Scenario - Master, and Slave Running on 2 VM's. > Master Wildfly - <replication-master cluster-name="my-cluster" group-name="srini-queues-cluster-group" check-for-live-server="true"/> > Slave Wildfly - <replication-slave cluster-name="my-cluster" group-name="srini-queues-cluster-group" allow-failback="false" max-saved-replicated-journal-size="1"/> > PFB below 2 errors. > At this time Slave will start deploying Queues even when Master wildfly is not stopped completely. Both management consoles can be reached. > Ideally, the Master server(Wildfly) should completely stop for Slave to start the deployment of queues and start the replication. > 2019/01/16 19:56:21,118+05:30 ERROR [org.apache.activemq.artemis.core.server] (default I/O-2) AMQ224044: error acknowledging message: java.lang.NullPointer > Exception > at org.apache.activemq.artemis.core.server.impl.ServerConsumerImpl.removeReferenceByID(ServerConsumerImpl.java:811) > 2019/01/16 19:56:21,121+05:30 ERROR [org.apache.activemq.artemis.core.server] (default I/O-2) AMQ224016: Caught exception: ActiveMQIllegalStateException[er > rorType=ILLEGAL_STATE message=null] > at org.apache.activemq.artemis.core.server.impl.ServerConsumerImpl.individualAcknowledge(ServerConsumerImpl.java:772) > at org.apache.activemq.artemis.core.server.impl.ServerSessionImpl.individualAcknowledge(ServerSessionImpl.java:739) > Detailed logs are attached. > At this stage, 1st component in my project pipeline has identified the slave as master now and stick with sending messages to it. Whereas the other components in the pipeline still consuming from Master(based on consumer count). > This caused the break-in message flow. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11605) Slave Artemis in Wildfly 10.1.0.Final is starting without Master Shutdown - Split brain

by ehsavoie Hugonnet (Jira)

[ https://issues.jboss.org/browse/WFLY-11605?page=com.atlassian.jira.plugin... ] ehsavoie Hugonnet updated WFLY-11605: ------------------------------------- Priority: Major (was: Blocker) > Slave Artemis in Wildfly 10.1.0.Final is starting without Master Shutdown - Split brain > --------------------------------------------------------------------------------------- > > Key: WFLY-11605 > URL: https://issues.jboss.org/browse/WFLY-11605 > Project: WildFly > Issue Type: Bug > Components: Clustering, JMS > Affects Versions: 10.1.0.Final > Reporter: Srinivas ev > Assignee: ehsavoie Hugonnet > Priority: Major > Labels: https://developer.jboss.org/thread/279503 > Attachments: Master and Slave logs.txt, Project component log.txt, Wildfly error abrupt failback.txt > > > Scenario - Master, and Slave Running on 2 VM's. > Master Wildfly - <replication-master cluster-name="my-cluster" group-name="srini-queues-cluster-group" check-for-live-server="true"/> > Slave Wildfly - <replication-slave cluster-name="my-cluster" group-name="srini-queues-cluster-group" allow-failback="false" max-saved-replicated-journal-size="1"/> > PFB below 2 errors. > At this time Slave will start deploying Queues even when Master wildfly is not stopped completely. Both management consoles can be reached. > Ideally, the Master server(Wildfly) should completely stop for Slave to start the deployment of queues and start the replication. > 2019/01/16 19:56:21,118+05:30 ERROR [org.apache.activemq.artemis.core.server] (default I/O-2) AMQ224044: error acknowledging message: java.lang.NullPointer > Exception > at org.apache.activemq.artemis.core.server.impl.ServerConsumerImpl.removeReferenceByID(ServerConsumerImpl.java:811) > 2019/01/16 19:56:21,121+05:30 ERROR [org.apache.activemq.artemis.core.server] (default I/O-2) AMQ224016: Caught exception: ActiveMQIllegalStateException[er > rorType=ILLEGAL_STATE message=null] > at org.apache.activemq.artemis.core.server.impl.ServerConsumerImpl.individualAcknowledge(ServerConsumerImpl.java:772) > at org.apache.activemq.artemis.core.server.impl.ServerSessionImpl.individualAcknowledge(ServerSessionImpl.java:739) > Detailed logs are attached. > At this stage, 1st component in my project pipeline has identified the slave as master now and stick with sending messages to it. Whereas the other components in the pipeline still consuming from Master(based on consumer count). > This caused the break-in message flow. -- 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