[JBoss-dev] [ jboss-Bugs-990882 ] destroying context with tomcat5 happens too late
Bugs item #990882, was opened at 2004-07-14 07:10 Message generated for change (Comment added) made by starksm You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=990882group_id=22866 Category: JBossWeb Group: v3.2 Status: Open Resolution: None Priority: 7 Submitted By: ittay dror (ittay) Assigned to: Nobody/Anonymous (nobody) Summary: destroying context with tomcat5 happens too late Initial Comment: Hi, When I stop my JBoss (3.2.5), it first undeployes all beans and only then stops the web service. This causes two wrong behaviors: 1. if some client tries to load a page (or send any request to a servlet), after some beans are undeployed, and before the service is stopped, the servlet will start to work but because the beans were undeployed, will get strange errors (NPE etc.) 2. if i want to hook into the contextDestroyed, to perform some cleanup, it is too late, since beans have already been undeployed. -- Comment By: Scott M Stark (starksm) Date: 2004-12-29 12:52 Message: Logged In: YES user_id=175228 All issues have been moved to http://jira.jboss.com. Existing issues have been moved. New issues will be closed with this canned reponse. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=990882group_id=22866 --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-990882 ] destroying context with tomcat5 happens too late
Bugs item #990882, was opened at 2004-07-14 14:10 Message generated for change (Settings changed) made by ittay You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=990882group_id=22866 Category: JBossWeb Group: v3.2 Status: Open Resolution: None Priority: 7 Submitted By: ittay dror (ittay) Assigned to: Nobody/Anonymous (nobody) Summary: destroying context with tomcat5 happens too late Initial Comment: Hi, When I stop my JBoss (3.2.5), it first undeployes all beans and only then stops the web service. This causes two wrong behaviors: 1. if some client tries to load a page (or send any request to a servlet), after some beans are undeployed, and before the service is stopped, the servlet will start to work but because the beans were undeployed, will get strange errors (NPE etc.) 2. if i want to hook into the contextDestroyed, to perform some cleanup, it is too late, since beans have already been undeployed. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=990882group_id=22866 --- This SF.Net email sponsored by Black Hat Briefings Training. Attend Black Hat Briefings Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
