October 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (SWSQE-424) Create Maistra Message Bus Consumer Job

by Guilherme Baufaker Rêgo (Jira)

[ https://issues.jboss.org/browse/SWSQE-424?page=com.atlassian.jira.plugin.... ] Guilherme Baufaker Rêgo updated SWSQE-424: ------------------------------------------ Team: Infrastructure > Create Maistra Message Bus Consumer Job > --------------------------------------- > > Key: SWSQE-424 > URL: https://issues.jboss.org/browse/SWSQE-424 > Project: Kiali QE > Issue Type: Dev Task > Reporter: Matt Mahoney > Assignee: Matt Mahoney > Priority: Major > > This job will: > - Consume the Message Bus Maistra build notice > - Run the Maistra job (deploy Maistra, bookinfo, kiali) > - Traffic to bookinfo > - Run E2E tests -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-30) Run SWS QE Automation tests on SWS and Report the results.

by Guilherme Baufaker Rêgo (Jira)

[ https://issues.jboss.org/browse/SWSQE-30?page=com.atlassian.jira.plugin.s... ] Guilherme Baufaker Rêgo resolved SWSQE-30. ------------------------------------------ Resolution: Done > Run SWS QE Automation tests on SWS and Report the results. > ---------------------------------------------------------- > > Key: SWSQE-30 > URL: https://issues.jboss.org/browse/SWSQE-30 > Project: Kiali QE > Issue Type: Sub-task > Reporter: Hayk Hovsepyan > Assignee: Hayk Hovsepyan > Priority: Major > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-27) Implement CI on SWS Project over Nightly builds and per PR

by Guilherme Baufaker Rêgo (Jira)

[ https://issues.jboss.org/browse/SWSQE-27?page=com.atlassian.jira.plugin.s... ] Guilherme Baufaker Rêgo resolved SWSQE-27. ------------------------------------------ Resolution: Done > Implement CI on SWS Project over Nightly builds and per PR > ---------------------------------------------------------- > > Key: SWSQE-27 > URL: https://issues.jboss.org/browse/SWSQE-27 > Project: Kiali QE > Issue Type: Task > Reporter: Hayk Hovsepyan > Assignee: Hayk Hovsepyan > Priority: Major > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-229) Make Jenkins Job Parameters consistent

by Guilherme Baufaker Rêgo (Jira)

[ https://issues.jboss.org/browse/SWSQE-229?page=com.atlassian.jira.plugin.... ] Guilherme Baufaker Rêgo resolved SWSQE-229. ------------------------------------------- Resolution: Done > Make Jenkins Job Parameters consistent > -------------------------------------- > > Key: SWSQE-229 > URL: https://issues.jboss.org/browse/SWSQE-229 > Project: Kiali QE > Issue Type: Task > Reporter: Matt Mahoney > Assignee: Michael Foley > Priority: Minor > > Currently the Job parameters are inconsistent from one job to another, thus make consistent across all jobs. > Ex: > Some jobs use Kiali Hostname while others use Kiali URL > Some jobs use OS Hostname while others use OS URL > etc. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-289) Create Istio Helm Installation job

by Guilherme Baufaker Rêgo (Jira)

[ https://issues.jboss.org/browse/SWSQE-289?page=com.atlassian.jira.plugin.... ] Guilherme Baufaker Rêgo updated SWSQE-289: ------------------------------------------ Team: Infrastructure > Create Istio Helm Installation job > ---------------------------------- > > Key: SWSQE-289 > URL: https://issues.jboss.org/browse/SWSQE-289 > Project: Kiali QE > Issue Type: Task > Reporter: Hayk Hovsepyan > Assignee: Guilherme Baufaker Rêgo > Priority: Minor > > According to https://istio.io/docs/setup/kubernetes/helm-install/ > New job to install via helm, new jenkins slave with helm installed. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-457) Jenkins Job for Complex Mesh

by Guilherme Baufaker Rêgo (Jira)

[ https://issues.jboss.org/browse/SWSQE-457?page=com.atlassian.jira.plugin.... ] Guilherme Baufaker Rêgo resolved SWSQE-457. ------------------------------------------- Resolution: Done > Jenkins Job for Complex Mesh > ----------------------------- > > Key: SWSQE-457 > URL: https://issues.jboss.org/browse/SWSQE-457 > Project: Kiali QE > Issue Type: QE Task > Reporter: Guilherme Baufaker Rêgo > Assignee: Guilherme Baufaker Rêgo > Priority: Major > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-463) Update Ansible on Jenkins Slaves

by Guilherme Baufaker Rêgo (Jira)

[ https://issues.jboss.org/browse/SWSQE-463?page=com.atlassian.jira.plugin.... ] Guilherme Baufaker Rêgo resolved SWSQE-463. ------------------------------------------- Resolution: Done > Update Ansible on Jenkins Slaves > -------------------------------- > > Key: SWSQE-463 > URL: https://issues.jboss.org/browse/SWSQE-463 > Project: Kiali QE > Issue Type: Task > Reporter: Guilherme Baufaker Rêgo > Assignee: Guilherme Baufaker Rêgo > Priority: Major > > Ansible is on 2.7 but Jenkins slaves still on 2.4 -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11036) Shutdown hangs if WAR is distributable and uses SSE

by Rich DiCroce (Jira)

[ https://issues.jboss.org/browse/WFLY-11036?page=com.atlassian.jira.plugin... ] Rich DiCroce commented on WFLY-11036: ------------------------------------- I'll see what I can do but you might be waiting a while. I have a lot of other tasks taking priority right now. > Shutdown hangs if WAR is distributable and uses SSE > --------------------------------------------------- > > Key: WFLY-11036 > URL: https://issues.jboss.org/browse/WFLY-11036 > Project: WildFly > Issue Type: Bug > Components: Clustering, Web (Undertow) > Affects Versions: 14.0.0.Final > Reporter: Rich DiCroce > Assignee: Paul Ferraro > Priority: Major > > I have an application (WAR) that uses server-sent events (as standardized in JAX-RS 2.1). The application is also marked as <distributable/> in web.xml. If anything actually opens a SSE channel, WildFly hangs during shutdown. > The culprit appears to be DistributableSessionManager. See the below thread dump, taken during a hung shutdown. DSM is coded to wait up to getDefaultMaxInactiveInterval() seconds in its stop() method, and the default is 30 minutes unless configured otherwise. That's why shutdown hangs, although I don't know what it's waiting for. > If I remove <distributable/> from web.xml, shutdown happens normally. > {code} > "ServerService Thread Pool -- 45" #154 prio=5 os_prio=0 tid=0x000000002bc1a800 nid=0x115e8 waiting on condition [0x0000000035c5e000] > java.lang.Thread.State: TIMED_WAITING (parking) > at sun.misc.Unsafe.park(Native Method) > - parking to wait for <0x00000000fb4bcc98> (a java.util.concurrent.locks.StampedLock) > at java.util.concurrent.locks.StampedLock.acquireWrite(StampedLock.java:1119) > at java.util.concurrent.locks.StampedLock.tryWriteLock(StampedLock.java:394) > at org.wildfly.clustering.web.undertow.session.DistributableSessionManager.stop(DistributableSessionManager.java:98) > - locked <0x00000000fb446c70> (a org.wildfly.clustering.web.undertow.session.DistributableSessionManager) > at io.undertow.servlet.core.DeploymentManagerImpl$3.call(DeploymentManagerImpl.java:617) > at io.undertow.servlet.core.DeploymentManagerImpl$3.call(DeploymentManagerImpl.java:607) > at io.undertow.servlet.core.ServletRequestContextThreadSetupAction$1.call(ServletRequestContextThreadSetupAction.java:42) > at io.undertow.servlet.core.ContextClassLoaderSetupAction$1.call(ContextClassLoaderSetupAction.java:43) > at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1502) > at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction$$Lambda$920/1245185678.call(Unknown Source) > at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1502) > at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction$$Lambda$920/1245185678.call(Unknown Source) > at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1502) > at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction$$Lambda$920/1245185678.call(Unknown Source) > at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1502) > at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction$$Lambda$920/1245185678.call(Unknown Source) > at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1502) > at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction$$Lambda$920/1245185678.call(Unknown Source) > at io.undertow.servlet.core.DeploymentManagerImpl.stop(DeploymentManagerImpl.java:621) > at org.wildfly.extension.undertow.deployment.UndertowDeploymentService.stopContext(UndertowDeploymentService.java:135) > at org.wildfly.extension.undertow.deployment.UndertowDeploymentService$2.run(UndertowDeploymentService.java:117) > at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35) > at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985) > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487) > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1378) > at java.lang.Thread.run(Thread.java:748) > at org.jboss.threads.JBossThread.run(JBossThread.java:485) > Locked ownable synchronizers: > - None > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-463) Update Ansible on Jenkins Slaves

by Guilherme Baufaker Rêgo (Jira)

Guilherme Baufaker Rêgo created SWSQE-463: --------------------------------------------- Summary: Update Ansible on Jenkins Slaves Key: SWSQE-463 URL: https://issues.jboss.org/browse/SWSQE-463 Project: Kiali QE Issue Type: Task Reporter: Guilherme Baufaker Rêgo Assignee: Guilherme Baufaker Rêgo Ansible is on 2.7 but Jenkins slaves still on 2.4 -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3038) [DMN Designer] Added type can not be resolved

by Michael Anstis (Jira)

[ https://issues.jboss.org/browse/DROOLS-3038?page=com.atlassian.jira.plugi... ] Michael Anstis commented on DROOLS-3038: ---------------------------------------- [~jomarko] [~karreiro] [~tari_manga] I've attached a DMN file I created following [~jomarko] steps.. IDK if it's the exact same as he used. Importing this file into {{drools-wb-webapp}} (or any of the "kie" workbenches) gives the {{[INFO] 2018-10-22 22:42:17,112 [EJB default - 2] ERROR Unable to resolve type reference 'tNum' on node 'Decision-1'}} error message (following an incremental build in the workbench). > [DMN Designer] Added type can not be resolved > --------------------------------------------- > > Key: DROOLS-3038 > URL: https://issues.jboss.org/browse/DROOLS-3038 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.12.0.Final > Reporter: Jozef Marko > Assignee: Guilherme Carreiro > Priority: Blocker > Labels: drools-tools > Attachments: DROOLS-3038.dmn, Screenshot from 2018-09-26 12-57-20.png, Screenshot from 2018-09-26 12-58-02.png, Screenshot from 2018-09-26 12-58-12.png > > > {{12:53:34,884 ERROR [org.kie.dmn.core.compiler.DMNCompilerImpl] (EJB default - 3) Unable to resolve type reference 'tNum' on node 'Decision-1'}} is error shown to user after reopening DMN model with used new defined item definition. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 9 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 October 2018