October 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-12725) ajp huge header

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFLY-12725?page=com.atlassian.jira.plugin... ] Brian Stansberry reassigned WFLY-12725: --------------------------------------- Component/s: Web (Undertow) Assignee: Flavia Rainone (was: Brian Stansberry) > ajp huge header > --------------- > > Key: WFLY-12725 > URL: https://issues.jboss.org/browse/WFLY-12725 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Affects Versions: 18.0.0.Final > Environment: windows7 > Reporter: zai xuan > Assignee: Flavia Rainone > Priority: Major > Labels: headers, long > > There are long headers in the AJP connection, resulting in errors. > ++++++++++++++++++++ > 12:44:37,327 ERROR [io.undertow.request] (default I/O-1) UT005001: An exception > occurred processing the request: java.lang.ArrayIndexOutOfBoundsException: 16 > at io.undertow.server.protocol.ajp.AjpRequestParser.headers(AjpRequestPa > rser.java:490) > at io.undertow.server.protocol.ajp.AjpRequestParser.parseString(AjpReque > stParser.java:536) > at io.undertow.server.protocol.ajp.AjpRequestParser.parse(AjpRequestPars > er.java:353) > at io.undertow.server.protocol.ajp.AjpReadListener.handleEvent(AjpReadLi > stener.java:169) > at io.undertow.server.protocol.ajp.AjpReadListener.handleEvent(AjpReadLi > stener.java:56) > at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java > :92) > at org.xnio.conduits.ReadReadyHandler$ChannelListenerHandler.readReady(R > eadReadyHandler.java:66) > at org.xnio.nio.NioSocketConduit.handleReady(NioSocketConduit.java:89) > at org.xnio.nio.WorkerThread.run(WorkerThread.java:591) > ++++++++++++++++++++ -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-12729) [18.0.x] Session passivation event can deadlock if it attempts write operations on a session

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFLY-12729?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFLY-12729: ------------------------------------ Git Pull Request: (was: https://github.com/wildfly/wildfly/pull/12705) > [18.0.x] Session passivation event can deadlock if it attempts write operations on a session > -------------------------------------------------------------------------------------------- > > Key: WFLY-12729 > URL: https://issues.jboss.org/browse/WFLY-12729 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 18.0.0.Final > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Priority: Critical > Labels: downstream_dependency > Fix For: 18.0.1.Final > > > 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, 1 month

1
0
0 / 0

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

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFLY-12653?page=com.atlassian.jira.plugin... ] Brian Stansberry commented on WFLY-12653: ----------------------------------------- [~pferraro] OK, I created WFLY-12729. > Session passivation event can deadlock if it attempts write operations on a session > ----------------------------------------------------------------------------------- > > Key: WFLY-12653 > URL: https://issues.jboss.org/browse/WFLY-12653 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 18.0.0.Final > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Priority: Critical > Labels: downstream_dependency > 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, 1 month

1
0
0 / 0

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

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFLY-12653?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFLY-12653: ------------------------------------ Priority: Critical (was: Major) > Session passivation event can deadlock if it attempts write operations on a session > ----------------------------------------------------------------------------------- > > Key: WFLY-12653 > URL: https://issues.jboss.org/browse/WFLY-12653 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 18.0.0.Final > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Priority: Critical > Labels: downstream_dependency > 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, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-12729) [18.0.x] Session passivation event can deadlock if it attempts write operations on a session

by Brian Stansberry (Jira)

Brian Stansberry created WFLY-12729: --------------------------------------- Summary: [18.0.x] Session passivation event can deadlock if it attempts write operations on a session Key: WFLY-12729 URL: https://issues.jboss.org/browse/WFLY-12729 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, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-12729) [18.0.x] Session passivation event can deadlock if it attempts write operations on a session

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFLY-12729?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFLY-12729: ------------------------------------ Fix Version/s: 18.0.1.Final (was: 19.0.0.Beta1) > [18.0.x] Session passivation event can deadlock if it attempts write operations on a session > -------------------------------------------------------------------------------------------- > > Key: WFLY-12729 > URL: https://issues.jboss.org/browse/WFLY-12729 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 18.0.0.Final > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Priority: Critical > Labels: downstream_dependency > Fix For: 18.0.1.Final > > > 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, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-12662) Update BouncyCastle from 1.60 to 1.64

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFLY-12662?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFLY-12662: ------------------------------------ Issue Type: Component Upgrade (was: Task) > Update BouncyCastle from 1.60 to 1.64 > ------------------------------------- > > Key: WFLY-12662 > URL: https://issues.jboss.org/browse/WFLY-12662 > Project: WildFly > Issue Type: Component Upgrade > Reporter: Rostislav Svoboda > Assignee: Rostislav Svoboda > Priority: Major > Fix For: 19.0.0.Beta1 > > > Update BouncyCastle -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-12694) Update jackson-databind to 2.9.10.1

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFLY-12694?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFLY-12694: ------------------------------------ Issue Type: Component Upgrade (was: Task) > Update jackson-databind to 2.9.10.1 > ----------------------------------- > > Key: WFLY-12694 > URL: https://issues.jboss.org/browse/WFLY-12694 > Project: WildFly > Issue Type: Component Upgrade > Components: Server > Reporter: Rostislav Svoboda > Assignee: Rostislav Svoboda > Priority: Major > Fix For: 19.0.0.Beta1 > > > Update jackson-databind to 2.9.10.1 > https://github.com/FasterXML/jackson-databind/releases -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-12720) [18.0.1] Update BouncyCastle from 1.60 to 1.64

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFLY-12720?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFLY-12720: ------------------------------------ Issue Type: Component Upgrade (was: Task) > [18.0.1] Update BouncyCastle from 1.60 to 1.64 > ---------------------------------------------- > > Key: WFLY-12720 > URL: https://issues.jboss.org/browse/WFLY-12720 > Project: WildFly > Issue Type: Component Upgrade > Reporter: Rostislav Svoboda > Assignee: Brian Stansberry > Priority: Major > Fix For: 18.0.1.Final > > > Update BouncyCastle -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-12726) [18.0.x] Update jackson-databind to 2.9.10.1

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFLY-12726?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFLY-12726: ------------------------------------ Issue Type: Component Upgrade (was: Task) > [18.0.x] Update jackson-databind to 2.9.10.1 > -------------------------------------------- > > Key: WFLY-12726 > URL: https://issues.jboss.org/browse/WFLY-12726 > Project: WildFly > Issue Type: Component Upgrade > Components: Server > Reporter: Rostislav Svoboda > Assignee: Brian Stansberry > Priority: Major > Fix For: 18.0.1.Final > > > Update jackson-databind to 2.9.10.1 > https://github.com/FasterXML/jackson-databind/releases -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira October 2019