December 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (ELY-1907) Release WildFly Elytron 2.0.0.Alpha6

by Farah Juma (Jira)

[ https://issues.redhat.com/browse/ELY-1907?page=com.atlassian.jira.plugin.... ] Farah Juma resolved ELY-1907. ----------------------------- Resolution: Done > Release WildFly Elytron 2.0.0.Alpha6 > ------------------------------------ > > Key: ELY-1907 > URL: https://issues.redhat.com/browse/ELY-1907 > Project: WildFly Elytron > Issue Type: Release > Reporter: Farah Juma > Assignee: Farah Juma > Priority: Major > Fix For: 2.0.0.Alpha6 > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4869) [DMN Designer] Data Types - Unexpected jump on clicking a row on the datatypes table

by Guilherme Gomes (Jira)

Guilherme Gomes created DROOLS-4869: --------------------------------------- Summary: [DMN Designer] Data Types - Unexpected jump on clicking a row on the datatypes table Key: DROOLS-4869 URL: https://issues.redhat.com/browse/DROOLS-4869 Project: Drools Issue Type: Task Components: DMN Editor Reporter: Guilherme Gomes Assignee: Guilherme Gomes Attachments: steps-to-reproduce.mp4 When users click on a list of that types that has a scroll bar, the screen unexpectedly jumps to a non-related data type. See the steps to reproduce: [^steps-to-reproduce.mp4] -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4773) Upgrade WildFly OpenSSL to 1.0.9.Final

by Farah Juma (Jira)

Farah Juma created WFCORE-4773: ---------------------------------- Summary: Upgrade WildFly OpenSSL to 1.0.9.Final Key: WFCORE-4773 URL: https://issues.redhat.com/browse/WFCORE-4773 Project: WildFly Core Issue Type: Component Upgrade Components: Security Reporter: Farah Juma Assignee: Farah Juma -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12870) Upgrade JBoss JSF API from 3.0.0.SP01 to 3.0.0.SP02

by Ilia Vassilev (Jira)

[ https://issues.redhat.com/browse/WFLY-12870?page=com.atlassian.jira.plugi... ] Ilia Vassilev updated WFLY-12870: --------------------------------- Affects Version/s: (was: 18.0.0.Final) > Upgrade JBoss JSF API from 3.0.0.SP01 to 3.0.0.SP02 > --------------------------------------------------- > > Key: WFLY-12870 > URL: https://issues.redhat.com/browse/WFLY-12870 > Project: WildFly > Issue Type: Component Upgrade > Components: Build System > Reporter: Ilia Vassilev > Assignee: Farah Juma > Priority: Major > Labels: downstream_dependency > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-1026) Service Details - Health - Missing fields

by Hayk Hovsepyan (Jira)

[ https://issues.redhat.com/browse/SWSQE-1026?page=com.atlassian.jira.plugi... ] Hayk Hovsepyan resolved SWSQE-1026. ----------------------------------- Resolution: Done > Service Details - Health - Missing fields > ----------------------------------------- > > Key: SWSQE-1026 > URL: https://issues.redhat.com/browse/SWSQE-1026 > Project: Kiali QE > Issue Type: QE Task > Reporter: Hayk Hovsepyan > Assignee: Hayk Hovsepyan > Priority: Major > Labels: automation > > Automate all the missing fields in Health Overview of Service Details. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12870) Upgrade JBoss JSF API from 3.0.0.SP01 to 3.0.0.SP02

by Ilia Vassilev (Jira)

[ https://issues.redhat.com/browse/WFLY-12870?page=com.atlassian.jira.plugi... ] Ilia Vassilev updated WFLY-12870: --------------------------------- Git Pull Request: (was: https://github.com/wildfly/wildfly/pull/12805) > Upgrade JBoss JSF API from 3.0.0.SP01 to 3.0.0.SP02 > --------------------------------------------------- > > Key: WFLY-12870 > URL: https://issues.redhat.com/browse/WFLY-12870 > Project: WildFly > Issue Type: Component Upgrade > Components: Build System > Reporter: Ilia Vassilev > Assignee: Farah Juma > Priority: Major > Labels: downstream_dependency > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12870) Upgrade JBoss JSF API from 3.0.0.SP01 to 3.0.0.SP02

by Ilia Vassilev (Jira)

[ https://issues.redhat.com/browse/WFLY-12870?page=com.atlassian.jira.plugi... ] Ilia Vassilev updated WFLY-12870: --------------------------------- Fix Version/s: (was: 19.0.0.Beta1) > Upgrade JBoss JSF API from 3.0.0.SP01 to 3.0.0.SP02 > --------------------------------------------------- > > Key: WFLY-12870 > URL: https://issues.redhat.com/browse/WFLY-12870 > Project: WildFly > Issue Type: Component Upgrade > Components: Build System > Reporter: Ilia Vassilev > Assignee: Farah Juma > Priority: Major > Labels: downstream_dependency > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12870) Upgrade JBoss JSF API from 3.0.0.SP01 to 3.0.0.SP02

by Ilia Vassilev (Jira)

Ilia Vassilev created WFLY-12870: ------------------------------------ Summary: Upgrade JBoss JSF API from 3.0.0.SP01 to 3.0.0.SP02 Key: WFLY-12870 URL: https://issues.redhat.com/browse/WFLY-12870 Project: WildFly Issue Type: Component Upgrade Components: Build System Affects Versions: 18.0.0.Final Reporter: Ilia Vassilev Assignee: Farah Juma Fix For: 19.0.0.Beta1 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12869) Remove Multiple JSF Applications found on same ClassLoader WARN

by Ilia Vassilev (Jira)

[ https://issues.redhat.com/browse/WFLY-12869?page=com.atlassian.jira.plugi... ] Ilia Vassilev moved JBEAP-18276 to WFLY-12869: ---------------------------------------------- Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-12869 (was: JBEAP-18276) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: JSF (was: JSF) QE Test Coverage: (was: -) Fix Version/s: (was: 7.3.1.GA) > Remove Multiple JSF Applications found on same ClassLoader WARN > --------------------------------------------------------------- > > Key: WFLY-12869 > URL: https://issues.redhat.com/browse/WFLY-12869 > Project: WildFly > Issue Type: Bug > Components: JSF > Reporter: Ilia Vassilev > Assignee: Bartosz Spyrko > Priority: Major > Labels: downstream_dependency > > Upstream removed or commented out this warning, we should remove it as it is spamming log files in some use cases: > jsf-api/src/main/java/javax/faces/CurrentThreadToServletContext.java > {code} > LOGGER.log(Level.WARNING, "Multiple JSF Applications found on same ClassLoader. Unable to safely determine which FactoryManager instance to use. Defaulting to first match."); > // LOGGER.log(Level.WARNING, "Multiple JSF Applications found on same ClassLoader. Unable to safely determine which FactoryManager instance to use. Defaulting to first match."); > {code} > https://github.com/javaserverfaces/mojarra/commit/6864ca0c10abb2a193dc2c3... -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-1398) Connection leak when there is an exception during getConnection for NoTransaction resource adapter

by Ilia Vassilev (Jira)

[ https://issues.redhat.com/browse/JBJCA-1398?page=com.atlassian.jira.plugi... ] Ilia Vassilev reassigned JBJCA-1398: ------------------------------------ Assignee: Stefano Maestri > Connection leak when there is an exception during getConnection for NoTransaction resource adapter > -------------------------------------------------------------------------------------------------- > > Key: JBJCA-1398 > URL: https://issues.redhat.com/browse/JBJCA-1398 > Project: IronJacamar > Issue Type: Bug > Components: Core > Affects Versions: 1.0.31.Final, 1.0.38.Final, 1.4.10 > Reporter: Stephen Fikes > Assignee: Stefano Maestri > Priority: Major > Labels: downstream_dependency > > When an exception occurs with a {{NoTransaction}} resource adapter during a {{getConnection}} attempt the pool leaks the connection. The exception (simulating a timeout of the underlying connect attempt) detail is below. > {code} > ... WARNING [support.jboss.ejb.session.SessionBean] (ServerService Thread Pool -- 51) Failed to get a connection: IJ000456: Unchecked throwable in ManagedConnection.getConnection() cl=org.jboss.jca.core.connectionmanager.listener.NoTxConnectionListener@1a933f80[state=NORMAL managed connection=support.redhat.jboss.jca.ManagedConnectionImpl@7a294431 connection handles=0 lastUse=1575419355891 trackByTx=false pool=org.jboss.jca.core.connectionmanager.pool.strategy.OnePool@1d6a5362 pool internal context=SemaphoreArrayListManagedConnectionPool@2f47607f[pool=EisConnectionFactory]]: javax.resource.ResourceException: IJ000456: Unchecked throwable in ManagedConnection.getConnection() cl=org.jboss.jca.core.connectionmanager.listener.NoTxConnectionListener@1a933f80[state=NORMAL managed connection=support.redhat.jboss.jca.ManagedConnectionImpl@7a294431 connection handles=0 lastUse=1575419355891 trackByTx=false pool=org.jboss.jca.core.connectionmanager.pool.strategy.OnePool@1d6a5362 pool internal context=SemaphoreArrayListManagedConnectionPool@2f47607f[pool=EisConnectionFactory]] > at org.jboss.jca.core.connectionmanager.AbstractConnectionManager.allocateConnection(AbstractConnectionManager.java:521) > at support.redhat.jboss.jca.ConnectionFactoryImpl.getConnection(ConnectionFactoryImpl.java:61) > ... > Caused by: javax.resource.ResourceException: Simulate timeout > at support.redhat.jboss.jca.ManagedConnectionImpl.getConnection(ManagedConnectionImpl.java:61) > at org.jboss.jca.core.connectionmanager.AbstractConnectionManager.allocateConnection(AbstractConnectionManager.java:508) > ... > {code} > There seems to be a difference in a {{NoTransaction}} and an {{XATransaction}} adapter where {{returnConnection}} is triggered by the {{TxConnectionManagerImpl}}. > {code} > ... [BMAN] org.jboss.jca.core.connectionmanager.pool.mcp.SemaphoreArrayListManagedConnectionPool.returnConnection(SemaphoreArrayListManagedConnectionPool.java:-1) > ... org.jboss.jca.core.connectionmanager.pool.AbstractPool.returnConnection(AbstractPool.java:633) > ... org.jboss.jca.core.connectionmanager.AbstractConnectionManager.returnManagedConnection(AbstractConnectionManager.java:456) > ... org.jboss.jca.core.connectionmanager.tx.TxConnectionManagerImpl.managedConnectionDisconnected(TxConnectionManagerImpl.java:515) > ... org.jboss.jca.core.connectionmanager.AbstractConnectionManager.allocateConnection(AbstractConnectionManager.java:525) > {code} > For a {{NoTransaction}} adapter, however, the abstract implementation is used: > {code} > ... [BMAN] org.jboss.jca.core.connectionmanager.AbstractConnectionManager.managedConnectionDisconnected(AbstractConnectionManager.java:697) > ... org.jboss.jca.core.connectionmanager.AbstractConnectionManager.allocateConnection(AbstractConnectionManager.java:525) > {code} > The empty implementation for [AbstractConnectionManager.managedConnectionDisconnected|https://github.co...] does nothing so the connection is not returned as it would be for a transactional implementation. > I also see the same issue with IronJacamar 1.4.18.Final so this issue remains in the latest release. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 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 December 2019