[ http://jira.jboss.com/jira/browse/JBAS-582?page=history ]
     
Scott M Stark closed JBAS-582:
------------------------------

    Resolution: Out of Date

> thread housekeeping in rar deployment
> -------------------------------------
>
>          Key: JBAS-582
>          URL: http://jira.jboss.com/jira/browse/JBAS-582
>      Project: JBoss Application Server
>         Type: Bug
>     Versions: JBossAS-3.2.6 Final
>     Reporter: SourceForge User
>     Assignee: Scott M Stark

>
>
> SourceForge Submitter: rodburgett .
> The IdleRemover and PoolFiller classes in the 
> org.jboss.resource.connectionmanager package each 
> creates a Thread to perform it's job.  Neither Thread is 
> terminated gracefully at shutdown, they continue until 
> all non-daemon threads terminate.
> There are diff files attached for modifications to 
> terminate the threads when the RARDeployer is stopped.
> The IdleRemover32.diff file contains an update to add a 
> public shutdown() method to the class.  The new 
> method simply invokes the existing stop method on the 
> remover field.
> The PoolFiller32.diff file contains updates to add a similar 
> public shutdown() method to the class.  The new 
> method simply invokes a new stop method on the 
> remover field.  The new stop method interrupts the 
> fillerThread, in a fashion very similar to IdelRemover.  
> Two additional updates are included for this class: the 
> addition of a Logger, and message logging as the thread 
> is terminated.
> The RARDeployer32.diff file contains updates to make 
> use of the new shutdown methods in the other classes.  
> A stopService method was added to perform some local 
> cleanup:
>  - invoke super.stopService
>  - shut down the IdleRemover and PoolFiller threads
>  - null out the service controller field
> Also, in the destroy method of the RARDeployer, the 
> order of two commands was reversed. super.destroy 
> should be called before the class loader of the 
> deployment info instance is nulled, since there's no 
> guarantee that the class loader won't be used by some 
> other destroy method in the inheritance chain.

-- 
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
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

Reply via email to