You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by anish pathadan <an...@gmail.com> on 2007/04/27 09:16:46 UTC

Re: [jira] Created: (AMQ-1214) threads not stopping causing memory leaks which can lead to OutOfMemoryError

Hi All,
    I tested this issue, the threads which are not stopped are readeChecker
and writeChecker threads started from InactivityMonitor. These two threads
are created as daemon threads. Can anybody please explain me the reason for
creating these threads as daemon threads when TCPTransport itself is a non
daemon thread.

Thanks,
Anish


JIRA jira@apache.org wrote:
> 
> threads not stopping causing memory leaks which can lead to
> OutOfMemoryError
> ----------------------------------------------------------------------------
> 
>                  Key: AMQ-1214
>                  URL: https://issues.apache.org/activemq/browse/AMQ-1214
>              Project: ActiveMQ
>           Issue Type: Bug
>     Affects Versions: 4.1.0
>          Environment: Fedora Core 6
>             Reporter: Xavier Toth
>          Attachments: threadleak.tar.gz
> 
> Threads started by ActiveMQ on behalf of a client persist in a ThreadGroup
> despite calling the 'interrupt' method on the group thereby leaking
> memory.  
> 
> -- 
> This message is automatically generated by JIRA.
> -
> You can reply to this email to add a comment to the issue online.
> 
> 
> 

-- 
View this message in context: http://www.nabble.com/-jira--Created%3A-%28AMQ-1214%29-threads-not-stopping-causing-memory-leaks-which-can-lead-to-OutOfMemoryError-tf3473682s2354.html#a10214262
Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.