April 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-4932) CLONE - Using session passivation results in WeldListener: java.lang.NullPointerException on normal operation

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/AS7-4932?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration commented on AS7-4932: ---------------------------------------------- Paul Ferraro <paul.ferraro(a)redhat.com> made a comment on [bug 900549|https://bugzilla.redhat.com/show_bug.cgi?id=900549] Quick status update: I've finally managed to reproduce the issue locally. I'm still isolating the exact cause. > CLONE - Using session passivation results in WeldListener: java.lang.NullPointerException on normal operation > ------------------------------------------------------------------------------------------------------------- > > Key: AS7-4932 > URL: https://issues.jboss.org/browse/AS7-4932 > Project: Application Server 7 > Issue Type: Bug > Components: Clustering > Affects Versions: 7.1.2.Final (EAP) > Reporter: Radoslav Husar > Assignee: Paul Ferraro > Priority: Blocker > Labels: as713tracking > Fix For: 7.1.3.Final (EAP) > > > NPE is thrown in roughly 0.36% of HTTP session request processing in the test. > This results in response code 503 returned to the client with the exception. > The test is using passivation-enabled WAR of clusterbench > https://github.com/rhusar/clusterbench > Here is a shorter soak test run that uncovered the issue > https://hudson.qa.jboss.com/hudson/view/EAP6/view/EAP6-Clustering-Soak/jo... > {noformat} > [JBossINF] 19:52:10,113 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host]] (ajp-perf20/10.16.90.58:8009-2570) Exception sending request initialized lifecycle event to listener instance of class org.jboss.weld.servlet.WeldListener: java.lang.NullPointerException > [JBossINF] at org.jboss.as.web.session.ClusteredSession.update(ClusteredSession.java:972) [jboss-as-web-7.1.2.Final-redhat-1.jar:7.1.2.Final-redhat-1] > [JBossINF] at org.jboss.as.web.session.DistributableSessionManager.loadSession(DistributableSessionManager.java:1377) [jboss-as-web-7.1.2.Final-redhat-1.jar:7.1.2.Final-redhat-1] > [JBossINF] at org.jboss.as.web.session.DistributableSessionManager.findSession(DistributableSessionManager.java:673) [jboss-as-web-7.1.2.Final-redhat-1.jar:7.1.2.Final-redhat-1] > [JBossINF] at org.jboss.as.web.session.DistributableSessionManager.findSession(DistributableSessionManager.java:84) [jboss-as-web-7.1.2.Final-redhat-1.jar:7.1.2.Final-redhat-1] > [JBossINF] at org.apache.catalina.connector.Request.doGetSession(Request.java:2618) [jbossweb-7.0.16.Final-redhat-1.jar:] > [JBossINF] at org.apache.catalina.connector.Request.getSession(Request.java:2375) [jbossweb-7.0.16.Final-redhat-1.jar:] > [JBossINF] at org.apache.catalina.connector.RequestFacade.getSession(RequestFacade.java:841) [jbossweb-7.0.16.Final-redhat-1.jar:] > [JBossINF] at org.jboss.weld.context.beanstore.http.LazySessionBeanStore.getSession(LazySessionBeanStore.java:72) [weld-core-1.1.8.Final-redhat-1.jar:1.1.8.Final-redhat-1] > [JBossINF] at org.jboss.weld.context.beanstore.http.LazySessionBeanStore.<init>(LazySessionBeanStore.java:58) [weld-core-1.1.8.Final-redhat-1.jar:1.1.8.Final-redhat-1] > [JBossINF] at org.jboss.weld.context.http.HttpSessionContextImpl.associate(HttpSessionContextImpl.java:31) [weld-core-1.1.8.Final-redhat-1.jar:1.1.8.Final-redhat-1] > [JBossINF] at org.jboss.weld.context.http.HttpSessionContextImpl.associate(HttpSessionContextImpl.java:16) [weld-core-1.1.8.Final-redhat-1.jar:1.1.8.Final-redhat-1] > [JBossINF] at org.jboss.weld.servlet.WeldListener.requestInitialized(WeldListener.java:134) [weld-core-1.1.8.Final-redhat-1.jar:1.1.8.Final-redhat-1] > [JBossINF] at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:143) [jbossweb-7.0.16.Final-redhat-1.jar:] > [JBossINF] at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [jbossweb-7.0.16.Final-redhat-1.jar:] > [JBossINF] at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [jbossweb-7.0.16.Final-redhat-1.jar:] > [JBossINF] at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:368) [jbossweb-7.0.16.Final-redhat-1.jar:] > [JBossINF] at org.apache.coyote.ajp.AjpProcessor.process(AjpProcessor.java:505) [jbossweb-7.0.16.Final-redhat-1.jar:] > [JBossINF] at org.apache.coyote.ajp.AjpProtocol$AjpConnectionHandler.process(AjpProtocol.java:452) [jbossweb-7.0.16.Final-redhat-1.jar:] > [JBossINF] at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:931) [jbossweb-7.0.16.Final-redhat-1.jar:] > [JBossINF] at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_30] > {noformat} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1283) The add at least one user page should not be displayed if a trust store has been defined on the realm.

by Darran Lofthouse (JIRA)

Darran Lofthouse created WFLY-1283: -------------------------------------- Summary: The add at least one user page should not be displayed if a trust store has been defined on the realm. Key: WFLY-1283 URL: https://issues.jboss.org/browse/WFLY-1283 Project: WildFly Issue Type: Bug Components: Domain Management, Security Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 8.0.0.Alpha1 If there is no user defined on the ManagementRealm the add new user page should not be displayed if a trust store has been defined as Client Cert authentication may be possible. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1278) Upgrade HornetQ to 2.3.0.Final

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-1278?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-1278: ----------------------------------------------- Brian Stansberry <brian.stansberry(a)redhat.com> changed the Status of [bug 956278|https://bugzilla.redhat.com/show_bug.cgi?id=956278] from NEW to POST > Upgrade HornetQ to 2.3.0.Final > ------------------------------ > > Key: WFLY-1278 > URL: https://issues.jboss.org/browse/WFLY-1278 > Project: WildFly > Issue Type: Component Upgrade > Components: JMS > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > Fix For: 8.0.0.Alpha1 > > > HornetQ 2.3.0.Final depends on Netty 3.6.2.Final which is the version in WildFly (no need to also upgrade Netty) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JGRP-1619) Fix the OSGi manifest entries

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-1619?page=com.atlassian.jira.plugin.... ] Bela Ban commented on JGRP-1619: -------------------------------- Which file is this ? jgroups.bnd ? Can you attach the modified file here, or - even better - submit a pull request ? > Fix the OSGi manifest entries > ----------------------------- > > Key: JGRP-1619 > URL: https://issues.jboss.org/browse/JGRP-1619 > Project: JGroups > Issue Type: Bug > Affects Versions: 3.3 > Reporter: Markus Wolf > Assignee: Bela Ban > Fix For: 3.3 > > > Currently the headers import the packages org.apache.log4j and org.apache.logging.log4j not optionally. > But in the documentation it is stated, that the log framework could be chosen by the implementor. > This is currently not the case when deploy to an osgi runtime. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1274) Camel integration with CDI

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/WFLY-1274?page=com.atlassian.jira.plugin.... ] Thomas Diesler edited comment on WFLY-1274 at 4/25/13 11:38 AM: ---------------------------------------------------------------- We need to at least verify that the camel-cdi component integrates with our cdi subsystem and that it actually works when a cdi/camel deployment gets processed by our DUPs. When such a thing gets deployed, the camel context and its associated routes must work with the components all wired together. I suspect there is work to be done at the DUP level. was (Author: thomas.diesler): We need to at least verify that the camel-cdi component integrates with our cdi subsystem and that it actually works when a cdi/camel deployment gets processed by our DUPs. When such a thing gets deployed, the camel context and its associated routes must work with the beans with the components all wired together . I suspect there is work to be done at the DUP level. > Camel integration with CDI > -------------------------- > > Key: WFLY-1274 > URL: https://issues.jboss.org/browse/WFLY-1274 > Project: WildFly > Issue Type: Sub-task > Components: OSGi > Reporter: Thomas Diesler > Assignee: Thomas Diesler > Labels: camel > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1274) Camel integration with CDI

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/WFLY-1274?page=com.atlassian.jira.plugin.... ] Thomas Diesler commented on WFLY-1274: -------------------------------------- We need to at least verify that the camel-cdi component integrates with our cdi subsystem and that it actually works when a cdi/camel deployment gets processed by our DUPs. When such a thing gets deployed, the camel context and its associated routes must work with the beans with the components all wired together . I suspect there is work to be done at the DUP level. > Camel integration with CDI > -------------------------- > > Key: WFLY-1274 > URL: https://issues.jboss.org/browse/WFLY-1274 > Project: WildFly > Issue Type: Sub-task > Components: OSGi > Reporter: Thomas Diesler > Assignee: Thomas Diesler > Labels: camel > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1274) Camel integration with CDI

by Anil Saldhana (JIRA)

[ https://issues.jboss.org/browse/WFLY-1274?page=com.atlassian.jira.plugin.... ] Anil Saldhana commented on WFLY-1274: ------------------------------------- http://camel.apache.org/cdi.html I thought this was already supported. > Camel integration with CDI > -------------------------- > > Key: WFLY-1274 > URL: https://issues.jboss.org/browse/WFLY-1274 > Project: WildFly > Issue Type: Sub-task > Components: OSGi > Reporter: Thomas Diesler > Assignee: Thomas Diesler > Labels: camel > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-158) Constant fields that are not final

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-158?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration commented on WFLY-158: ---------------------------------------------- Brian Stansberry <brian.stansberry(a)redhat.com> changed the Status of [bug 926050|https://bugzilla.redhat.com/show_bug.cgi?id=926050] from POST to ASSIGNED > Constant fields that are not final > ---------------------------------- > > Key: WFLY-158 > URL: https://issues.jboss.org/browse/WFLY-158 > Project: WildFly > Issue Type: Bug > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Fix For: 8.0.0.Alpha1 > > Attachments: non-final-fields.txt > > > Analysis by Stephan Mueller shows that the AS codebase includes a significant number of public constant fields that are missing the "final" keyword, which could allow incorrect or nefarious code to change them. This task is to fix these. > As part of the work for a few cases I'll reduce the field visibility. > I'll attach file listing the cases. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-158) Constant fields that are not final

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-158?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration commented on WFLY-158: ---------------------------------------------- Rostislav Svoboda <rsvoboda(a)redhat.com> made a comment on [bug 926050|https://bugzilla.redhat.com/show_bug.cgi?id=926050] PR is ready - https://github.com/jbossas/jboss-eap/pull/73 setting blocker flag to get this change to EAP 6.1.0 > Constant fields that are not final > ---------------------------------- > > Key: WFLY-158 > URL: https://issues.jboss.org/browse/WFLY-158 > Project: WildFly > Issue Type: Bug > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Fix For: 8.0.0.Alpha1 > > Attachments: non-final-fields.txt > > > Analysis by Stephan Mueller shows that the AS codebase includes a significant number of public constant fields that are missing the "final" keyword, which could allow incorrect or nefarious code to change them. This task is to fix these. > As part of the work for a few cases I'll reduce the field visibility. > I'll attach file listing the cases. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1282) rewrite doesn't support conditions

by Jean-Frederic Clere (JIRA)

[ https://issues.jboss.org/browse/WFLY-1282?page=com.atlassian.jira.plugin.... ] Jean-Frederic Clere commented on WFLY-1282: ------------------------------------------- +++ <rewrite pattern="(.*)" substitution="-" flags="F"> <condition test="%{QUERY_STRING}" pattern="wsdl" flags="OR"/> </rewrite> +++ The condition is ignored. Additionally the flags should NOT be mandatory like in mod_rewrite no flags in condition means AND (and you can't use flags="AND"). > rewrite doesn't support conditions > ---------------------------------- > > Key: WFLY-1282 > URL: https://issues.jboss.org/browse/WFLY-1282 > Project: WildFly > Issue Type: Bug > Components: Web (JBoss Web) > Reporter: Jean-Frederic Clere > Assignee: Jean-Frederic Clere > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 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 April 2013