June 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-6666) clustering-web-infinispan: infinite recursion in session activation code

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-6666?page=com.atlassian.jira.plugin.... ] Radoslav Husar reassigned WFLY-6666: ------------------------------------ Assignee: Paul Ferraro (was: Jason Greene) > clustering-web-infinispan: infinite recursion in session activation code > ------------------------------------------------------------------------ > > Key: WFLY-6666 > URL: https://issues.jboss.org/browse/WFLY-6666 > Project: WildFly > Issue Type: Bug > Affects Versions: 9.0.2.Final > Reporter: Kamil Podlešák > Assignee: Paul Ferraro > Attachments: stacktrace, stacktrace2 > > > When unmarshalling of session throws one of the expected exception (ClassNotFoundException, InvalidClassException, InvalidObjectException), it is handled by attempt to remote this session from cache (CoarseSessionFactory.findValue). This attempt, however, ends up in the same method, tries to unmarshall the session, catches the exception.... until it reaches stack limit and throws StackOverflowError. > As an added injury, each exception is logged with full stack, which is getting longer and longer. Total log size is approximately 40MB per request, so it usually quite quickly disappears by log rotation. > Version 10.0.0 is OK (the code is completely different and does not have this problem). > See also: WFLY-6665 (similar, but not exactly the same bug). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6666) clustering-web-infinispan: infinite recursion in session activation code

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-6666?page=com.atlassian.jira.plugin.... ] Radoslav Husar updated WFLY-6666: --------------------------------- Component/s: Clustering > clustering-web-infinispan: infinite recursion in session activation code > ------------------------------------------------------------------------ > > Key: WFLY-6666 > URL: https://issues.jboss.org/browse/WFLY-6666 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 9.0.2.Final > Reporter: Kamil Podlešák > Assignee: Paul Ferraro > Attachments: stacktrace, stacktrace2 > > > When unmarshalling of session throws one of the expected exception (ClassNotFoundException, InvalidClassException, InvalidObjectException), it is handled by attempt to remote this session from cache (CoarseSessionFactory.findValue). This attempt, however, ends up in the same method, tries to unmarshall the session, catches the exception.... until it reaches stack limit and throws StackOverflowError. > As an added injury, each exception is logged with full stack, which is getting longer and longer. Total log size is approximately 40MB per request, so it usually quite quickly disappears by log rotation. > Version 10.0.0 is OK (the code is completely different and does not have this problem). > See also: WFLY-6665 (similar, but not exactly the same bug). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6666) clustering-web-infinispan: infinite recursion in session activation code

by Kamil Podlešák (JIRA)

[ https://issues.jboss.org/browse/WFLY-6666?page=com.atlassian.jira.plugin.... ] Kamil Podlešák commented on WFLY-6666: -------------------------------------- Quick hotfix: https://github.com/podlesh/wildfly/tree/hotfix/inifinte-loop-detection Tests, it *does* solve the problem - but it's too much of a hack for proper pull request (IMO). > clustering-web-infinispan: infinite recursion in session activation code > ------------------------------------------------------------------------ > > Key: WFLY-6666 > URL: https://issues.jboss.org/browse/WFLY-6666 > Project: WildFly > Issue Type: Bug > Affects Versions: 9.0.2.Final > Reporter: Kamil Podlešák > Assignee: Jason Greene > Attachments: stacktrace, stacktrace2 > > > When unmarshalling of session throws one of the expected exception (ClassNotFoundException, InvalidClassException, InvalidObjectException), it is handled by attempt to remote this session from cache (CoarseSessionFactory.findValue). This attempt, however, ends up in the same method, tries to unmarshall the session, catches the exception.... until it reaches stack limit and throws StackOverflowError. > As an added injury, each exception is logged with full stack, which is getting longer and longer. Total log size is approximately 40MB per request, so it usually quite quickly disappears by log rotation. > Version 10.0.0 is OK (the code is completely different and does not have this problem). > See also: WFLY-6665 (similar, but not exactly the same bug). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6033) enable JPA entity class transformation if any of the new Hibernate enhancer properties are enabled

by Scott Marlow (JIRA)

[ https://issues.jboss.org/browse/WFLY-6033?page=com.atlassian.jira.plugin.... ] Scott Marlow updated WFLY-6033: ------------------------------- Fix Version/s: 10.1.0.Final > enable JPA entity class transformation if any of the new Hibernate enhancer properties are enabled > -------------------------------------------------------------------------------------------------- > > Key: WFLY-6033 > URL: https://issues.jboss.org/browse/WFLY-6033 > Project: WildFly > Issue Type: Bug > Components: JPA / Hibernate > Affects Versions: 10.0.0.CR5 > Reporter: Scott Marlow > Assignee: Scott Marlow > Fix For: 10.1.0.Final > > > See new Hibernate properties at [https://github.com/hibernate/hibernate-orm/commit/809e3cf4b9eda5c8922bb8a...]. > New properties that influence entity class transformation are: > {quote} > hibernate.enhancer.enableDirtyTracking > hibernate.enhancer.enableLazyInitialization > hibernate.enhancer.enableAssociationManagement > {quote} > If any of the above properties are true, it is the same as the application setting jboss.as.jpa.classtransformer=true. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6033) enable JPA entity class transformation if any of the new Hibernate enhancer properties are enabled

by Scott Marlow (JIRA)

[ https://issues.jboss.org/browse/WFLY-6033?page=com.atlassian.jira.plugin.... ] Scott Marlow closed WFLY-6033. ------------------------------ Resolution: Done > enable JPA entity class transformation if any of the new Hibernate enhancer properties are enabled > -------------------------------------------------------------------------------------------------- > > Key: WFLY-6033 > URL: https://issues.jboss.org/browse/WFLY-6033 > Project: WildFly > Issue Type: Bug > Components: JPA / Hibernate > Affects Versions: 10.0.0.CR5 > Reporter: Scott Marlow > Assignee: Scott Marlow > Fix For: 10.1.0.Final > > > See new Hibernate properties at [https://github.com/hibernate/hibernate-orm/commit/809e3cf4b9eda5c8922bb8a...]. > New properties that influence entity class transformation are: > {quote} > hibernate.enhancer.enableDirtyTracking > hibernate.enhancer.enableLazyInitialization > hibernate.enhancer.enableAssociationManagement > {quote} > If any of the above properties are true, it is the same as the application setting jboss.as.jpa.classtransformer=true. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6666) clustering-web-infinispan: infinite recursion in session activation code

by Kamil Podlešák (JIRA)

[ https://issues.jboss.org/browse/WFLY-6666?page=com.atlassian.jira.plugin.... ] Kamil Podlešák updated WFLY-6666: --------------------------------- Description: When unmarshalling of session throws one of the expected exception (ClassNotFoundException, InvalidClassException, InvalidObjectException), it is handled by attempt to remote this session from cache (CoarseSessionFactory.findValue). This attempt, however, ends up in the same method, tries to unmarshall the session, catches the exception.... until it reaches stack limit and throws StackOverflowError. As an added injury, each exception is logged with full stack, which is getting longer and longer. Total log size is approximately 40MB per request, so it usually quite quickly disappears by log rotation. Version 10.0.0 is OK (the code is completely different and does not have this problem). See also: WFLY-6665 (similar, but not exactly the same bug). was: When unmarshalling of session throws one of the expected exception (ClassNotFoundException, InvalidClassException, InvalidObjectException), it is handled by attempt to remote this session from cache (CoarseSessionFactory.findValue). This attempt, however, ends up in the same method, tries to unmarshall the session, catches the exception.... until it reaches stack limit and throws StackOverflowError. As an added injury, each exception is logged with full stack, which is getting longer and longer. Total log size is approximately 40MB per request which means it usually quickly gets rolled away. Version 10.0.0 is OK (the code is completely different and does not have this problem). See also: WFLY-6665 (similar, but not exactly the same bug). > clustering-web-infinispan: infinite recursion in session activation code > ------------------------------------------------------------------------ > > Key: WFLY-6666 > URL: https://issues.jboss.org/browse/WFLY-6666 > Project: WildFly > Issue Type: Bug > Affects Versions: 9.0.2.Final > Reporter: Kamil Podlešák > Assignee: Jason Greene > Attachments: stacktrace, stacktrace2 > > > When unmarshalling of session throws one of the expected exception (ClassNotFoundException, InvalidClassException, InvalidObjectException), it is handled by attempt to remote this session from cache (CoarseSessionFactory.findValue). This attempt, however, ends up in the same method, tries to unmarshall the session, catches the exception.... until it reaches stack limit and throws StackOverflowError. > As an added injury, each exception is logged with full stack, which is getting longer and longer. Total log size is approximately 40MB per request, so it usually quite quickly disappears by log rotation. > Version 10.0.0 is OK (the code is completely different and does not have this problem). > See also: WFLY-6665 (similar, but not exactly the same bug). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6666) clustering-web-infinispan: infinite recursion in session activation code

by Kamil Podlešák (JIRA)

[ https://issues.jboss.org/browse/WFLY-6666?page=com.atlassian.jira.plugin.... ] Kamil Podlešák updated WFLY-6666: --------------------------------- Attachment: stacktrace2 Longer stacktrace from the* same request* as the first one > clustering-web-infinispan: infinite recursion in session activation code > ------------------------------------------------------------------------ > > Key: WFLY-6666 > URL: https://issues.jboss.org/browse/WFLY-6666 > Project: WildFly > Issue Type: Bug > Affects Versions: 9.0.2.Final > Reporter: Kamil Podlešák > Assignee: Jason Greene > Attachments: stacktrace, stacktrace2 > > > When unmarshalling of session throws one of the expected exception (ClassNotFoundException, InvalidClassException, InvalidObjectException), it is handled by attempt to remote this session from cache (CoarseSessionFactory.findValue). This attempt, however, ends up in the same method, tries to unmarshall the session, catches the exception.... until it reaches stack limit and throws StackOverflowError. > As an added injury, each exception is logged with full stack, which is getting longer and longer. Total log size is approximately 40MB per request which means it usually quickly gets rolled away. > Version 10.0.0 is OK (the code is completely different and does not have this problem). > See also: WFLY-6665 (similar, but not exactly the same bug). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6666) clustering-web-infinispan: infinite recursion in session activation code

by Kamil Podlešák (JIRA)

[ https://issues.jboss.org/browse/WFLY-6666?page=com.atlassian.jira.plugin.... ] Kamil Podlešák updated WFLY-6666: --------------------------------- Attachment: stacktrace Sample stacktrace (one of the shorter ones) from real application (not the same one referenced in "Steps to Reproduce") > clustering-web-infinispan: infinite recursion in session activation code > ------------------------------------------------------------------------ > > Key: WFLY-6666 > URL: https://issues.jboss.org/browse/WFLY-6666 > Project: WildFly > Issue Type: Bug > Affects Versions: 9.0.2.Final > Reporter: Kamil Podlešák > Assignee: Jason Greene > Attachments: stacktrace > > > When unmarshalling of session throws one of the expected exception (ClassNotFoundException, InvalidClassException, InvalidObjectException), it is handled by attempt to remote this session from cache (CoarseSessionFactory.findValue). This attempt, however, ends up in the same method, tries to unmarshall the session, catches the exception.... until it reaches stack limit and throws StackOverflowError. > As an added injury, each exception is logged with full stack, which is getting longer and longer. Total log size is approximately 40MB per request which means it usually quickly gets rolled away. > Version 10.0.0 is OK (the code is completely different and does not have this problem). > See also: WFLY-6665 (similar, but not exactly the same bug). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6666) clustering-web-infinispan: infinite recursion in session activation code

by Kamil Podlešák (JIRA)

Kamil Podlešák created WFLY-6666: ------------------------------------ Summary: clustering-web-infinispan: infinite recursion in session activation code Key: WFLY-6666 URL: https://issues.jboss.org/browse/WFLY-6666 Project: WildFly Issue Type: Bug Affects Versions: 9.0.2.Final Reporter: Kamil Podlešák Assignee: Jason Greene When unmarshalling of session throws one of the expected exception (ClassNotFoundException, InvalidClassException, InvalidObjectException), it is handled by attempt to remote this session from cache (CoarseSessionFactory.findValue). This attempt, however, ends up in the same method, tries to unmarshall the session, catches the exception.... until it reaches stack limit and throws StackOverflowError. As an added injury, each exception is logged with full stack, which is getting longer and longer. Total log size is approximately 40MB per request which means it usually quickly gets rolled away. Version 10.0.0 is OK (the code is completely different and does not have this problem). See also: WFLY-6665 (similar, but not exactly the same bug). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6576) mod_cluster advertise="false" does not disable advertise if there are no proxies configured

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-6576?page=com.atlassian.jira.plugin.... ] Radoslav Husar updated WFLY-6576: --------------------------------- Fix Version/s: 10.1.0.Final > mod_cluster advertise="false" does not disable advertise if there are no proxies configured > ------------------------------------------------------------------------------------------- > > Key: WFLY-6576 > URL: https://issues.jboss.org/browse/WFLY-6576 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 10.0.0.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Minor > Labels: ux > Fix For: 10.1.0.Final > > > {noformat} > 17:05:56,822 INFO [org.jboss.modcluster] (ServerService Thread Pool -- 64) MODCLUSTER000001: Initializing mod_cluster version 1.3.2.Final > 17:05:56,833 INFO [org.jboss.modcluster] (ServerService Thread Pool -- 64) MODCLUSTER000032: Listening to proxy advertisements on /224.0.1.105:23364 > {noformat} > {noformat} > [standalone@localhost:9990 /] /subsystem=modcluster/mod-cluster-config=configuration:read-resource > { > "outcome" => "success", > "result" => { > "advertise" => false, > "advertise-security-key" => undefined, > "advertise-socket" => undefined, > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 4 months

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 June 2016