[ http://jira.jboss.com/jira/browse/JBAS-1008?page=history ]
Scott M Stark updated JBAS-1008:
--------------------------------
Priority: Major (was: Critical)
> destroying context with tomcat5 happens too late
> ------------------------------------------------
>
> Key: JBAS-1008
> URL: http://jira.jboss.com/jira/browse/JBAS-1008
> Project: JBoss Application Server
> Type: Bug
> Components: Web (Tomcat) service
> Versions: JBossAS-3.2.6 Final
> Reporter: SourceForge User
> Assignee: Remy Maucherat
>
>
> SourceForge Submitter: ittay .
> 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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
-------------------------------------------------------
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://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
JBoss-Development mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jboss-development
