September 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFWIP-186) PVC access mode is hardcoded to ReadWriteOnce

by Martin Choma (Jira)

[ https://issues.jboss.org/browse/WFWIP-186?page=com.atlassian.jira.plugin.... ] Martin Choma commented on WFWIP-186: ------------------------------------ So Operator will be missing feature of configuring shared storage between pods? User won't be able to share neither ReadWriteMany nor ReadOnlyMany? Do I understand correctly? > PVC access mode is hardcoded to ReadWriteOnce > --------------------------------------------- > > Key: WFWIP-186 > URL: https://issues.jboss.org/browse/WFWIP-186 > Project: WildFly WIP > Issue Type: Bug > Components: OpenShift > Reporter: Martin Choma > Assignee: Jeff Mesnil > Priority: Blocker > > Setting different access mode (ReadWriteMany, ReadOnlyMany) is ignored > [1] https://github.com/wildfly/wildfly-operator/blob/master/pkg/controller/wi... -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4309) [DMN Designer] Search feature - The cell is not highlighted/focused when GDT is on pinned mode

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-4309?page=com.atlassian.jira.plugi... ] Jozef Marko commented on DROOLS-4309: ------------------------------------- [~karreiro] the title and description seems to be in conflict. One says pinned mode, the second one edit mode, please which is correct? > [DMN Designer] Search feature - The cell is not highlighted/focused when GDT is on pinned mode > ---------------------------------------------------------------------------------------------- > > Key: DROOLS-4309 > URL: https://issues.jboss.org/browse/DROOLS-4309 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Reporter: Guilherme Gomes > Assignee: Daniel José dos Santos > Priority: Major > Labels: drools-tools > > When the GDT is on edit mode, the canvas does not move to show the highlighted a cell that's not visible. -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4658) Upgrade jboss-remoting to 5.0.15.Final

by Flavia Rainone (Jira)

[ https://issues.jboss.org/browse/WFCORE-4658?page=com.atlassian.jira.plugi... ] Flavia Rainone commented on WFCORE-4658: ---------------------------------------- Thanks, [~brian.stansberry], I don't know what I was thinking when I created a WFLY Jira :-) > Upgrade jboss-remoting to 5.0.15.Final > -------------------------------------- > > Key: WFCORE-4658 > URL: https://issues.jboss.org/browse/WFCORE-4658 > Project: WildFly Core > Issue Type: Component Upgrade > Reporter: Flavia Rainone > Assignee: Flavia Rainone > Priority: Blocker > Fix For: 10.0.0.Beta7 > > > Upgrade jboss-remoting to 5.0.15.Final -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12188) Option READ_TIMEOUT is ignored

by Flavia Rainone (Jira)

[ https://issues.jboss.org/browse/WFLY-12188?page=com.atlassian.jira.plugin... ] Flavia Rainone commented on WFLY-12188: --------------------------------------- [~brian.stansberry] After some investigation, I figured that the only way that read timeout is being properly set is at Undertow subsystem via: {code} <subsystem xmlns="urn:jboss:domain:undertow:10.0" default-server="default-server" default-virtual-host="default-host" default-servlet-container="default" default-security-domain="other" statistics-enabled="${wildfly.undertow.statistics-enabled:${wildfly.statistics-enabled:false}}"> <buffer-cache name="default"/> <server name="default-server"> <http-listener name="default" socket-binding="http" redirect-socket="https" enable-http2="true" read-timeout="120"/> <https-listener name="https" socket-binding="https" security-realm="ApplicationRealm" enable-http2="true" read-timeout="5000"/> {code} So, for users using {code} <connection uri="remote+http://127.0.0.1:8080" /> {code} or {code} <connection uri="remote://127.0.0.1:8080" /> {code} It is the timeout at http-listener that counts. If using 8443 port, it is the one in https-listener. If the option is passed via: {code} <subsystem xmlns="urn:jboss:domain:remoting:4.0"> <http-connector name="http-remoting-connector" connector-ref="default" security-realm="ApplicationRealm"> <properties> <property name="org.xnio.Options.READ_TIMEOUT" value="100"/> </properties> </http-connector> </subsystem> {code} It is completely ignored, even if the read-timeout config in Undertow http-listener is ommitted, i.e., it is not overwritten, it is plainly ignored. What do you think we should do about this? Just document it, or remove the XNIO Options support from http-connector? Add a warning? > Option READ_TIMEOUT is ignored > ------------------------------ > > Key: WFLY-12188 > URL: https://issues.jboss.org/browse/WFLY-12188 > Project: WildFly > Issue Type: Bug > Components: EJB, Remoting > Affects Versions: 17.0.0.Final > Reporter: Joerg Baesner > Assignee: Flavia Rainone > Priority: Blocker > Labels: blocker-WF18 > > What's the difference of the {{READ_TIMEOUT}} in _ejb3_ subsystem vs. _remoting_ subsystem? See: > {code} > <remote connector-ref="http-remoting-connector" thread-pool-name="default"> > <channel-creation-options> > <option name="READ_TIMEOUT" value="${prop.remoting-connector.read.timeout:20}" type="xnio"/> > <option name="MAX_OUTBOUND_MESSAGES" value="1234" type="remoting"/> > </channel-creation-options> > </remote> > {code} > {code} > <subsystem xmlns="urn:jboss:domain:remoting:4.0"> > <endpoint/> > <http-connector name="http-remoting-connector" connector-ref="default" security-realm="ApplicationRealm"> >  > <properties> > <property name="org.jboss.remoting3.RemotingOptions.HEARTBEAT_INTERVAL" value="5000"/> > <property name="KEEP_ALIVE" value="true"/> > <property name="READ_TIMEOUT" value="10000"/> > <property name="WRITE_TIMEOUT" value="10000"/> > </properties> > </http-connector> > {code} > None of those options work. -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-651) Refactor Kiali Performance Job

by Guilherme Baufaker Rêgo (Jira)

[ https://issues.jboss.org/browse/SWSQE-651?page=com.atlassian.jira.plugin.... ] Guilherme Baufaker Rêgo updated SWSQE-651: ------------------------------------------ Sprint: Kiali Sprint #25, Kiali Sprint #26, Kiali Sprint #27, Kiali Sprint #28 (was: Kiali Sprint #25, Kiali Sprint #26, Kiali Sprint #27) > Refactor Kiali Performance Job > ------------------------------- > > Key: SWSQE-651 > URL: https://issues.jboss.org/browse/SWSQE-651 > Project: Kiali QE > Issue Type: Task > Reporter: Guilherme Baufaker Rêgo > Assignee: Guilherme Baufaker Rêgo > Priority: Major > Labels: performance > > Kiali Performance Job needs to be refactored to reflect changes (https://github.com/kiali/kiali-performance-testing/pull/1) and (https://github.com/kiali/kiali-performance-testing/pull/2) -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-796) Kiali Doc PQI/OKR Metrics

by Guilherme Baufaker Rêgo (Jira)

[ https://issues.jboss.org/browse/SWSQE-796?page=com.atlassian.jira.plugin.... ] Guilherme Baufaker Rêgo updated SWSQE-796: ------------------------------------------ Sprint: Kiali Sprint #26, Kiali Sprint #27, Kiali Sprint #28 (was: Kiali Sprint #26, Kiali Sprint #27) > Kiali Doc PQI/OKR Metrics > ------------------------- > > Key: SWSQE-796 > URL: https://issues.jboss.org/browse/SWSQE-796 > Project: Kiali QE > Issue Type: Story > Reporter: Matthew Mahoney > Assignee: Guilherme Baufaker Rêgo > Priority: Major > Labels: PQI > > Currently Kiali Doc metrics are not represented in Tablue. Work with Kiali Docs folks to identify tests which will generate PQI/OKR metrics. -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12512) Intermittent failures in DynamicJNDIContextEJBInvocationTestCase

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFLY-12512?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFLY-12512: ------------------------------------ Labels: (was: blocker-WF18) > Intermittent failures in DynamicJNDIContextEJBInvocationTestCase > ---------------------------------------------------------------- > > Key: WFLY-12512 > URL: https://issues.jboss.org/browse/WFLY-12512 > Project: WildFly > Issue Type: Bug > Components: EJB > Affects Versions: 18.0.0.Beta1 > Reporter: Brian Stansberry > Assignee: Tomasz Adamski > Priority: Major > Fix For: 18.0.0.Final > > > We're starting to see quite frequent intermittent failures of DynamicJNDIContextEJBInvocationTestCase. > Looking at the history[1] it seems that this first started popping up with the EJB Client Interceptors PR.[2] > [1] https://ci.wildfly.org/project.html?projectId=WF_PullRequest&buildTypeId=... > [2] https://github.com/wildfly/wildfly/pull/12490 > I'm putting Blocker priority on this because it's a potential regression. But if it's not a regression, just a test that needs improvement, please lower the Priority right away, i.e. don't wait to fix the test. -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12512) Intermittent failures in DynamicJNDIContextEJBInvocationTestCase

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFLY-12512?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFLY-12512: ------------------------------------ Priority: Major (was: Blocker) > Intermittent failures in DynamicJNDIContextEJBInvocationTestCase > ---------------------------------------------------------------- > > Key: WFLY-12512 > URL: https://issues.jboss.org/browse/WFLY-12512 > Project: WildFly > Issue Type: Bug > Components: EJB > Affects Versions: 18.0.0.Beta1 > Reporter: Brian Stansberry > Assignee: Tomasz Adamski > Priority: Major > Labels: blocker-WF18 > Fix For: 18.0.0.Final > > > We're starting to see quite frequent intermittent failures of DynamicJNDIContextEJBInvocationTestCase. > Looking at the history[1] it seems that this first started popping up with the EJB Client Interceptors PR.[2] > [1] https://ci.wildfly.org/project.html?projectId=WF_PullRequest&buildTypeId=... > [2] https://github.com/wildfly/wildfly/pull/12490 > I'm putting Blocker priority on this because it's a potential regression. But if it's not a regression, just a test that needs improvement, please lower the Priority right away, i.e. don't wait to fix the test. -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12534) Upgrade Hibernate ORM from 5.3.11 to 5.3.12

by Scott Marlow (Jira)

[ https://issues.jboss.org/browse/WFLY-12534?page=com.atlassian.jira.plugin... ] Scott Marlow updated WFLY-12534: -------------------------------- Description: Hibernate needs private dependencies on JAXB 2.3 API + IMPL. (was: Hibernate needs private dependencies on JAXB API + IMPL.) > Upgrade Hibernate ORM from 5.3.11 to 5.3.12 > ------------------------------------------- > > Key: WFLY-12534 > URL: https://issues.jboss.org/browse/WFLY-12534 > Project: WildFly > Issue Type: Component Upgrade > Components: JPA / Hibernate > Reporter: Gail Badner > Assignee: Gail Badner > Priority: Major > Fix For: 18.0.0.Final > > > Hibernate needs private dependencies on JAXB 2.3 API + IMPL. -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12534) Upgrade Hibernate ORM from 5.3.11 to 5.3.12

by Gail Badner (Jira)

Gail Badner created WFLY-12534: ---------------------------------- Summary: Upgrade Hibernate ORM from 5.3.11 to 5.3.12 Key: WFLY-12534 URL: https://issues.jboss.org/browse/WFLY-12534 Project: WildFly Issue Type: Component Upgrade Components: JPA / Hibernate Reporter: Gail Badner Assignee: Gail Badner Fix For: 18.0.0.Final Hibernate needs private dependencies on JAXB API + IMPL. -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 10 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 September 2019