October 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-11037) Intermittent Agroal warnings during startup

by Martin Simka (Jira)

[ https://issues.jboss.org/browse/WFLY-11037?page=com.atlassian.jira.plugin... ] Martin Simka commented on WFLY-11037: ------------------------------------- [~lbarreiro] [~kabirkhan] [~jamezp] I think this was fixed by WFLY-11203 > Intermittent Agroal warnings during startup > ------------------------------------------- > > Key: WFLY-11037 > URL: https://issues.jboss.org/browse/WFLY-11037 > Project: WildFly > Issue Type: Bug > Components: Agroal > Affects Versions: 14.0.0.Final > Reporter: Rich DiCroce > Priority: Major > > Sometimes during startup, Agroal spams the log with this: > {code} > 2018-09-18 10:35:46,226 WARN [io.agroal.pool] (Agroal_6738675721) WFLYAG0601: SciQ_DS: Closing connection in incorrect state CHECKED_IN > 2018-09-18 10:35:46,226 WARN [io.agroal.pool] (Agroal_6738675721) WFLYAG0601: SciQ_DS: Closing connection in incorrect state DESTROYED > 2018-09-18 10:35:46,226 WARN [io.agroal.pool] (Agroal_6738675721) WFLYAG0601: SciQ_DS: Closing connection in incorrect state DESTROYED > 2018-09-18 10:35:46,227 WARN [io.agroal.pool] (Agroal_6738675721) WFLYAG0601: SciQ_DS: Closing connection in incorrect state DESTROYED > 2018-09-18 10:35:46,227 WARN [io.agroal.pool] (Agroal_6738675721) WFLYAG0601: SciQ_DS: Closing connection in incorrect state DESTROYED > 2018-09-18 10:35:46,227 WARN [io.agroal.pool] (Agroal_6738675721) WFLYAG0601: SciQ_DS: Closing connection in incorrect state DESTROYED > 2018-09-18 10:35:46,227 WARN [io.agroal.pool] (Agroal_6738675721) WFLYAG0601: SciQ_DS: Closing connection in incorrect state DESTROYED > 2018-09-18 10:35:46,228 WARN [io.agroal.pool] (Agroal_6738675721) WFLYAG0601: SciQ_DS: Closing connection in incorrect state DESTROYED > 2018-09-18 10:35:46,228 WARN [io.agroal.pool] (Agroal_6738675721) WFLYAG0601: SciQ_DS: Closing connection in incorrect state DESTROYED > 2018-09-18 10:35:46,228 WARN [io.agroal.pool] (Agroal_6738675721) WFLYAG0601: SciQ_DS: Closing connection in incorrect state DESTROYED > 2018-09-18 10:35:46,228 WARN [io.agroal.pool] (Agroal_6738675721) WFLYAG0601: SciQ_DS: Closing connection in incorrect state DESTROYED > 2018-09-18 10:35:46,229 WARN [io.agroal.pool] (Agroal_6738675721) WFLYAG0601: SciQ_DS: Closing connection in incorrect state DESTROYED > 2018-09-18 10:35:46,229 WARN [io.agroal.pool] (Agroal_6738675721) WFLYAG0601: SciQ_DS: Closing connection in incorrect state DESTROYED > 2018-09-18 10:35:46,229 WARN [io.agroal.pool] (Agroal_6738675721) WFLYAG0601: SciQ_DS: Closing connection in incorrect state DESTROYED > 2018-09-18 10:35:46,229 WARN [io.agroal.pool] (Agroal_6738675721) WFLYAG0601: SciQ_DS: Closing connection in incorrect state DESTROYED > 2018-09-18 10:35:46,229 WARN [io.agroal.pool] (Agroal_6738675721) WFLYAG0601: SciQ_DS: Closing connection in incorrect state DESTROYED > 2018-09-18 10:35:46,229 WARN [io.agroal.pool] (Agroal_6738675721) WFLYAG0601: SciQ_DS: Closing connection in incorrect state DESTROYED > 2018-09-18 10:35:46,230 WARN [io.agroal.pool] (Agroal_6738675721) WFLYAG0601: SciQ_DS: Closing connection in incorrect state DESTROYED > 2018-09-18 10:35:46,230 WARN [io.agroal.pool] (Agroal_6738675721) WFLYAG0601: SciQ_DS: Closing connection in incorrect state DESTROYED > 2018-09-18 10:35:46,230 WARN [io.agroal.pool] (Agroal_6738675721) WFLYAG0601: SciQ_DS: Closing connection in incorrect state DESTROYED > 2018-09-18 10:35:46,230 WARN [io.agroal.pool] (Agroal_6738675721) WFLYAG0601: SciQ_DS: Closing connection in incorrect state DESTROYED > 2018-09-18 10:35:46,230 WARN [io.agroal.pool] (Agroal_6738675721) WFLYAG0601: SciQ_DS: Closing connection in incorrect state DESTROYED > 2018-09-18 10:35:46,230 WARN [io.agroal.pool] (Agroal_6738675721) WFLYAG0601: SciQ_DS: Closing connection in incorrect state DESTROYED > 2018-09-18 10:35:46,231 WARN [io.agroal.pool] (Agroal_6738675721) WFLYAG0601: SciQ_DS: Closing connection in incorrect state DESTROYED > 2018-09-18 10:35:46,231 WARN [io.agroal.pool] (Agroal_6738675721) WFLYAG0601: SciQ_DS: Closing connection in incorrect state DESTROYED > 2018-09-18 10:35:46,231 WARN [io.agroal.pool] (Agroal_6738675721) WFLYAG0601: SciQ_DS: Closing connection in incorrect state DESTROYED > 2018-09-18 10:35:46,231 WARN [io.agroal.pool] (Agroal_6738675721) WFLYAG0601: SciQ_DS: Closing connection in incorrect state DESTROYED > 2018-09-18 10:35:46,231 WARN [io.agroal.pool] (Agroal_6738675721) WFLYAG0601: SciQ_DS: Closing connection in incorrect state DESTROYED > 2018-09-18 10:35:46,231 WARN [io.agroal.pool] (Agroal_6738675721) WFLYAG0601: SciQ_DS: Closing connection in incorrect state DESTROYED > 2018-09-18 10:35:46,231 WARN [io.agroal.pool] (Agroal_6738675721) WFLYAG0601: SciQ_DS: Closing connection in incorrect state DESTROYED > 2018-09-18 10:35:46,232 WARN [io.agroal.pool] (Agroal_6738675721) WFLYAG0601: SciQ_DS: Closing connection in incorrect state DESTROYED > 2018-09-18 10:35:46,232 WARN [io.agroal.pool] (Agroal_6738675721) WFLYAG0601: SciQ_DS: Closing connection in incorrect state DESTROYED > 2018-09-18 10:35:46,232 WARN [io.agroal.pool] (Agroal_6738675721) WFLYAG0601: SciQ_DS: Closing connection in incorrect state DESTROYED > 2018-09-18 10:35:46,232 WARN [io.agroal.pool] (Agroal_6738675721) WFLYAG0601: SciQ_DS: Closing connection in incorrect state DESTROYED > 2018-09-18 10:35:46,232 WARN [io.agroal.pool] (Agroal_6738675721) WFLYAG0601: SciQ_DS: Closing connection in incorrect state DESTROYED > 2018-09-18 10:35:46,232 WARN [io.agroal.pool] (Agroal_6738675721) WFLYAG0601: SciQ_DS: Closing connection in incorrect state DESTROYED > 2018-09-18 10:35:46,232 WARN [io.agroal.pool] (Agroal_6738675721) WFLYAG0601: SciQ_DS: Closing connection in incorrect state DESTROYED > 2018-09-18 10:35:46,232 WARN [io.agroal.pool] (Agroal_6738675721) WFLYAG0601: SciQ_DS: Closing connection in incorrect state DESTROYED > 2018-09-18 10:35:46,233 WARN [io.agroal.pool] (Agroal_6738675721) WFLYAG0601: SciQ_DS: Closing connection in incorrect state DESTROYED > {code} > I'm not sure why, and it doesn't always happen. > My pool configuration is: > {code} > <connection-pool max-size="${database.maxPool:20}" background-validation="30000" idle-removal="30"/> > {code} > But this also occurs when background-validation and idle-removal are omitted. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3152) [DMN Designer] Context Expression can not be saved

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-3152?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-3152: -------------------------------- Fix Version/s: 7.14.0.Final > [DMN Designer] Context Expression can not be saved > -------------------------------------------------- > > Key: DROOLS-3152 > URL: https://issues.jboss.org/browse/DROOLS-3152 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.14.0.Final > Reporter: Jozef Marko > Assignee: Matteo Mortari > Priority: Blocker > Labels: drools-tools > Fix For: 7.14.0.Final > > Attachments: CE-LEs.dmn, Screenshot from 2018-10-16 15-03-23.png, error.log > > > User can not save DMN diagram if it contains a decision node with *Context* as top level expression. > Spotted during DROOLS-3109 review, however not 100% sure it is the root cause. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-464) Bookinfo installation fails on B18/12

by Hayk Hovsepyan (Jira)

Hayk Hovsepyan created SWSQE-464: ------------------------------------ Summary: Bookinfo installation fails on B18/12 Key: SWSQE-464 URL: https://issues.jboss.org/browse/SWSQE-464 Project: Kiali QE Issue Type: Bug Reporter: Hayk Hovsepyan Assignee: Guilherme Baufaker Rêgo Failing with different param runs: http://jenkins2.bc.jonqe.lab.eng.bos.redhat.com:8080/job/install-bookinfo... http://jenkins2.bc.jonqe.lab.eng.bos.redhat.com:8080/job/install-bookinfo... http://jenkins2.bc.jonqe.lab.eng.bos.redhat.com:8080/job/install-bookinfo... -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3169) [DMN Designer] Last Context Entry differentiation

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-3169?page=com.atlassian.jira.plugi... ] Jozef Marko commented on DROOLS-3169: ------------------------------------- [~manstis] Idea for quick fix, in {{ContextUIModelMapper}} we differentiate what cell we construct depending on cell is from last row or not. Can't we add new {{GridCellImplementation}} similar to {{InformationItemCell}}, that use its own renderer in {{ContextUIModelMapper}}. > [DMN Designer] Last Context Entry differentiation > ------------------------------------------------- > > Key: DROOLS-3169 > URL: https://issues.jboss.org/browse/DROOLS-3169 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Affects Versions: 7.14.0.Final > Reporter: Jozef Marko > Assignee: Michael Anstis > Priority: Major > Labels: drools-tools > Attachments: Screenshot from 2018-10-22 17-35-07.png > > > The last Context Entry, shown in the attachment, should be differentiated to other Context Entries. Currently we differentiate it just by the Name *Default* that user can not change. > We should improve this in one of the following ways: > - Keep name *Default*, change font to italics and use grey background color > - Merge the *Default* and *Value* cells of last entry and remove the name *Default* -- 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 Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-3038?page=com.atlassian.jira.plugi... ] Jozef Marko commented on DROOLS-3038: ------------------------------------- [~manstis] Thanks, yes the file you attached is valid reproducer for the issue, basically any file I created using workbench and set custom data type for some node / column / row. > [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

[JBoss JIRA] (DROOLS-3143) [DMN Designer] DMN unmarshal from 1.1, 1.2; marshal as 1.2

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-3143?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-3143: -------------------------------- Labels: drools-tools (was: ) > [DMN Designer] DMN unmarshal from 1.1, 1.2; marshal as 1.2 > ---------------------------------------------------------- > > Key: DROOLS-3143 > URL: https://issues.jboss.org/browse/DROOLS-3143 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Reporter: Matteo Mortari > Assignee: Matteo Mortari > Priority: Major > Labels: drools-tools > > Unmarshalling side will need to open either 1.1 or 1.2 models. > Marshalling side will need to persist always as 1.2 model. > /cc [~manstis] -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-311) Create a test with External incoming traffic via Ingress gateway

by Guilherme Baufaker Rêgo (Jira)

[ https://issues.jboss.org/browse/SWSQE-311?page=com.atlassian.jira.plugin.... ] Guilherme Baufaker Rêgo resolved SWSQE-311. ------------------------------------------- Assignee: Guilherme Baufaker Rêgo (was: Michael Foley) Resolution: Done Our Kiali Test Mesh and E2E covers this case now. > Create a test with External incoming traffic via Ingress gateway > ---------------------------------------------------------------- > > Key: SWSQE-311 > URL: https://issues.jboss.org/browse/SWSQE-311 > Project: Kiali QE > Issue Type: QE Task > Reporter: viet nguyen > Assignee: Guilherme Baufaker Rêgo > Priority: Major > > Let's say you're running web app on OpenShift with an external route at http://app.mycompnay.com. In order to send traffic to Istio service mesh, the traffic must go through Istio Ingress gateway, not openshift route -> service -> pod. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-311) Create a test with External incoming traffic via Ingress gateway

by Guilherme Baufaker Rêgo (Jira)

[ https://issues.jboss.org/browse/SWSQE-311?page=com.atlassian.jira.plugin.... ] Guilherme Baufaker Rêgo edited comment on SWSQE-311 at 10/22/18 8:56 PM: ------------------------------------------------------------------------- Our Kiali Test Mesh and E2E cover this case now. was (Author: gbaufake): Our Kiali Test Mesh and E2E covers this case now. > Create a test with External incoming traffic via Ingress gateway > ---------------------------------------------------------------- > > Key: SWSQE-311 > URL: https://issues.jboss.org/browse/SWSQE-311 > Project: Kiali QE > Issue Type: QE Task > Reporter: viet nguyen > Assignee: Guilherme Baufaker Rêgo > Priority: Major > > Let's say you're running web app on OpenShift with an external route at http://app.mycompnay.com. In order to send traffic to Istio service mesh, the traffic must go through Istio Ingress gateway, not openshift route -> service -> pod. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-462) Update Istio Upstream Job

by Guilherme Baufaker Rêgo (Jira)

[ https://issues.jboss.org/browse/SWSQE-462?page=com.atlassian.jira.plugin.... ] Guilherme Baufaker Rêgo updated SWSQE-462: ------------------------------------------ Sprint: Kiali Sprint #13 (was: Kiali Sprint #13) > Update Istio Upstream Job > ------------------------- > > Key: SWSQE-462 > URL: https://issues.jboss.org/browse/SWSQE-462 > Project: Kiali QE > Issue Type: Task > Reporter: Guilherme Baufaker Rêgo > Assignee: Guilherme Baufaker Rêgo > Priority: Major > > Istio Upstream job is fixed on Istio 1.0.2 version. > That needs to be updated in order to permit using another versions of istio -- 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 updated SWSQE-463: ------------------------------------------ Sprint: Kiali Sprint #13 (was: Kiali Sprint #13) > 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

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