[jboss-jira] [JBoss JIRA] (EJBTHREE-2276) Graceful shutdown required for EJB 2.x container

[Tom Ross (Updated) (JIRA)]

     [ https://issues.jboss.org/browse/EJBTHREE-2276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tom Ross updated EJBTHREE-2276:
-------------------------------

    Description: 
Currently the only way to prevent resources being shutdown while a user application is still running after a shutdown command has been issued is to use the <depends> element in the jboss.xml deployment file. This approach is very tedious, inefficient and impractical for a very large applications. Customer is asking for more comprehensive approach where none of the resources are unloaded as long as the user application is still running after a shutdown command is issued. They would like to avoid the need for defining specific dependancies.


  was:
Currently the only way to prevent resources being shutdown while a user application is still running after a shutdown command is issued to use the <depends> element in the jboss.xml deployment file. This approach is very tedious, inefficient and impractical for a very large applications. Customer is asking for more comprehensive approach where none of the resources are unloaded as long as the user application is still running after a shutdown command is issued. They would like to avoid the need for defining specific dependancies.



    
> Graceful shutdown required for EJB 2.x container
> ------------------------------------------------
>
>                 Key: EJBTHREE-2276
>                 URL: https://issues.jboss.org/browse/EJBTHREE-2276
>             Project: EJB 3.0
>          Issue Type: Feature Request
>          Components: core, interceptors
>         Environment: JBoss EAP 5.1.x
>            Reporter: Tom Ross
>
> Currently the only way to prevent resources being shutdown while a user application is still running after a shutdown command has been issued is to use the <depends> element in the jboss.xml deployment file. This approach is very tedious, inefficient and impractical for a very large applications. Customer is asking for more comprehensive approach where none of the resources are unloaded as long as the user application is still running after a shutdown command is issued. They would like to avoid the need for defining specific dependancies.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira