[dna-issues] [JBoss JIRA] Commented: (DNA-598) Shutting down JcrEngine returns, but leaves idle threads running (preventing shutdown of VM) for 60 seconds
Randall Hauch (JIRA)
jira-events at lists.jboss.org
Thu Dec 17 15:37:30 EST 2009
[ https://jira.jboss.org/jira/browse/DNA-598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12500648#action_12500648 ]
Randall Hauch commented on DNA-598:
-----------------------------------
Fixed the problem with the shutdown leaving idle threads and blocking termination of the VM. After debugging (and using a new NameThreadFactory that creates threads with names beginning with a specified prefix), it's clear now that these extra threads were owned by the Executor used in the FederatedRepositorySource, and this executor was not being shutdown in the FederatedRepositorySource.close() method. The Executor was creating the threads with a timeout of 60sec, which makes sense. Fixing this now properly shuts down the Executor, and this fixes the problem.
> Shutting down JcrEngine returns, but leaves idle threads running (preventing shutdown of VM) for 60 seconds
> -----------------------------------------------------------------------------------------------------------
>
> Key: DNA-598
> URL: https://jira.jboss.org/jira/browse/DNA-598
> Project: DNA
> Issue Type: Bug
> Components: JCR
> Affects Versions: 0.6
> Reporter: Randall Hauch
> Assignee: Randall Hauch
> Fix For: 0.7
>
>
> A simple program that configures, starts, uses, and then (properly) shuts down a JcrEngine will work correctly, but the VM will not exit for roughly 60 seconds after the engine is shutdown. A stack dump shows that there are several running (but idle) worker threads.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the dna-issues
mailing list