You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Jarek Gawor (JIRA)" <ji...@apache.org> on 2007/12/03 23:24:43 UTC
[jira] Created: (GERONIMO-3667) JNDI is not available in
servlet.destroy() or ServletContextListener.contextDestroyed() callbacks
JNDI is not available in servlet.destroy() or ServletContextListener.contextDestroyed() callbacks
-------------------------------------------------------------------------------------------------
Key: GERONIMO-3667
URL: https://issues.apache.org/jira/browse/GERONIMO-3667
Project: Geronimo
Issue Type: Bug
Security Level: public (Regular issues)
Components: Tomcat
Affects Versions: 2.1
Reporter: Jarek Gawor
Assignee: Jarek Gawor
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-3667) JNDI is not available in
servlet.destroy() or ServletContextListener.contextDestroyed() callbacks
Posted by "Joe Bohn (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-3667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Joe Bohn updated GERONIMO-3667:
-------------------------------
Affects Version/s: 2.0.2
Fix Version/s: (was: 2.0.x)
2.0.3
> JNDI is not available in servlet.destroy() or ServletContextListener.contextDestroyed() callbacks
> -------------------------------------------------------------------------------------------------
>
> Key: GERONIMO-3667
> URL: https://issues.apache.org/jira/browse/GERONIMO-3667
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: Tomcat
> Affects Versions: 2.0.2, 2.1
> Reporter: Jarek Gawor
> Assignee: Jarek Gawor
> Fix For: 2.0.3, 2.1
>
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (GERONIMO-3667) JNDI is not available in
servlet.destroy() or ServletContextListener.contextDestroyed() callbacks
Posted by "Jarek Gawor (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-3667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jarek Gawor resolved GERONIMO-3667.
-----------------------------------
Resolution: Fixed
Fix Version/s: 2.1
2.0.x
Committed fixes to trunk (revision 600788) and branches/2.0 (revision 600789).
> JNDI is not available in servlet.destroy() or ServletContextListener.contextDestroyed() callbacks
> -------------------------------------------------------------------------------------------------
>
> Key: GERONIMO-3667
> URL: https://issues.apache.org/jira/browse/GERONIMO-3667
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: Tomcat
> Affects Versions: 2.1
> Reporter: Jarek Gawor
> Assignee: Jarek Gawor
> Fix For: 2.0.x, 2.1
>
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3667) JNDI is not available in
servlet.destroy() or ServletContextListener.contextDestroyed() callbacks
Posted by "Kan Ogawa (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-3667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12548556 ]
Kan Ogawa commented on GERONIMO-3667:
-------------------------------------
Jarek,
I reported a similar issue before, which is GERONIMO-3528.
After a few days, I will try to test it by using both trunk and branches/2.0 builds.
> JNDI is not available in servlet.destroy() or ServletContextListener.contextDestroyed() callbacks
> -------------------------------------------------------------------------------------------------
>
> Key: GERONIMO-3667
> URL: https://issues.apache.org/jira/browse/GERONIMO-3667
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: Tomcat
> Affects Versions: 2.1
> Reporter: Jarek Gawor
> Assignee: Jarek Gawor
> Fix For: 2.0.x, 2.1
>
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.