You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@geronimo.apache.org by "Kan Ogawa (JIRA)" <ji...@apache.org> on 2007/10/10 06:06:50 UTC

[jira] Created: (GERONIMO-3528) Cannot lookup JNDI context inside some servlet event listeners.

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: 2.0.1, 1.1.1
            Reporter: Kan Ogawa


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.

[jira] Assigned: (GERONIMO-3528) Cannot lookup JNDI context inside some servlet event listeners.

Posted by "Jarek Gawor (JIRA)" <ji...@apache.org>.

     [ https://issues.apache.org/jira/browse/GERONIMO-3528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jarek Gawor reassigned GERONIMO-3528:
-------------------------------------

    Assignee: Jarek Gawor

> 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.

[jira] Commented: (GERONIMO-3528) Cannot lookup JNDI context inside some servlet event listeners.

Posted by "Kan Ogawa (JIRA)" <ji...@apache.org>.

    [ https://issues.apache.org/jira/browse/GERONIMO-3528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12534734 ] 

Kan Ogawa commented on GERONIMO-3528:
-------------------------------------

Isn't this issue related to the following topic?
http://www.nabble.com/java%3Acomp-JNDI-lookup-seems-to-fail-after-server-restart-tf4584712s134.html

In my tested sample application, the context root is "/examples".

> 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
>         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.

[jira] Closed: (GERONIMO-3528) Cannot lookup JNDI context inside some servlet event listeners.

Posted by "Jarek Gawor (JIRA)" <ji...@apache.org>.

     [ https://issues.apache.org/jira/browse/GERONIMO-3528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jarek Gawor closed GERONIMO-3528.
---------------------------------

    Resolution: Fixed

Great! Thanks for double checking.


> 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
>             Fix For: 2.0.x, 2.1
>
>         Attachments: examples.war, TestedResults.html, TestedResults2_including_G3667.html, TestedResults_including_G3667.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.

[jira] Commented: (GERONIMO-3528) Cannot lookup JNDI context inside some servlet event listeners.

Posted by "Kan Ogawa (JIRA)" <ji...@apache.org>.

    [ https://issues.apache.org/jira/browse/GERONIMO-3528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12549782 ] 

Kan Ogawa commented on GERONIMO-3528:
-------------------------------------

My tested v2.0.3-SNAPSHOT was built from current source code.

> 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
>             Fix For: 2.0.x, 2.1
>
>         Attachments: examples.war, TestedResults.html, TestedResults_including_G3667.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.

[jira] Commented: (GERONIMO-3528) Cannot lookup JNDI context inside some servlet event listeners.

Posted by "Jarek Gawor (JIRA)" <ji...@apache.org>.

    [ https://issues.apache.org/jira/browse/GERONIMO-3528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12549789 ] 

Jarek Gawor commented on GERONIMO-3528:
---------------------------------------

Here's part of the output using your example.war:

[INFO] ServletRequest Destroyed.
[INFO] ServletRequest - JNDI Context 'javax.naming.InitialContext@1d2a35d' has been constructed.
[INFO] ServletRequest - SystemDatabase has been lookuped from JNDI Context and been connected.
[INFO] HttpSession Destroyed.
[INFO] HttpSession - JNDI Context 'javax.naming.InitialContext@128b564' has been constructed.
[INFO] HttpSession - SystemDatabase has been lookuped from JNDI Context and been connected.
[INFO] HttpSession Attribute 'sessAttr1' Removed.
[INFO] HttpSession Attribute - JNDI Context 'javax.naming.InitialContext@1c6849' has been constructed.
[INFO] HttpSession Attribute - SystemDatabase has been lookuped from JNDI Context and been connected.

> 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
>             Fix For: 2.0.x, 2.1
>
>         Attachments: examples.war, TestedResults.html, TestedResults_including_G3667.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.

[jira] Updated: (GERONIMO-3528) Cannot lookup JNDI context inside some servlet event listeners.

Posted by "Kan Ogawa (JIRA)" <ji...@apache.org>.

     [ https://issues.apache.org/jira/browse/GERONIMO-3528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kan Ogawa updated GERONIMO-3528:
--------------------------------

    Attachment: TestedResults.html

Attached the tested results.

> 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
>         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.

[jira] Updated: (GERONIMO-3528) Cannot lookup JNDI context inside some servlet event listeners.

Posted by "Kan Ogawa (JIRA)" <ji...@apache.org>.

     [ https://issues.apache.org/jira/browse/GERONIMO-3528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kan Ogawa updated GERONIMO-3528:
--------------------------------

    Attachment: TestedResults_including_G3667.html

> 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
>             Fix For: 2.0.x, 2.1
>
>         Attachments: examples.war, TestedResults.html, TestedResults_including_G3667.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.

[jira] Updated: (GERONIMO-3528) Cannot lookup JNDI context inside some servlet event listeners.

Posted by "Joe Bohn (JIRA)" <ji...@apache.org>.

     [ https://issues.apache.org/jira/browse/GERONIMO-3528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Joe Bohn updated GERONIMO-3528:
-------------------------------

    Fix Version/s:     (was: 2.0.x)
                   2.0.3

> 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
>             Fix For: 2.0.3, 2.1
>
>         Attachments: examples.war, TestedResults.html, TestedResults2_including_G3667.html, TestedResults_including_G3667.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.

[jira] Commented: (GERONIMO-3528) Cannot lookup JNDI context inside some servlet event listeners.

Posted by "Jarek Gawor (JIRA)" <ji...@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.

[jira] Updated: (GERONIMO-3528) Cannot lookup JNDI context inside some servlet event listeners.

Posted by "Kan Ogawa (JIRA)" <ji...@apache.org>.

     [ https://issues.apache.org/jira/browse/GERONIMO-3528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kan Ogawa updated GERONIMO-3528:
--------------------------------

    Attachment: TestedResults2_including_G3667.html

Jarek,

I have rebuilt snapshot from current source code (r602608) and retested it.
As you say, I have verified that all test cases are OK results.
I have uploaded the test results again. Thank you for supporting!

> 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
>             Fix For: 2.0.x, 2.1
>
>         Attachments: examples.war, TestedResults.html, TestedResults2_including_G3667.html, TestedResults_including_G3667.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.

[jira] Updated: (GERONIMO-3528) Cannot lookup JNDI context inside some servlet event listeners.

Posted by "Kan Ogawa (JIRA)" <ji...@apache.org>.

     [ https://issues.apache.org/jira/browse/GERONIMO-3528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kan Ogawa updated GERONIMO-3528:
--------------------------------

    Attachment: examples.war

Attached sample web application.

> 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
>         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.

[jira] Commented: (GERONIMO-3528) Cannot lookup JNDI context inside some servlet event listeners.

Posted by "Kan Ogawa (JIRA)" <ji...@apache.org>.

    [ https://issues.apache.org/jira/browse/GERONIMO-3528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12549881 ] 

Kan Ogawa commented on GERONIMO-3528:
-------------------------------------

Jarek,

Today, I will build the latest branch/2.0 source code and test it again.

By the way, what is svn revision number of your built and tested snapshot?

> 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
>             Fix For: 2.0.x, 2.1
>
>         Attachments: examples.war, TestedResults.html, TestedResults_including_G3667.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.

[jira] Reopened: (GERONIMO-3528) Cannot lookup JNDI context inside some servlet event listeners.

Posted by "Kan Ogawa (JIRA)" <ji...@apache.org>.

     [ https://issues.apache.org/jira/browse/GERONIMO-3528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kan Ogawa reopened GERONIMO-3528:
---------------------------------


Jarek,

I has re-tested this issue, using the 2.0.3 snapshot  with your fix.
In HttpSessionListener#destroyed callback case only, JNDI lookup fails.
For more detail, see my atteched tested results.

> 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
>             Fix For: 2.0.x, 2.1
>
>         Attachments: examples.war, TestedResults.html, TestedResults_including_G3667.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.

[jira] Resolved: (GERONIMO-3528) Cannot lookup JNDI context inside some servlet event listeners.

Posted by "Jarek Gawor (JIRA)" <ji...@apache.org>.

     [ https://issues.apache.org/jira/browse/GERONIMO-3528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jarek Gawor resolved GERONIMO-3528.
-----------------------------------

       Resolution: Fixed
    Fix Version/s: 2.1
                   2.0.x

Committed fix to branches/2.0 (revision 601864).

Btw Jetty does not have this problem (at least in trunk).


> 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
>             Fix For: 2.0.x, 2.1
>
>         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.

[jira] Commented: (GERONIMO-3528) Cannot lookup JNDI context inside some servlet event listeners.

Posted by "Jarek Gawor (JIRA)" <ji...@apache.org>.

    [ https://issues.apache.org/jira/browse/GERONIMO-3528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12549787 ] 

Jarek Gawor commented on GERONIMO-3528:
---------------------------------------

Can you do svn update and build again becuase I'm not seeing this problem anymore.


> 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
>             Fix For: 2.0.x, 2.1
>
>         Attachments: examples.war, TestedResults.html, TestedResults_including_G3667.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.

[jira] Commented: (GERONIMO-3528) Cannot lookup JNDI context inside some servlet event listeners.

Posted by "Jarek Gawor (JIRA)" <ji...@apache.org>.

    [ https://issues.apache.org/jira/browse/GERONIMO-3528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12549730 ] 

Jarek Gawor commented on GERONIMO-3528:
---------------------------------------

Did you build 2.0.3-SNAPSHOT from source code or downloaded a published snapshot?


> 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
>             Fix For: 2.0.x, 2.1
>
>         Attachments: examples.war, TestedResults.html, TestedResults_including_G3667.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.