You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Jim Gomes (JIRA)" <ji...@apache.org> on 2011/09/17 02:23:08 UTC

[jira] [Created] (AMQNET-343) Thread leak with maxInactivityDuration=0 is specified

Thread leak with maxInactivityDuration=0 is specified
-----------------------------------------------------

                 Key: AMQNET-343
                 URL: https://issues.apache.org/jira/browse/AMQNET-343
             Project: ActiveMQ .Net
          Issue Type: Bug
          Components: ActiveMQ
    Affects Versions: 1.5.1
         Environment: Windows 7, .NET 2.0, .NET 4.0
            Reporter: Jim Gomes
            Assignee: Jim Gomes
             Fix For: 1.5.2


When the wireFormat.maxInactivityDuration=0 parameter is specified on the connection URI, the inactivity monitor thread will not be cleaned up.  If connections are created/destroyed constantly in the application, then eventually the system resources will become exhausted.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (AMQNET-343) Thread leak with maxInactivityDuration=0 is specified

Posted by "Jim Gomes (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/AMQNET-343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jim Gomes resolved AMQNET-343.
------------------------------

    Resolution: Fixed

> Thread leak with maxInactivityDuration=0 is specified
> -----------------------------------------------------
>
>                 Key: AMQNET-343
>                 URL: https://issues.apache.org/jira/browse/AMQNET-343
>             Project: ActiveMQ .Net
>          Issue Type: Bug
>          Components: ActiveMQ
>    Affects Versions: 1.5.1
>         Environment: Windows 7, .NET 2.0, .NET 4.0
>            Reporter: Jim Gomes
>            Assignee: Jim Gomes
>              Labels: leak, thread
>             Fix For: 1.5.2
>
>
> When the wireFormat.maxInactivityDuration=0 parameter is specified on the connection URI, the inactivity monitor thread will not be cleaned up.  If connections are created/destroyed constantly in the application, then eventually the system resources will become exhausted.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira