You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Jan K (JIRA)" <ji...@apache.org> on 2007/03/21 00:17:34 UTC

[jira] Created: (AMQ-1212) Connections on the Broker side are not being properly disposed of when client closes them.

Connections on the Broker side are not being properly disposed of when client closes them.
------------------------------------------------------------------------------------------

                 Key: AMQ-1212
                 URL: https://issues.apache.org/activemq/browse/AMQ-1212
             Project: ActiveMQ
          Issue Type: Bug
          Components: Broker
    Affects Versions: 4.1.1
         Environment: Latest trunk version (As of March 20, 2007) of AMQ .NET client, windows 2000 (for the broker) 
            Reporter: Jan K
            Priority: Critical


The connection pool on the broker grew until no more connections could be made. I did notice, that the connections that were supposed to have been disposed, have their ConnectionId set to 'Unavailable' when viewed using JConsole. That was the only difference between truly active connections and ones that should have been closed. 

For now, we have fixed it by going back to 4.0.2. 

 


-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Assigned: (AMQ-1212) Connections on the Broker side are not being properly disposed of when client closes them.

Posted by "Rob Davies (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/activemq/browse/AMQ-1212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rob Davies reassigned AMQ-1212:
-------------------------------

    Assignee: Rob Davies

> Connections on the Broker side are not being properly disposed of when client closes them.
> ------------------------------------------------------------------------------------------
>
>                 Key: AMQ-1212
>                 URL: https://issues.apache.org/activemq/browse/AMQ-1212
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 4.1.1
>         Environment: Latest trunk version (As of March 20, 2007) of AMQ .NET client, windows 2000 (for the broker) 
>            Reporter: Jan K
>            Assignee: Rob Davies
>             Fix For: 5.1.0
>
>
> The connection pool on the broker grew until no more connections could be made. I did notice, that the connections that were supposed to have been disposed, have their ConnectionId set to 'Unavailable' when viewed using JConsole. That was the only difference between truly active connections and ones that should have been closed. 
> For now, we have fixed it by going back to 4.0.2. 
>  

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Updated: (AMQ-1212) Connections on the Broker side are not being properly disposed of when client closes them.

Posted by "Rob Davies (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/activemq/browse/AMQ-1212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rob Davies updated AMQ-1212:
----------------------------

    Priority: Major  (was: Critical)

> Connections on the Broker side are not being properly disposed of when client closes them.
> ------------------------------------------------------------------------------------------
>
>                 Key: AMQ-1212
>                 URL: https://issues.apache.org/activemq/browse/AMQ-1212
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 4.1.1
>         Environment: Latest trunk version (As of March 20, 2007) of AMQ .NET client, windows 2000 (for the broker) 
>            Reporter: Jan K
>             Fix For: 5.2.0
>
>
> The connection pool on the broker grew until no more connections could be made. I did notice, that the connections that were supposed to have been disposed, have their ConnectionId set to 'Unavailable' when viewed using JConsole. That was the only difference between truly active connections and ones that should have been closed. 
> For now, we have fixed it by going back to 4.0.2. 
>  

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Resolved: (AMQ-1212) Connections on the Broker side are not being properly disposed of when client closes them.

Posted by "Rob Davies (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/activemq/browse/AMQ-1212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rob Davies resolved AMQ-1212.
-----------------------------

    Fix Version/s: 5.1.0
                       (was: 5.2.0)
       Resolution: Fixed

> Connections on the Broker side are not being properly disposed of when client closes them.
> ------------------------------------------------------------------------------------------
>
>                 Key: AMQ-1212
>                 URL: https://issues.apache.org/activemq/browse/AMQ-1212
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 4.1.1
>         Environment: Latest trunk version (As of March 20, 2007) of AMQ .NET client, windows 2000 (for the broker) 
>            Reporter: Jan K
>            Assignee: Rob Davies
>             Fix For: 5.1.0
>
>
> The connection pool on the broker grew until no more connections could be made. I did notice, that the connections that were supposed to have been disposed, have their ConnectionId set to 'Unavailable' when viewed using JConsole. That was the only difference between truly active connections and ones that should have been closed. 
> For now, we have fixed it by going back to 4.0.2. 
>  

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.