Return-Path: Delivered-To: apmail-geronimo-dev-archive@www.apache.org Received: (qmail 83788 invoked from network); 6 Dec 2007 21:24:09 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 6 Dec 2007 21:24:09 -0000 Received: (qmail 45397 invoked by uid 500); 6 Dec 2007 21:23:55 -0000 Delivered-To: apmail-geronimo-dev-archive@geronimo.apache.org Received: (qmail 45351 invoked by uid 500); 6 Dec 2007 21:23:55 -0000 Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: dev@geronimo.apache.org List-Id: Delivered-To: mailing list dev@geronimo.apache.org Received: (qmail 45340 invoked by uid 99); 6 Dec 2007 21:23:55 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 06 Dec 2007 13:23:55 -0800 X-ASF-Spam-Status: No, hits=-100.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.4] (HELO brutus.apache.org) (140.211.11.4) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 06 Dec 2007 21:24:04 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 48372714256 for ; Thu, 6 Dec 2007 13:23:43 -0800 (PST) Message-ID: <26480810.1196976223293.JavaMail.jira@brutus> Date: Thu, 6 Dec 2007 13:23:43 -0800 (PST) From: "Jarek Gawor (JIRA)" To: dev@geronimo.apache.org Subject: [jira] Commented: (GERONIMO-3528) Cannot lookup JNDI context inside some servlet event listeners. In-Reply-To: <23891356.1191989210779.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/GERONIMO-3528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12549197 ] Jarek Gawor commented on GERONIMO-3528: --------------------------------------- Committed fixes to trunk (revision 601860). > Cannot lookup JNDI context inside some servlet event listeners. > --------------------------------------------------------------- > > Key: GERONIMO-3528 > URL: https://issues.apache.org/jira/browse/GERONIMO-3528 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: naming > Affects Versions: 1.1.1, 2.0.1 > Reporter: Kan Ogawa > Assignee: Jarek Gawor > Attachments: examples.war, TestedResults.html > > > In some servlet event listeners, JNDI context lookup fails. > I encountered this issue while testing the following use case: > - When http session has became invalid by timeout, web container automatically updates the logoff datetime to database system. > So I have made sample application to reproduce this issue and the tested results. > This stack trace is one of NG results: > 16:23:35,661 ERROR [[/examples]] Session event listener threw exception > java.lang.NullPointerException > at org.apache.xbean.naming.context.ContextFlyweight.lookup(ContextFlyweight.java:44) > at org.apache.xbean.naming.context.ContextFederation.getFederatedBinding(ContextFederation.java:71) > at org.apache.xbean.naming.context.AbstractFederatedContext.getBinding(AbstractFederatedContext.java:63) > at org.apache.xbean.naming.context.AbstractContext.lookup(AbstractContext.java:129) > at org.apache.xbean.naming.context.AbstractContext.lookup(AbstractContext.java:611) > at org.apache.xbean.naming.context.AbstractContext.lookup(AbstractContext.java:152) > at org.apache.xbean.naming.context.AbstractContext.lookup(AbstractContext.java:597) > at javax.naming.InitialContext.lookup(InitialContext.java:351) > at examples.DBConnector.testConnection(DBConnector.java:26) > at examples.HttpSessionListenerImpl.sessionDestroyed(HttpSessionListenerImpl.java:15) > at org.apache.catalina.session.StandardSession.expire(StandardSession.java:702) > at org.apache.catalina.session.StandardSession.isValid(StandardSession.java:592) > at org.apache.catalina.session.ManagerBase.processExpires(ManagerBase.java:682) > at org.apache.catalina.session.ManagerBase.backgroundProcess(ManagerBase.java:667) > at org.apache.catalina.core.ContainerBase.backgroundProcess(ContainerBase.java:1316) > at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChildren(ContainerBase.java:1601) > at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChildren(ContainerBase.java:1610) > at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChildren(ContainerBase.java:1610) > at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.run(ContainerBase.java:1590) > at java.lang.Thread.run(Thread.java:595) > If Geronimo v1.1, the stack trace is: > [ERROR] HttpSession - SystemDatabase doesn't have been lookuped from JNDI Context. > javax.naming.NameNotFoundException: comp/env/jdbc/SystemDatasource > at org.apache.geronimo.naming.java.RootContext.lookup(RootContext.java:45) > at javax.naming.InitialContext.lookup(InitialContext.java:351) > at examples.DBConnector.testConnection(DBConnector.java:26) > at examples.HttpSessionListenerImpl.sessionDestroyed(HttpSessionListenerImpl.java:15) > at org.apache.catalina.session.StandardSession.expire(StandardSession.java:685) > at org.apache.catalina.session.StandardSession.isValid(StandardSession.java:577) > at org.apache.catalina.session.ManagerBase.processExpires(ManagerBase.java:678) > at org.apache.catalina.session.ManagerBase.backgroundProcess(ManagerBase.java:663) > at org.apache.catalina.core.ContainerBase.backgroundProcess(ContainerBase.java:1283) > at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChildren(ContainerBase.java:1568) > at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChildren(ContainerBase.java:1577) > at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChildren(ContainerBase.java:1577) > at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.run(ContainerBase.java:1557) > at java.lang.Thread.run(Thread.java:595) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.