January 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-4790) Migrate deployment-scanner module to new MSC API

by Richard Opalka (Jira)

[ https://issues.redhat.com/browse/WFCORE-4790?page=com.atlassian.jira.plug... ] Richard Opalka updated WFCORE-4790: ----------------------------------- Summary: Migrate deployment-scanner module to new MSC API (was: Migrade deployment-scanner module to new MSC API) > Migrate deployment-scanner module to new MSC API > ------------------------------------------------ > > Key: WFCORE-4790 > URL: https://issues.redhat.com/browse/WFCORE-4790 > Project: WildFly Core > Issue Type: Task > Components: Deployment Scanner > Reporter: Richard Opalka > Assignee: Richard Opalka > Priority: Major > Fix For: 11.0.0.Beta6 > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4790) Migrade deployment-scanner module to new MSC API

by Richard Opalka (Jira)

Richard Opalka created WFCORE-4790: -------------------------------------- Summary: Migrade deployment-scanner module to new MSC API Key: WFCORE-4790 URL: https://issues.redhat.com/browse/WFCORE-4790 Project: WildFly Core Issue Type: Task Components: Deployment Scanner Reporter: Richard Opalka Assignee: Richard Opalka Fix For: 11.0.0.Beta6 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12930) HttpSessionListener.sessionDestroyed event can deadlock if it attempts write operations on a session

by Paul Ferraro (Jira)

Paul Ferraro created WFLY-12930: ----------------------------------- Summary: HttpSessionListener.sessionDestroyed event can deadlock if it attempts write operations on a session Key: WFLY-12930 URL: https://issues.redhat.com/browse/WFLY-12930 Project: WildFly Issue Type: Bug Components: Clustering Affects Versions: 18.0.1.Final Reporter: Paul Ferraro Assignee: Paul Ferraro Infinispan listeners are intentionally non-transactional - and thus should never attempt to perform cache writes. In order to trigger the requisite session listeners, session destroy events need to lookup the cache entries relevant to a given session via SessionFactory.findValue(..). However, if there are entries missing (e.g. a creation meta data entry w/out a access meta data entry), this method will attempt to purge the orphaned entries. This should never be done within the context of a session destroy event. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12929) HttpSessionListener.sessionDestroyed event can deadlock if it attempts write operations on a session

by Paul Ferraro (Jira)

[ https://issues.redhat.com/browse/WFLY-12929?page=com.atlassian.jira.plugi... ] Paul Ferraro updated WFLY-12929: -------------------------------- Summary: HttpSessionListener.sessionDestroyed event can deadlock if it attempts write operations on a session (was: Session remove event can deadlock if it attempts write operations on a session) > HttpSessionListener.sessionDestroyed event can deadlock if it attempts write operations on a session > ---------------------------------------------------------------------------------------------------- > > Key: WFLY-12929 > URL: https://issues.redhat.com/browse/WFLY-12929 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 18.0.1.Final > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Priority: Critical > Labels: downstream_dependency > > Infinispan listeners are intentionally non-transactional - and thus should never attempt to perform cache writes. > In order to trigger the requisite session listeners, session destroy events need to lookup the cache entries relevant to a given session via SessionFactory.findValue(..). However, if there are entries missing (e.g. a creation meta data entry w/out a access meta data entry), this method will attempt to purge the orphaned entries. This should never be done within the context of a session destroy event. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12929) Session remove event can deadlock if it attempts write operations on a session

by Paul Ferraro (Jira)

[ https://issues.redhat.com/browse/WFLY-12929?page=com.atlassian.jira.plugi... ] Paul Ferraro updated WFLY-12929: -------------------------------- Description: Infinispan listeners are intentionally non-transactional - and thus should never attempt to perform cache writes. In order to trigger the requisite session listeners, session destroy events need to lookup the cache entries relevant to a given session via SessionFactory.findValue(..). However, if there are entries missing (e.g. a creation meta data entry w/out a access meta data entry), this method will attempt to purge the orphaned entries. This should never be done within the context of a session destroy event. was: Activation/passivation listeners are intentionally non-transactional - and thus should never attempt to perform cache writes. In order to trigger the requisite activation/passivation listeners, activation/passivation events need to lookup the cache entries relevant to a given session via SessionFactory.findValue(..). However, if there are entries missing (e.g. a creation meta data entry w/out a access meta data entry), this method will attempt to purge the orphaned entries. This should never be done within the context of an activation/passivation event. > Session remove event can deadlock if it attempts write operations on a session > ------------------------------------------------------------------------------ > > Key: WFLY-12929 > URL: https://issues.redhat.com/browse/WFLY-12929 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 18.0.1.Final > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Priority: Critical > Labels: downstream_dependency > > Infinispan listeners are intentionally non-transactional - and thus should never attempt to perform cache writes. > In order to trigger the requisite session listeners, session destroy events need to lookup the cache entries relevant to a given session via SessionFactory.findValue(..). However, if there are entries missing (e.g. a creation meta data entry w/out a access meta data entry), this method will attempt to purge the orphaned entries. This should never be done within the context of a session destroy event. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12929) Session remove event can deadlock if it attempts write operations on a session

by Paul Ferraro (Jira)

[ https://issues.redhat.com/browse/WFLY-12929?page=com.atlassian.jira.plugi... ] Paul Ferraro updated WFLY-12929: -------------------------------- Affects Version/s: 18.0.1.Final (was: 18.0.0.Final) > Session remove event can deadlock if it attempts write operations on a session > ------------------------------------------------------------------------------ > > Key: WFLY-12929 > URL: https://issues.redhat.com/browse/WFLY-12929 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 18.0.1.Final > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Priority: Critical > Labels: downstream_dependency > > Activation/passivation listeners are intentionally non-transactional - and thus should never attempt to perform cache writes. > In order to trigger the requisite activation/passivation listeners, activation/passivation events need to lookup the cache entries relevant to a given session via SessionFactory.findValue(..). However, if there are entries missing (e.g. a creation meta data entry w/out a access meta data entry), this method will attempt to purge the orphaned entries. This should never be done within the context of an activation/passivation event. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12929) Session remove event can deadlock if it attempts write operations on a session

by Paul Ferraro (Jira)

[ https://issues.redhat.com/browse/WFLY-12929?page=com.atlassian.jira.plugi... ] Paul Ferraro updated WFLY-12929: -------------------------------- Fix Version/s: (was: 19.0.0.Beta1) > Session remove event can deadlock if it attempts write operations on a session > ------------------------------------------------------------------------------ > > Key: WFLY-12929 > URL: https://issues.redhat.com/browse/WFLY-12929 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 18.0.1.Final > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Priority: Critical > Labels: downstream_dependency > > Activation/passivation listeners are intentionally non-transactional - and thus should never attempt to perform cache writes. > In order to trigger the requisite activation/passivation listeners, activation/passivation events need to lookup the cache entries relevant to a given session via SessionFactory.findValue(..). However, if there are entries missing (e.g. a creation meta data entry w/out a access meta data entry), this method will attempt to purge the orphaned entries. This should never be done within the context of an activation/passivation event. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12929) Session remove event can deadlock if it attempts write operations on a session

by Paul Ferraro (Jira)

[ https://issues.redhat.com/browse/WFLY-12929?page=com.atlassian.jira.plugi... ] Paul Ferraro updated WFLY-12929: -------------------------------- Git Pull Request: (was: https://github.com/wildfly/wildfly/pull/12705) > Session remove event can deadlock if it attempts write operations on a session > ------------------------------------------------------------------------------ > > Key: WFLY-12929 > URL: https://issues.redhat.com/browse/WFLY-12929 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 18.0.1.Final > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Priority: Critical > Labels: downstream_dependency > > Activation/passivation listeners are intentionally non-transactional - and thus should never attempt to perform cache writes. > In order to trigger the requisite activation/passivation listeners, activation/passivation events need to lookup the cache entries relevant to a given session via SessionFactory.findValue(..). However, if there are entries missing (e.g. a creation meta data entry w/out a access meta data entry), this method will attempt to purge the orphaned entries. This should never be done within the context of an activation/passivation event. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12929) Session remove event can deadlock if it attempts write operations on a session

by Paul Ferraro (Jira)

Paul Ferraro created WFLY-12929: ----------------------------------- Summary: Session remove event can deadlock if it attempts write operations on a session Key: WFLY-12929 URL: https://issues.redhat.com/browse/WFLY-12929 Project: WildFly Issue Type: Bug Components: Clustering Affects Versions: 18.0.0.Final Reporter: Paul Ferraro Assignee: Paul Ferraro Fix For: 19.0.0.Beta1 Activation/passivation listeners are intentionally non-transactional - and thus should never attempt to perform cache writes. In order to trigger the requisite activation/passivation listeners, activation/passivation events need to lookup the cache entries relevant to a given session via SessionFactory.findValue(..). However, if there are entries missing (e.g. a creation meta data entry w/out a access meta data entry), this method will attempt to purge the orphaned entries. This should never be done within the context of an activation/passivation event. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4789) Enable TLS 1.3 by default

by Farah Juma (Jira)

Farah Juma created WFCORE-4789: ---------------------------------- Summary: Enable TLS 1.3 by default Key: WFCORE-4789 URL: https://issues.redhat.com/browse/WFCORE-4789 Project: WildFly Core Issue Type: Feature Request Components: Security Reporter: Farah Juma WFCORE-4172 added support for TLS 1.3 but left TLS 1.3 disabled by default for reasons described in WFWIP-160: https://github.com/wildfly/wildfly-core/pull/3815/commits/4ee03bd5662b1fd... Once we are ready to do so, we should enable TLS 1.3 by default. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 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 2020